====== Caddy 502 Bad Gateway ======

Services show 502 Bad Gateway errors.

===== Symptom =====

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

===== Cause =====

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

===== Fix =====

**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`

===== Prevention =====

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

===== See Also =====

  * [[folkzone:troubleshooting:start|Troubleshooting Index]]
  * [[folkzone:infrastructure:docker|Docker Infrastructure]]

Last updated: 2026-06-19
  * [[folkzone:start|Return to folkzone]]