[Bug]: "Traefik Proxy Outdated" email notification not triggered for external server

Error Message and Logs

Description

The "Traefik Proxy Outdated" notification (email) was never sent, even though the Traefik proxy on an external (non-main) server was running v3.6.10 while v3.6.11+ was available. The outdated state persisted for over 6 weeks (since March 6). The warning banner on the Proxy Configuration page did show correctly — but no email was sent.

Setup

Coolify v4.0.0-beta.473 on the main server (full Coolify installation)
External server managed by Coolify, running only the proxy and managed resources
Traefik image tag on both servers: traefik:v3.6 (floating tag)
Main server Traefik: v3.6.13 (up to date, floating tag pulled latest)
External server Traefik: v3.6.10 (container not recreated since March 6)
Email notification channel: configured and working (test email received successfully)
"Traefik Proxy Outdated" event: enabled for email

Expected behavior

An email notification ("Coolify: Traefik proxy outdated on 1 server(s)") should be sent when the external server's running Traefik version is behind the latest available patch.

Actual behavior

No email was sent!
The outdated proxy was only discovered by manually visiting the Proxy Configuration page of the external server in the Coolify UI, where the yellow "Traefik Patch Update Available" banner was displayed. And this message provided a lower "new version" than the most current version (discovered by check)

Possible root cause

The outdated-check may only run against the main server, or it may compare the configured image tag (traefik:v3.6) rather than the actually running container version — since the floating tag technically resolves to "latest," the check might consider it up to date even though the running container was built from an older pull.

Steps to Reproduce

1. setup at least two server, both managed through the coolify UI; one will be automatically the MAIN server.
2. update the main server with a new full installation (including a new proxy module version)
3. visit regularly the proxy page of the other server, awaiting "the message" [loop]
   if, then:
4. check message
5. check version tag by

docker inspect coolify-proxy --format '{{.Config.Image}}'
docker exec coolify-proxy traefik version

on both instances, seeing a difference between MAIN and OTHER in version tag. If no email reached for OTHER, than you have it

Example Repository URL

No response

Coolify Version

v4.0.0-beta.473

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04

Additional Information

No response

Start at the Proxy Configuration page behavior and the enabled “Traefik Proxy Outdated” email event, comparing checks for the main and external servers. Use the supplied docker inspect and traefik version commands on both instances to verify configured versus running versions. Done means an outdated external proxy reliably triggers the expected email without requiring a page visit.