Site Tools


troubleshooting:caddy_traefik_port_conflict

Caddy Port Conflict with Coolify Traefik

Status: Resolved
Date: 2026-05-27
Affected service: Caddy

Symptom

After restarting the Caddy container, it failed to start with:

Bind for 0.0.0.0:80 failed: port is already allocated

All services at folk.zone subdomains returned 502 Bad Gateway.

Root Cause

Coolify's built-in Traefik proxy was already bound to port 80 on the host. Both Caddy and Traefik were trying to bind the same host port.

Fix

Changed Caddy's host port mapping in docker-compose.yml from 80:80 to 8082:80. The container still listens on port 80 internally, so Cloudflare Tunnel (which connects via the Docker network using caddy:80) required no changes.

# docker-compose.yml
caddy:
  ports:
    - "8082:80"  # was "80:80"

See Also

troubleshooting/caddy_traefik_port_conflict.txt · Last modified: by 127.0.0.1