[Bug]: Proxy update warning persists on v4.3.21 after upgrading Traefik to v3.7.13
Description and Error Message
On self-hosted Coolify v4.3.21, both managed servers still show Attention required → Proxy: Update available after upgrading their Traefik proxies to v3.7.13.
The original notifications reported a patch update from 3.6.20 to 3.6.25, with 3.7.13 also available on the newer minor branch. The local server was first updated to 3.6.25; docker exec coolify-proxy traefik version confirmed that update. Both servers were subsequently updated to 3.7.13, which the operator confirmed is running, but the warning remains.
The affected server's status dropdown shows:
Server Ready
Proxy Update available
Sentinel In sync
Expected Behavior
Once the running proxy is on the latest supported version and its version check completes, the obsolete proxy update warning should clear. Genuine pending configuration changes or other server warnings should remain visible.
Steps to Reproduce
Observed sequence on the affected installation; not yet reproduced in a clean development environment:
- Run Coolify v4.3.21 with a Traefik
3.6.20proxy and an outstanding patch-update notification for3.6.25(also advertising the3.7branch). - In Servers → Proxy → Configuration, change the image to
traefik:v3.6.25, save, and restart the proxy through Coolify. Confirm the running version in the server terminal. - Change the image to
traefik:v3.7.13, save, and restart the proxy through Coolify. - Confirm that the proxy is running
3.7.13. - Open the server's status dropdown: it still reports Proxy: Update available and Attention required.
The remaining warning affects both the Coolify host and a remote managed server.
Example Repository URL
Not applicable; this concerns Coolify's server/proxy status UI.
Coolify Version
v4.3.21
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Remote managed server, as reported by Coolify: Ubuntu 26.04 LTS, x86_64; Docker Compose 5.1.4. Docker Engine version and the Coolify host's OS version have not been collected.
Screenshots / Visuals
The status dropdown is transcribed above. Original screenshots contain installation-specific details and are not attached.
Additional Information
Related: #11490 and its fix #11496, released in v4.3.11 and already included in this installation's v4.3.21.
One possible uncovered case: clearAppliedTraefikBranchWarning() in v4.3.21 returns early unless the stored warning type is minor_upgrade, while the initial notification here was a patch-update notification. A stale patch_update record might therefore survive that cleanup path. This is a hypothesis, not a confirmed root cause: the stored traefik_outdated_info / detected_traefik_version values and background version-check job state have not been inspected.
This report documents the symptom persisting after the earlier fix; it does not propose clearing warning records without validating the running version. Prepared with AI assistance from the operator's observations and screenshots.
Source: coollabsio/coolify