Proxy overview
Coolify runs one coolify-proxy container on each server connected to Coolify. The proxy accepts public HTTP and HTTPS requests, matches each request to a configured domain, and forwards it to the correct resource container over a Docker network.
Traefik is the default proxy in Coolify. You can select Caddy instead, or select Custom (None) and operate your own proxy without Coolify-managed routing.
Choose a proxy
A direct host port mapping bypasses the proxy. Use a mapped port only when a client must connect directly or the protocol does not belong behind an HTTP reverse proxy.
Open the proxy settings
- Open Servers in the Coolify dashboard.
- Select the server that receives traffic for your resources.
- Select Proxy.
The Configuration page shows the selected proxy, its generated Docker Compose configuration, and controls for starting, stopping, restarting, saving, or resetting that configuration. Dynamic Configurations stores file-provider configuration, and Logs shows proxy output.
An invalid proxy configuration can make every application and service on the server unreachable. Keep a copy of working custom configuration and test changes on a non-production server when possible.
Switch between Traefik and Caddy
The running proxy must be stopped before Coolify allows you to switch it. Plan a maintenance window because public routes remain unavailable until the new proxy starts and the resources have compatible labels.
Prepare resource labels
Confirm that applications and services have labels for the target proxy.
For an application with Readonly labels enabled, open its General page and use Reset Labels to Defaults if its generated labels are outdated. For a Docker Compose application or service, save the Compose configuration so Coolify can generate the current proxy labels.
Stop the current proxy
Open Servers > your server > Proxy, then select Stop Proxy. Wait until the status changes to Proxy Exited.
Stopping the proxy interrupts HTTP and HTTPS traffic for every resource routed through it.
Select the new proxy
Select Switch Proxy, confirm the warning, then choose Traefik or Caddy. Coolify replaces the selected proxy type and generates its default configuration.
Custom changes in the previous proxy configuration may not carry over. Recreate only the settings that the new proxy supports.
Start the proxy and redeploy resources
Select Start Proxy. Redeploy or restart each affected application and service so the target proxy labels are present on the running containers.
Verify public routes
Open at least one HTTP and one HTTPS domain on the server. Confirm that HTTPS uses the expected certificate, redirects behave correctly, and the resource responds through the new proxy.
If a route fails, inspect Servers > your server > Proxy > Logs and the resource's generated labels.