504 Gateway Timeout but No App Errors? Find Who Cut It Off
A 504 with clean app logs can mean a gateway or load balancer timeout ran out first. How I found mine near 30 seconds, and how I tell 502, 503, 504 apart.
Servers & Linux
My own servers and builds are where these came from: a VNC black screen, a Yocto build out of disk, a webhook that fired twice. Each post shows the log line that pointed to the cause, then the fix.
Docker and CI
- docker-compose to docker compose: Why CI Still Fails
- Yocto Build Disk Space: Why 60GB Failed and 200GB Worked
Self-hosting
- n8n Retry On Fail Sent It Twice: Why, and How to Fix It
- TigerVNC Black Screen on Ubuntu: Check xstartup First
- 504 Gateway Timeout but No App Errors? Find Who Cut It Off
All posts, newest first
docker-compose to docker compose: Why CI Still Fails
docker-compose: command not found usually means only the v1 binary is gone. Search the whole repo, CI workflows included, then switch to docker compose.
n8n Retry On Fail Sent It Twice: Why, and How to Fix It
n8n Retry On Fail re-runs the whole node, every item included, after a timeout, even when the first call landed. Why it duplicates, and how to fix it.
Yocto Build Disk Space: Why 60GB Failed and 200GB Worked
How much disk space does a Yocto build need? The Yocto 6.0 docs say 140GB free. My i.MX6 build stopped on 60GB; on 200GB+ it finished in 2h 20m.
TigerVNC Black Screen on Ubuntu: Check xstartup First
TigerVNC connects on Ubuntu but the screen stays black? Check ~/.vnc/xstartup and its execute bit first. And skip opening port 5901: use an SSH tunnel.