Skip to content
Back

Unable to login after upgrade to 1.9.5

  • 0
  • 2
  • Self Hosted
6 Jul, 2026, 13:24

I had v1.9.0 installed on a VPS without a web server installed, I followed the instructions as per the upgrade guide with the added --migrate=true arg as there is no web server on the VPS to run the installation URL provided during an normal install/upgrade. All wen twell, the docker compose and .env were backed up and new args were added, I ran the upgrade command and stepped through the questions, set no to assistant and all others came from the .env file, secrets etc are unchanged. All green. I ran the migrate command, no issues in the output.

Since completing I have been unable to login with the console, 404 Not Found Error for Login, register and reset password

Console outputs POST https://..***/v1/account/sessions/email 404 (Not Found)

There is no error output in the logs, with a 200 response from /v1/health/version in the http.request.

Running docker ps --no-trunc I see all looks good EXCEPT for the appwrite container: appwrite/appwrite:1.9.5 - "docker-php-entrypoint php app/http.php" - 25 minutes ago - Up 25 minutes (unhealthy) - 80/tcp - appwrite

Where the executor uses the same args but is healthy. openruntimes/executor:0.25.1 - "docker-php-entrypoint php app/http.php" - 25 minutes ago - Up 25 minutes (healthy) - 80/tcp - exc1

Any ideas before I wipe the VPS and start again?

TL;DR
User unable to login after upgrading to version 1.9.5 of Appwrite. The logs show issues with HTTPS force option being disabled, logging adapter misconfigured, and connectivity errors in Console.DB and Projects.DB. They are receiving a warning related to 'foreach()' and a 404 error locally. Solution: Enable HTTPS force option, configure logging adapter, resolve connectivity issues with Console.DB and Projects.DB.
6 Jul, 2026, 13:45

I can help. This usually happens when the Appwrite container upgrade didn’t complete properly or the reverse proxy/API routing is broken after migration, especially since the appwrite container is showing unhealthy and /v1/account/sessions/email is returning 404. Did you check the logs specifically for the appwrite and traefik/nginx containers, and can you confirm whether /v1/account endpoints respond locally from inside the VPS?

6 Jul, 2026, 15:51

Hi Albert, I did look at container logs and nothing shows an error in appwrite logs and traefik logs are empty, appwrite-console does show normal load of page but no logs when clicking Sign-In etc. The VPS cannot connect locally either, 404 error still.

Running docker inspect appwrite in the Health->Status->Log section I see this

Running Appwrite Doctor for version 1.9.5 ...

[Settings] 🟒 Hostname is valid (###) 🟒 CNAME record target is valid (###) 🟒 A record target is valid (127.0.0.1) 🟒 AAAA record target is valid (::1) 🟒 Using a unique secret key for encryption 🟒 App environment is set for production 🟒 Abuse protection is enabled 🟒 Console access limits are enabled πŸ”΄ HTTPS force option is disabled πŸ”΄ HTTPS force option is disabled for function/site domains πŸ”΄ Logging adapter is misconfigured

[Connectivity] πŸ”΄ Console.DB.(console)...........................disconnected πŸ”΄ Projects.DB.(database_db_main).................disconnected 🟒 Cache(cache_redis_main)...........................connected

Warning: foreach() argument must be of type array|object, null given in /usr/src/code/src/Appwrite/Platform/Tasks/Doctor.php on line 179 🟒 PubSub(pubsub)....................................connected

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more