Recommended way to upgrade the bundled Traefik on an existing installation?

[RiKaZaRai]

Hi Dokploy team,

On an existing self-hosted installation, the bundled Traefik does not seem to follow Dokploy upgrades, and I couldn't find a documented procedure to upgrade it. I'd like to confirm the recommended way.

Context

• Dokploy v0.30.8, standalone dokploy-traefik container (not a Swarm service), single server.
• The dokploy-traefik container was created in April 2026 with traefik:v3.6.7 and was never recreated, even though Dokploy was upgraded several times.
• Dokploy v0.30.8 ships TRAEFIK_VERSION || "3.6.25" (packages/server/src/setup/traefik-setup.ts, from fix(security): update Traefik from v3.6.7 to v3.6.25 #4584), so new installs get 3.6.25. Existing installs stay on the version they were created with.
• The troubleshooting page (https://docs.dokploy.com/docs/core/troubleshooting/instance) shows how to recreate the container manually, but it pins traefik:v3.6.7, which is affected by the advisories fixed in fix(security): update Traefik from v3.6.7 to v3.6.25 #4584.

What I did

Reading the code, settings.writeTraefikEnv (Settings → Web Server → Traefik → Environment) calls writeTraefikSetup → initializeStandaloneTraefik. That recreates the container with the current TRAEFIK_VERSION and reconnects the services. I saved the environment unchanged. Traefik came back on v3.6.25 with the same mounts, ports and networks, and no errors in the logs. All 74 routed domains returned the same HTTP status codes and certificates as before.

Questions

1. Is re-saving the Traefik environment (or toggling the dashboard or ports) the intended way to upgrade Traefik on existing installs? Or is there a supported command or button I missed?
2. Could the docs mention this? The troubleshooting example could also use TRAEFIK_VERSION instead of a fixed v3.6.7.
3. Is there a plan for Traefik 3.7.x? The 3.6 branch has stopped receiving security fixes: the September/October 2026 advisories are only patched in 3.7.13+ and 2.11.57+. Is setting TRAEFIK_VERSION=3.7.x on the Dokploy service supported, or not recommended yet?

Thanks for Dokploy!

[charles-benedito]

hey, ur reading of the code matches what i see and afaik there's no dedicated upgrade button. in apps/dokploy/server/api/routers/settings.ts the only traefik mutations are reloadTraefik, which just restarts the existing container, and toggleDashboard / writeTraefikEnv, which both go through writeTraefikSetup. that calls initializeStandaloneTraefik, which pulls traefik:v${TRAEFIK_VERSION}, force removes dokploy-traefik and recreates it with the same mounts and ports. so re-saving the env (or toggling the dashboard) is effectively the upgrade path right now.

for 3.7, TRAEFIK_VERSION is just process.env.TRAEFIK_VERSION || "3.6.25" in packages/server/src/setup/traefik-setup.ts, so setting it on the dokploy service should be picked up on the next recreate. whether 3.7 is recommended yet is a maintainer call tho, i haven't seen anything in the repo about it.

https://github.com/Dokploy/dokploy/blob/canary/packages/server/src/setup/traefik-setup.ts