Fix a timeout or container that will not start

Error: Timeout / no response / container not starting

DNS is fine but nothing answers — the app container is down or traffic is blocked.

The container crashed or never started, or the firewall is blocking ports 80/443.

The fix

1. Check whether the container is actually running:

   docker ps --format "table {{.Names}}\t{{.Status}}" | grep -i <your-app>

2. If it is not listed or keeps restarting, open Coolify → the app → Logs / build logs and fix the start error, then redeploy.

3. If it IS running, confirm ports 80 and 443 are open on the VPS firewall (and the cloud provider’s security group).

Related Coolify errors

• no available server (Traefik 503) behind your Coolify domain after a successful deploy
• 502 Bad Gateway (Traefik) — build succeeds and container runs, but your-domain.com returns 502 Bad Gateway
• Healthcheck failed / Container is unhealthy — new container never receives traffic, deploy rolls back to the old container (or shows 404 "No available server")
• ECONNREFUSED / ENOTFOUND / connection to server at "postgres" port 5432 failed

Have Emsden Studio fix it for you — from A$149

All Coolify deploy errors