The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Update Coolify’s Traefik proxy from Servers > your server > Proxy > Configuration: save a copy of the working configuration, change the image version, save the configuration in Coolify, restart the proxy, redeploy resources when labels or networks changed, and test both HTTP and HTTPS domains. Do not treat /data/coolify/proxy/docker-compose.yml as the permanent source of truth for UI-managed changes, because Coolify can regenerate it.
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
What a Traefik update changes in Coolify
Traefik is Coolify’s default integrated reverse proxy. A proxy container runs on each Coolify server that hosts resources and receives public traffic for those resources. Updating its image therefore affects more than one application: an invalid main Compose definition, a missing network, or an incompatible setting can make every public route on that server fail.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteA routine update changes the Traefik image tag while retaining the existing entry points, certificate resolvers, volumes, networks, ports, environment variables, and generated routing labels. A broader proxy migration changes the proxy type or several of those settings. Treat the second case as a service-wide change rather than a simple version bump.
Current Coolify documentation says new proxy configurations use Traefik v3.7. That does not by itself mean every existing custom configuration should be changed to v3.7. Review an existing configuration for custom flags, certificates, mounts, and network assumptions before selecting a new image version.
Prepare a safe maintenance window
Identify the affected server
In Coolify, note which server receives the domains you intend to test. The proxy is configured per server, so changing one server does not update proxies on other servers. If your resources are spread across servers, repeat the process separately and verify each server’s domains.
Keep a known-good copy
Before editing, copy the current proxy configuration somewhere you can retrieve it. Coolify generates the main file at /data/coolify/proxy/docker-compose.yml, but the supported place to make persistent changes is the Proxy Configuration screen. Saving a copy of the configuration text gives you a rollback reference if the new image will not start or routes stop working.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Plan for a brief interruption
Changing the main Compose definition requires a proxy restart. Public traffic can be interrupted while the container is replaced and reconnects to its networks. Switching proxy types temporarily interrupts every public route on that server. Schedule the change when a short service interruption is acceptable, and avoid combining an image update with unrelated routing edits unless you have a specific reason.
Use a non-production server for risky changes
If you are changing command flags, ports, volumes, environment variables, certificate resolvers, or networks in addition to the image tag, test the configuration on a non-production server where possible. A routine image update is easier to diagnose when those other variables remain unchanged.
Update Traefik through the Coolify dashboard
1. Open the proxy configuration
- Sign in to the Coolify dashboard.
- Open Servers.
- Select the server that receives the traffic.
- Choose Proxy, then open Configuration.
The page shows the selected proxy, the generated Docker Compose configuration, and controls to start, stop, restart, save, or reset it. Confirm that you are editing the intended server before changing any text.
2. Inspect the existing definition
Find the Traefik image reference and record its current tag. Read the surrounding Compose definition before changing it. Preserve the existing entry points and their ports, certificate resolvers, mounted volumes, attached networks, environment variables, and command-line flags unless the upgrade specifically requires a documented change.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallPay particular attention to custom certificate storage and ACME-related settings. Removing a volume or changing a resolver can affect certificate renewal even when the container itself starts normally. Likewise, removing a network can leave the proxy unable to reach an application that still appears healthy.
Rank #2
3. Change only the image version for a routine update
Replace the current Traefik image tag with the version you have selected. Keep the rest of the generated configuration intact for a routine update. Existing custom configurations should be reviewed before moving to the version used by new Coolify configurations, because custom flags or older assumptions may not be compatible without additional work.
Do not delete generated routing labels or rewrite them by hand as part of an image-only update. Coolify creates labels and network connections for deployed resources; those should continue to be generated by Coolify rather than replaced with an untracked manual configuration.
4. Save in Coolify
Click Save on the Proxy Configuration page after reviewing the edited definition. An edit made only in the server’s filesystem is not synchronized back to the dashboard. When Coolify starts or restarts the proxy, it can regenerate the file and replace a disk-only edit. Resetting the proxy configuration also removes custom changes from the main Compose file, so do not use Reset unless you intentionally want to discard them.
5. Restart the proxy
Use the page’s Restart control after saving a change to the image or to the main Compose definition. A restart is required when you change the image, command flags, environment variables, ports, volumes, or the main /data/coolify/proxy/docker-compose.yml definition. Wait for the proxy to return to a running state before judging the application routes.
6. Redeploy resources when their generated data must change
Redeploy or restart an affected resource when you changed domains, ports, proxy behavior, Compose definitions, or networks and Coolify must regenerate labels or destination-network connections. An image-only proxy restart does not normally require every application to be redeployed, but a resource whose labels or network attachments changed does.
When a restart is required
| Change | Restart the proxy? | Additional action |
|---|---|---|
| Traefik image tag in the main Compose definition | Yes | Save in Coolify, then verify public routes. |
| Command-line flags or environment variables | Yes | Check entry points, certificate resolvers, and startup logs. |
| Ports, volumes, or attached networks in the main Compose definition | Yes | Redeploy resources if their destination networks or labels must be regenerated. |
File-based dynamic configuration under /data/coolify/proxy/dynamic/ |
Normally no | Allow Traefik to watch the file, then inspect logs and test the affected route. |
| Application domains, ports, proxy behavior, or Compose definitions | Usually the resource must be deployed or restarted | Redeploy the affected resource so Coolify regenerates labels and network connections. |
Dynamic files are watched separately from the main Compose definition, so a valid file change normally takes effect without restarting Traefik. That convenience does not protect against YAML syntax errors or references to missing objects; those mistakes can disable routes while the Traefik process continues running.
Use the Coolify CLI instead
Coolify documents this command for updating proxy settings:
Recommended Free Tools
Rank #3
- Mastering Docker: Enhance your containerization and DevOps skills to deliver production ready applications, 4th Edition
- Packt Publishing
- ABIS BOOK
coolify server proxy update <server_uuid>
The command accepts --proxy-type, including TRAEFIK. Run the help command on the installed CLI to see the options supported by that version:
coolify server proxy update --help
The CLI is useful for repeatable administration or automation, but it does not remove the need to preserve the working configuration and verify routes. Confirm the server UUID before running the command, and use the dashboard afterward to inspect the saved proxy configuration and its status.
Verify the update from the outside
Test an HTTP domain
Open at least one HTTP domain served by the updated server. Confirm that the request reaches the expected application and that any intended HTTP-to-HTTPS redirect still occurs. A response from the wrong application can indicate an altered router rule or label even when the proxy container is running.
Test an HTTPS domain
Open at least one HTTPS domain and inspect the certificate presented by the browser. Confirm that the certificate matches the hostname, is not unexpectedly expired, and that the application response is the one expected for that resource. Test a hostname that uses the same certificate resolver and entry point as your production routes if those differ.
Check the proxy logs
In Coolify, open Servers > your server > Proxy > Logs. Look for startup failures, rejected configuration, port-binding errors, certificate-resolver messages, and network-connection errors. Check the logs immediately after the restart and again after opening a test domain so that request-time routing errors are visible.
Inspect generated labels and networks
If one resource fails while others work, inspect that resource’s generated labels and its network attachments. Coolify connects the proxy to destination networks when resources are created, deployed, or when the proxy starts or restarts. A missing connection may require restarting the proxy or redeploying the resource.
- Expected application response appears on HTTP.
- Expected redirect behavior is preserved.
- HTTPS presents the correct certificate for the hostname.
- The application is reachable through its normal public domain.
- Proxy logs show no startup or routing errors for the test requests.
- The affected resource has the expected labels and destination network.
Routine image update versus proxy migration
| Decision point | Routine Traefik image update | Broader proxy migration or redesign |
|---|---|---|
| Image tag | Changes to the selected Traefik version. | May change along with the proxy type or image family. |
| Flags, ports, volumes, and environment | Remain unchanged unless compatibility requires a documented adjustment. | May all change and need a configuration review. |
| Generated labels and destination networks | Should remain compatible with existing resources. | Must be checked and often regenerated through redeployment. |
| Interruption | Plan for an interruption while the proxy restarts. | Switching proxies temporarily interrupts every public route on the server. |
| Certificate and redirect checks | Verify at least one HTTP and one HTTPS domain. | Verify every entry point, resolver, redirect, and representative application class. |
| Rollback | Restore the saved configuration, save it in Coolify, and restart. | Restore the complete known-good proxy definition and redeploy resources whose labels or networks changed. |
If your planned change belongs in the right-hand column, document every intentional difference before applying it. Treat each changed port, volume, resolver, and network as a separate failure point rather than assuming that a new image alone caused a problem.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot common failures
Coolify overwrote your manual edit
Symptom: The image tag or another setting reverted after starting or restarting the proxy.
Cause: The change was made only in /data/coolify/proxy/docker-compose.yml and was not saved in the dashboard.
Fix: Reopen Servers > your server > Proxy > Configuration, apply the change there, click Save, and then restart. Keep the file on disk as a reference, not as the UI-managed source of truth.
The proxy will not start or every route is down
Symptom: Applications and services on the server become unreachable after the change.
Cause: The main Compose definition may contain invalid YAML, an unsupported flag, a port conflict, a missing volume, or an unavailable network.
Fix: Open the proxy logs, compare the saved configuration with your known-good copy, and restore the last working definition in the Configuration page. Save it and restart the proxy. Test HTTP and HTTPS before attempting another upgrade.
Only one application is unreachable
Symptom: The proxy is running and most domains work, but one resource returns an error or timeout.
Best Value
Cause: The resource may have stale labels, a changed port, or no connection to the destination network.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Fix: Inspect the resource’s generated labels and network attachments, then redeploy or restart that resource. Restart the proxy as well if its network connections were created or changed during the operation.
Traefik runs but a dynamic route disappeared
Symptom: The process stays up, but a route defined by a file under /data/coolify/proxy/dynamic/ no longer works.
Cause: The dynamic YAML may contain a syntax error or refer to a missing middleware, service, router, or certificate object.
Fix: Restore the last working dynamic file, check the proxy logs for the rejected object, and correct the reference. A main-proxy restart is normally unnecessary for a valid dynamic-file change, but do not assume a file was accepted merely because the container remained running.
HTTPS fails after the update
Symptom: HTTP works, but HTTPS shows a certificate error, fails to redirect, or returns a default route.
Cause: A certificate resolver, entry point, certificate volume, or router label may have changed or failed to load.
Fix: Compare those settings with the saved configuration, inspect logs for resolver errors, and verify that the certificate storage volume is still mounted. Redeploy the affected resource if its HTTPS labels changed, then test the hostname again.
Rollback procedure
- Open Servers > your server > Proxy > Configuration.
- Replace the current definition with the known-good copy, including the previous image tag and any preserved custom settings.
- Click Save; do not leave the rollback only in the filesystem.
- Click Restart and wait for the proxy to become healthy.
- Check Proxy > Logs for startup and network errors.
- Open representative HTTP and HTTPS domains.
- Redeploy resources if labels, domains, ports, or networks were changed during the failed update.
If the rollback itself does not restore traffic, compare the generated labels and network attachments for an affected resource. The failed update may have changed resource-side data that a proxy rollback alone cannot regenerate.
Quick Recap
Operational checklist
- Correct server selected in Coolify.
- Known-good proxy configuration copied before editing.
- Current image tag and custom settings recorded.
- Entry points, certificate resolvers, volumes, networks, and labels preserved unless intentionally changed.
- Configuration saved on the Proxy Configuration page.
- Proxy restarted after changing the main Compose definition.
- Resources redeployed when labels, domains, ports, proxy behavior, or networks changed.
- At least one HTTP and one HTTPS domain tested.
- Certificate, redirect, application response, logs, labels, and networks checked.
- Rollback copy retained until normal traffic is confirmed.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
