Fix Coolify Dashboard Unreachable After Reboot

Error: Coolify dashboard won't load / This site can't be reached

The Coolify UI (and your hosted sites) won't load because the Coolify containers or the proxy didn't come back up healthy after a server restart.

After a server reboot the Coolify containers and the proxy must restart for the dashboard and your domains to route. Two things commonly break this on Coolify: (1) the proxy isn't running, so nothing on your domains resolves through it, and the dashboard is down even though the server is up; (2) the coolify container comes back unhealthy because the bundled Redis volume got into a bad state on the unclean reboot, a recurring issue reported in the Coolify repo. Port 8000 (Coolify's direct, proxy-bypassing dashboard port) may also be blocked by a firewall or taken by another container.

The fix

1. Test the dashboard directly by IP, bypassing the proxy. Open your firewall on port 8000 and visit http://<your-vps-ip>:8000. If the login page shows, Coolify is up and the problem is the proxy (skip to the proxy step).

2. SSH into the server and check the Coolify containers are running and healthy.

   docker ps --format "table {{.Names}}\t{{.Status}}"

3. If a Coolify container is missing or unhealthy, restart it and re-check its status.

   docker restart coolify

4. If port 8000 is held by a non-Coolify container, stop everything then bring only Coolify back up to clear the conflict.

   docker stop $(docker ps -q) && docker start $(docker ps -a -q --filter "name=coolify")

5. If the coolify container keeps coming back unhealthy after the reboot, its Redis volume is likely corrupted (a known post-reboot issue). Stop Docker, clear the coolify-redis data, then start Docker again.

   systemctl stop docker && rm -rf /var/lib/docker/volumes/coolify-redis/_data/* && systemctl start docker

6. Start the proxy: in the Coolify dashboard go to the Proxy page and click 'Start Proxy', then wait about two minutes for it to come up and pick up routes. If the proxy was recently reconfigured, reset it and check its logs. To prevent recurrence, confirm the proxy and apps are set to restart on boot.

Verify it worked

your-domain.com (and your hosted sites) load again over HTTPS, and the dashboard is reachable on its normal domain rather than only via http://<your-vps-ip>:8000.

docker ps --filter "name=coolify-proxy" --format "{{.Names}} {{.Status}}"

Related Coolify errors

• Timeout / no response / container not starting
• 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")

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

All Coolify deploy errors