Services show 502 Bad Gateway errors.

Services show 502 Bad Gateway errors. Caddy cannot reach backend containers. Services temporarily unavailable after configuration changes.

Caddy and backend containers are not on the same Docker network, or Caddy needs to be restarted after configuration changes.

Steps:

1. Verify Caddy is running: `docker compose ps caddy`
2. Check Caddy logs: `docker compose logs caddy`
3. Ensure backend containers are on the same network
4. Restart Caddy: `docker compose restart caddy`
5. Test connectivity: `docker exec folkzone-caddy ping backend-container-name`

Always restart Caddy after configuration changes. Ensure all services use the same Docker network.

• Troubleshooting Index
• Docker Infrastructure

Last updated: 2026-06-19

• Return to folkzone