Back

Gateway Timeout on Console after Upgrade from 1.5.3 to 1.5.4

  • 0
  • Self Hosted
  • General
BobcatProgrammer
29 Mar, 2024, 18:15

I upgraded from 1.5.3 to 1.5.4 following the guide https://appwrite.io/docs/advanced/self-hosting/update After upgrade I get a Gateway Timeout when accessing the console (Traefik error)

I ran the migration script and also already tried docker compose down followed by 'docker compose up -d' All containers are up and running ( docker ps and portainer dashboard say so)

Where should i go look?

TL;DR
Developers upgraded from 1.5.3 to 1.5.4 and encountered a `Gateway Timeout` error on the console (Traefik issue). Running `docker compose up -d --build --force-recreate` fixed the problem.
BobcatProgrammer
29 Mar, 2024, 18:15

Traefik Logs: ''' time="2024-03-29T17:42:50Z" level=info msg="Configuration loaded from flags." time="2024-03-29T17:54:09Z" level=error msg="accept tcp [::]:443: use of closed network connection" entryPointName=appwrite_websecure time="2024-03-29T17:54:09Z" level=error msg="accept tcp [::]:80: use of closed network connection" entryPointName=appwrite_web time="2024-03-29T17:54:09Z" level=error msg="close tcp [::]:80: use of closed network connection" entryPointName=appwrite_web time="2024-03-29T17:54:27Z" level=info msg="Configuration loaded from flags." time="2024-03-29T17:56:01Z" level=error msg="accept tcp [::]:80: use of closed network connection" entryPointName=appwrite_web time="2024-03-29T17:56:01Z" level=error msg="Error while starting server: accept tcp [::]:80: use of closed network connection" entryPointName=appwrite_web time="2024-03-29T17:56:01Z" level=error msg="accept tcp [::]:443: use of closed network connection" entryPointName=appwrite_websecure time="2024-03-29T17:56:21Z" level=info msg="Configuration loaded from flags." '''

BobcatProgrammer
29 Mar, 2024, 18:15

Appwrite Logs: ' Worker 2 started successfully Worker 1 started successfully Worker 3 started successfully Worker 4 started successfully Worker 5 started successfully Worker 6 started successfully Worker 7 started successfully Worker 8 started successfully Worker 11 started successfully Worker 9 started successfully Worker 10 started successfully Worker 12 started successfully [Setup] - Server database init started... [Setup] - Creating database: appwrite... [Setup] - Server database init completed... Server started successfully (max payload is 6,291,456 bytes) Master pid 1, manager pid 7 Worker 2 started successfully Worker 1 started successfully Worker 4 started successfully Worker 3 started successfully Worker 5 started successfully Worker 6 started successfully Worker 7 started successfully Worker 8 started successfully Worker 9 started successfully Worker 10 started successfully Worker 11 started successfully Worker 12 started successfully [Setup] - Server database init started... [Setup] - Creating database: appwrite... [Setup] - Server database init completed... Server started successfully (max payload is 6,291,456 bytes) Master pid 1, manager pid 6 Worker 1 started successfully Worker 2 started successfully Worker 3 started successfully Worker 4 started successfully Worker 5 started successfully Worker 7 started successfully Worker 6 started successfully Worker 8 started successfully Worker 10 started successfully Worker 9 started successfully Worker 11 started successfully Worker 12 started successfully [Setup] - Server database init started... [Setup] - Creating database: appwrite... [Setup] - Server database init completed... Server started successfully (max payload is 6,291,456 bytes) Master pid 1, manager pid 7 '

BobcatProgrammer
29 Mar, 2024, 18:52

docker compose up -d --build --force-recreate fixed it.. no idea why

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