I think people have also had problems migrating if they don't migrate their appwrite-certificates and maybe appwrite-config volume. This is because the database has data about certificates generated, but the certificates don't actually exist on disk so HTTPS doesn't work.
If you didn't get a chance to backup those, you can try to manually delete the certificates info in the database manually. $ and > characters to indicate whether the command is executed in the shell or mysql CLI, respectively:
# shell into the mariadb container$ docker-compose exec mariadb sh
# authenticate with mysql# do not add whitespace between -p and password$ mysql -u root -p"$MYSQL_ROOT_PASSWORD"# use the appwrite database> use appwrite;# Find the documentID for your domain in the database:> SELECT * FROM `app_console.database.properties` p where p.key ="domain";# note the documentUid - that's what we'll use to query/delete them from the database# We'll need to remove the document from two tables, here's the other one> SELECT * FROM `app_console.database.documents` d where d.uid ="thedocumentUID";# Now we can delete these two rows:> DELETE FROM `app_console.database.properties` where documentUid ="thedocumentUID";> DELETE FROM `app_console.database.documents` where uid ="thedocumentUID";
I think people have also had problems migrating if they don't migrate their
appwrite-certificates
and maybeappwrite-config
volume. This is because the database has data about certificates generated, but the certificates don't actually exist on disk so HTTPS doesn't work.If you didn't get a chance to backup those, you can try to manually delete the certificates info in the database manually.
$
and>
characters to indicate whether the command is executed in the shell or mysql CLI, respectively:Credits to @kodumbeats for the SQL queries.