Traefik overview

Traefik is Coolify's default integrated reverse proxy. Coolify generates Traefik routes from resource domains and container ports, connects the proxy to the required Docker networks, and configures automatic TLS certificates for HTTPS domains.

Most deployments do not need to edit Traefik directly. Use the proxy guides only when the generated defaults do not cover your routing, certificate, or authentication requirement.

The short version

Set a domain on an application or service and Coolify generates the normal Traefik route. Use dynamic configuration for reusable file-based middleware, custom certificates, dashboards, and load-balancer services.

Changes to the main Traefik Docker Compose configuration require a proxy restart. File-based dynamic configuration is watched and can update without restarting Traefik.


What Coolify manages

Coolify configures:

  • the coolify-proxy Traefik container on connected servers
  • public http and https entry points on ports 80 and 443
  • Docker and file providers for generated routes and dynamic configuration
  • the letsencrypt TLS certificate resolver for HTTP challenge
  • resource router, middleware, service, and target-port labels
  • the Docker networks that let Traefik reach routed resources

The main configuration is stored at /data/coolify/proxy/docker-compose.yml. Traefik file-provider configuration is stored under /data/coolify/proxy/dynamic/ and mounted at /traefik/dynamic/ inside the proxy container.

Keep generated routing intact

Resetting the proxy configuration removes custom changes from the main Docker Compose file. Editing application labels after disabling Readonly labels also makes you responsible for preserving every generated route and middleware label.


Choose a Traefik guide

Certificates

Choose how Traefik obtains or loads TLS certificates.

Advanced routing

Change how Traefik processes and distributes requests.

On this page