
Hi team,
I'm experiencing an issue after upgrading my self-hosted Appwrite instance from version 1.6.2 to 1.7.3.
Initially, I encountered migration issues when trying to update to 1.7.2, which I saw had already been reported on GitHub. I noticed that a contributor had submitted a PR to fix it, and the fix was included in 1.7.3.
I proceeded with the update using the following commands:
docker run -it --rm \
--volume /var/run/docker.sock:/var/run/docker.sock \
--volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw \
--entrypoint="upgrade" \
appwrite/appwrite:1.7.3
Then:
cd appwrite/
docker compose exec appwrite migrate
There were no critical errors during the update or migration process — only a few yellow warnings (screenshot attached).
However, after the upgrade, I'm unable to access the Appwrite console. When I try to log in from an incognito window, the console crashes immediately after attempting authentication, making it completely unusable.
Any guidance on how to resolve this would be greatly appreciated.
Thanks in advance!
(Attached: Screenshot of migration warnings)

Recommended threads
- Having errors migrating to cloud
Project will not migrate compeltely
- ENV vars not updating
When i do `nano .env` it shows `_APP_DOMAIN_TARGET=` as set to my domain, but when i do `docker compose exec appwrite vars` it shows `_APP_DOMAIN_TARGET=` as ...
- Index with the requested key already exi...
I'm using appwrite cli to create DB and I'm getting index_already_exists Is there a way to undestand the index name and maybe to skip if it's already exits?
