408 Timeout / Curl Error 7 in Executor when accessing deployed site (Self-Hosted)
- 0
- 2
- Self Hosted
- Sites
- Functions
Hey everyone, I am losing my mind over a routing loop/timeout issue on a fresh self-hosted setup. I have a single Linux VPS (IP: 45.141.37.105) and one domain (vietsoul.de).
The main Appwrite console works perfectly at appwrite.vietsoul.de. However, when I try to access my deployed site at vietsoul.de, the browser hangs and eventually throws a 408 Synchronous function execution timed out.
My Setup:
- Appwrite 1.9.0 (Self-Hosted via docker-compose)
- Cloudflare DNS: A Records for
appwrite,sites,functions,www, and@are all pointing to the VPS IP. Proxy status is set to DNS Only so Appwrite handles Let's Encrypt SSL. .envtargets:_APP_DOMAIN="appwrite.vietsoul.de",_APP_DOMAIN_SITES="sites.vietsoul.de"
The Logs:
[Error] Type: Exception
[Error] Message: Internal curl error has occurred within the executor! Error Number: 7
[Error] File: /usr/local/src/Executor/Runner/Docker.php
[Error] Line: 1161
What I have already tried (that did not fix it):
- Server Resources: Verified my VPS has plenty of RAM (5.5GB free, no swapping).
- Cleaned up Runtimes: Reduced
_APP_FUNCTIONS_RUNTIMESdown to justnode-20.0,node-21.0,node-22,php-8.0,php-8.3,static-1,flutter-3.29to prevent network daemon overload. - IPv6: Emptied
_APP_DOMAIN_TARGET_AAAA=to prevent IPv6 routing blackholes. - Internal DNS / Hairpin NAT routing: I tried adding
extra_hoststo the executor forhost-gateway. When that failed, I added networkaliasesto thetraefikcontainer for both theappwriteandruntimesnetworks to force internal DNS resolution.
It seems like the temporary build container on the runtimes network is failing to reach appwrite.vietsoul.de to download the deployment tarball, resulting in the connection refused (Error 7) and the subsequent 408 timeout.
Does anyone know the exact docker-compose routing fix to allow the build containers to resolve the main Appwrite domain on a single-node setup?
I tried debugging it with google gemini, but that thing just seemed to send me into even more destruction...
I never worked with docker tbh and this is my first self hosted Appwrite so i just counted on AI helping me fix 1-2 errors, but i legit got nowhere
seems like ur really close to figurng out the problem, very narrow to some networking issue on docker side
did u try checking traeffic? maybe its getting blocked there somehow
Thanks for the help! I finally fixed it! turns out it was a weird DNS issue from the hoster. The server had a search domain that caused Docker to resolve all internal services (like MariaDB and Redis) to 127.0.0.1, which broke the whole network. I just had to add dns_search: [.] to my compose file to ignore it, and now it works like a charm! Gemini CLI really helped me dig into the VPS directly to find it.
Recommended threads
- Suspicious access pattern detected when ...
Hello, I am having trouble restoring my project. In the past it worked with no problems, but today I get an error "Suspicious access pattern detected". How can ...
- Websites hosted on my appwrite sites hav...
Hello, all my websites hosted on appwrite sites are not running I am getting this message "This site can’t be reached drivehub.appwrite.network took too long t...
- Session cookies stored on wrong (sub-)do...
Hi, I own a domain `example.com` which is registered with the Appwrite nameserver. My website runs on Sites, using `www.example.com` as domain, and my function...