Update Traefik from Coolify’s dashboard, not by editing the server file alone: open Servers > your server > Proxy > Configuration, back up the generated Compose configuration, review the image tag and custom settings, save the change, then restart the proxy. Redeploy affected resources if labels, domains, ports, or networks changed. Finally, test both HTTP and HTTPS and review the proxy logs before considering the update complete.
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
What the Traefik proxy does in Coolify
Traefik is Coolify’s default integrated reverse proxy. A proxy container runs on each server that hosts Coolify resources and receives public traffic for those applications and services. It terminates or forwards connections, applies the routes generated from your resource settings, handles certificate resolvers, and connects to the Docker networks where destination containers run.
As an Amazon Associate I earn from qualifying purchases.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows 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 reinstallThat server-wide role is why an image update is not the same as updating an ordinary application container. A malformed proxy definition, a missing network, or an incompatible custom setting can affect every public route on that server. Coolify’s documentation also warns that switching proxies temporarily interrupts every public route. Treat an image change as infrastructure maintenance: preserve a rollback copy, make the edit in the UI-managed configuration, restart deliberately, and verify real domains afterward.
Choose the change you actually need
Many requests to “update Traefik” mean changing only the container image tag. Others involve changing command flags, ports, volumes, environment variables, networks, or even moving to a different proxy type. These have different compatibility and outage risks.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
| Change | What changes | Restart needed? | Resource redeploy usually needed? | Main risk to check |
|---|---|---|---|---|
| Routine Traefik image update | The image reference in the saved proxy Compose configuration |
Yes. Main Compose or image changes take effect only when the proxy is restarted. | Not necessarily, provided existing labels, networks, entry points, and certificate settings remain compatible. | Container startup failure or behavior changes between Traefik versions. |
| Proxy configuration change | Command flags, environment variables, ports, volumes, entry points, certificate resolvers, or other Compose settings | Yes. | Often. Redeploy resources when routing labels, domains, ports, proxy behavior, or networks are regenerated. | Invalid YAML, a missing object, a port conflict, or a lost certificate/network definition. |
| Dynamic-file edit | A file under /data/coolify/proxy/dynamic/ |
Normally no; Traefik watches these files. | Only when the change also requires new resource labels, domains, ports, or network connections. | YAML syntax errors or references to objects that do not exist can disable affected routes while Traefik continues running. |
| Broader proxy change or migration | Proxy type, image, flags, ports, volumes, environment, generated labels, or destination networks | Yes, and switching proxies interrupts public routes on the server. | Plan to redeploy resources so labels and network attachments are regenerated. | Incompatible routing assumptions, certificate handling, and a larger rollback scope. |
If your goal is simply to move to the version used by new Coolify configurations, current Coolify documentation identifies Traefik v3.7 for new configurations. Existing custom configurations should be reviewed before you change their image version; do not assume that a custom Compose file is equivalent to a newly generated one.
Prepare a safe rollback before editing
Use the Coolify configuration as the source of truth
The supported persistent location for proxy changes is the Coolify dashboard. The generated file is stored on disk at /data/coolify/proxy/docker-compose.yml, but a direct filesystem edit is not synchronized back to the UI. When Coolify starts or restarts the proxy, it can regenerate that file and overwrite a disk-only change. Make your planned edit in Servers > your server > Proxy > Configuration and save it there.
Copy the known-good configuration
Before changing anything, copy the complete current configuration from the Configuration page and keep it with the maintenance record. Include the image reference and all custom sections, not just the line you intend to alter. If you are allowed to work on the server filesystem, you can also preserve a separate copy of /data/coolify/proxy/docker-compose.yml, but that file is a rollback reference, not the authoritative place to make the edit.
Record the settings that must survive
- Existing entry points and their ports.
- Certificate resolvers and any certificate-related settings.
- Volumes, Docker networks, and network aliases used by the proxy.
- Generated routing labels and any intentional custom labels.
- Environment variables and command-line flags that were added for your installation.
- The domains you will use for post-update HTTP and HTTPS checks.
If production traffic is concentrated on one server, schedule the restart for a maintenance window. A proxy restart can interrupt routes while the container stops, pulls or starts the new image, and reconnects to destination networks. Do not promise a zero-downtime update unless you have separately designed redundancy; the documented behavior is that switching proxies temporarily interrupts every public route on that server.
Update Traefik from the Coolify dashboard
1. Open the server’s proxy configuration
- Sign in to the Coolify dashboard.
- Open Servers.
- Select the server that receives the domains you plan to test.
- Choose Proxy, then open Configuration.
The page identifies the selected proxy, displays the generated Docker Compose configuration, and provides controls to start, stop, restart, save, or reset it. Confirm that you are editing the intended server; proxy settings are server-specific.
2. Find and review the image reference
Locate the Traefik image line in the generated Compose definition. Compare the current tag with the version you intend to run. New Coolify configurations currently use Traefik v3.7, but an existing installation may contain a custom or older tag. Before replacing it, read the rest of the file and compare it with the rollback copy. A version change is safest when entry points, certificate resolvers, volumes, networks, labels, flags, and environment variables remain unchanged.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Do not remove generated routing settings simply because they look repetitive. They are part of how Coolify connects public domains to resource containers. Change unrelated settings only when you have a separate reason and a tested rollback.
3. Preserve custom settings
Check every custom block that is easy to lose during an edit: additional command arguments, environment variables, mounted files, network declarations, and certificate configuration. If your installation uses dynamic configuration files, note their paths under /data/coolify/proxy/dynamic/ and leave them intact unless the update specifically requires a change.
4. Save in Coolify
Save the edited configuration using the page’s Save control. Saving in the dashboard is essential because Coolify uses the UI-managed configuration when it regenerates or restarts the proxy. Do not treat a successful text edit in a shell as completion.
Use Reset only when you deliberately want to remove custom changes from the main Compose file. Resetting is not a harmless refresh: it removes custom changes, so make sure your backup is available before selecting it.
Free tools Windows power users keep installed
One-click scans. No signup required.
5. Restart the proxy when the main definition changed
Use the page’s Restart control after changing the image or any part of the main Compose definition. A restart is required for changes to the image, command flags, environment variables, ports, volumes, or the main /data/coolify/proxy/docker-compose.yml to take effect. Starting or restarting through Coolify also ensures the saved UI configuration is the one being applied.
Watch the proxy status after the restart. If it fails to start, do not repeatedly restart while changing several variables at once. Restore the known-good saved configuration, restart once, and then investigate the specific error in the proxy logs.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
When to redeploy applications and services
A proxy restart and a resource redeploy solve different problems. The restart loads the proxy’s Compose definition and reconnects its container. A resource deployment regenerates the labels and network attachments that tell the proxy where an application or service is located.
Redeploy or restart an affected resource when you changed any of the following:
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →- Compose definitions or image references for the resource.
- Public domains or ports.
- Proxy behavior represented by generated labels.
- Docker networks or the way the resource joins them.
Coolify connects the proxy to destination networks when resources are created, deployed, or when the proxy starts or restarts. If a route still fails after a successful proxy restart, redeploy the resource so its labels and network connection are regenerated. Avoid redeploying every resource automatically when only the Traefik image changed and existing routing metadata is unchanged; target the resources affected by your configuration edit.
Use the Coolify CLI when dashboard access is not practical
Coolify documents this command for updating proxy settings:
coolify server proxy update <server_uuid>The command accepts --proxy-type, including TRAEFIK. Run the help command on the installed CLI before adding other options:
coolify server proxy update --helpCLI options can vary with the installed Coolify version. Confirm the server UUID and review the resulting configuration in the dashboard afterward. The CLI is not a reason to bypass the UI-managed source of truth: verify that the intended proxy type and settings appear under the server’s Proxy Configuration page, then perform the required restart and validation.
Recommended Free Tools
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Verify domains, certificates, and application responses
Test an HTTP domain
Open at least one public HTTP domain routed through the server. Confirm that the expected application responds rather than a proxy error, a default page, or an unrelated service. If your design redirects HTTP to HTTPS, verify that the redirect goes to the correct hostname and does not loop.
Test an HTTPS domain
Open at least one HTTPS domain. Check that the certificate presented is the expected certificate for that hostname, that the connection is trusted by the browser, and that the application response is correct after TLS negotiation. A proxy update can leave the container running while certificate resolvers or entry points are misconfigured, so a green container status alone is not proof that HTTPS works.
Check more than one route when the server hosts several resources
Because the proxy is server-wide, test representative applications on different destination networks or with different entry points when possible. Include a route that uses the certificate resolver most important to your deployment. This catches a network attachment or label problem that a single healthy domain could hide.
Inspect logs and generated labels if a route fails
In Coolify, open Servers > your server > Proxy > Logs and look for startup, provider, certificate, network, or routing errors. Then inspect the affected resource’s generated labels. A missing router or service label points to resource configuration; a missing network connection points to deployment or proxy network attachment; a certificate error points to the resolver or entry-point settings.
Record the exact failing hostname, protocol, response, and time. This makes it easier to distinguish a DNS issue from a proxy route, certificate, or application failure without changing several settings simultaneously.
Troubleshoot the common failure modes
The configuration reverted after a restart
This usually means the change was made only in /data/coolify/proxy/docker-compose.yml or another server-side file. Coolify does not synchronize such edits back to the UI and may overwrite them when it starts or restarts the proxy. Re-enter the change under Proxy > Configuration, save it, and restart from Coolify.
Every application became unreachable
An invalid main Compose definition, a bad port or volume, or a proxy that failed to start can remove access to every route on the server. Restore the known-good configuration you copied before the update and use the Coolify restart control. Once traffic returns, compare the old and new definitions one change at a time. If possible, validate custom changes on a non-production server before applying them to the server carrying live traffic.
The proxy runs, but one route is missing
Inspect the resource’s generated labels and confirm that the resource is attached to the network the proxy can reach. Redeploy or restart that resource to regenerate labels and network connections. If only one dynamic rule is affected, inspect the corresponding file under /data/coolify/proxy/dynamic/ for a YAML syntax error or a reference to an object that does not exist.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsDynamic configuration broke while Traefik stayed running
Watched dynamic files normally apply without a proxy restart, but a malformed file can make its affected routes unavailable while the Traefik process continues. Restore the last working dynamic file, then check Proxy > Logs for the parsing or missing-object error. Do not restart first unless the main Compose definition also changed; a restart will not fix invalid YAML.
HTTP works but HTTPS fails
Compare the HTTPS entry point and certificate resolver with the saved working configuration. Confirm that the HTTPS port and resolver were preserved, then inspect logs for certificate or router errors. If the configuration is correct but the resource labels are stale, redeploy the affected resource and repeat the HTTPS test.
The new image will not start
Stop making additional edits and restore the previous image tag and configuration from your backup in the Coolify Configuration page. Save, restart, and verify one HTTP and one HTTPS route. After service is restored, review custom flags, mounted files, networks, and version compatibility before attempting another controlled update.
Operational checklist
- Confirm the correct server under Servers.
- Copy the complete working proxy configuration.
- Review the image tag and all custom entry points, certificate resolvers, volumes, networks, labels, flags, and environment variables.
- Edit and save under Servers > your server > Proxy > Configuration.
- Restart for image or main Compose changes; do not restart solely for a valid watched dynamic-file edit.
- Redeploy resources when domains, ports, labels, proxy behavior, or networks changed.
- Test at least one HTTP and one HTTPS domain, including redirects, certificates, and application responses.
- Review Proxy > Logs and the affected resource’s generated labels if anything fails.
- Keep the rollback copy until all tested routes remain healthy.
Bottom line
The reliable Coolify workflow is: back up the working definition, change the Traefik image in the dashboard’s Proxy Configuration page, save it there, restart the proxy for main Compose changes, redeploy resources when routing metadata or networks changed, and verify real HTTP and HTTPS traffic. Avoid disk-only edits, preserve custom settings, and keep rollback ready because one proxy configuration serves every public route on that server.
Quick Recap
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.
