[Bug]: Container Status Changes notification not sent on docker kill/crash

[mattiacolombomc]

Error Message and Logs

Environment

• Coolify version: 4.0.0-beta.471
• OS: Ubuntu 24, aarch64
• Notification: Telegram and Pushover

Description

Container Status Changes notification is enabled in Settings → Notifications → Telegram and Pushover, but no notification is sent when a container crashes or is killed via docker kill.

Notification IS sent when:

• A new deployment succeeds
• A container restarts after a crash (the restart notification arrives, not the crash)

Notification is NOT sent when:

• Container is killed with docker kill <container_name>
• Container crashes unexpectedly

Steps to Reproduce

Steps to reproduce

1. Enable "Container Status Changes" in Telegram and Pushover notification settings
2. Run docker kill <container_name> on any running container managed by Coolify
3. No Telegram or Pushover notification received
4. Container restarts → notification received for the restart

Expected behavior

Notification should be sent immediately when container goes down, not only when it comes back up.

Example Repository URL

No response

Coolify Version

4.0.0-beta.471

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04.4 LTS (Noble Numbat)

Additional Information

No response

[mattiacolombomc]

may be related to #8269

[mattiacolombomc]

This seems to be a broader issue than just Telegram. I tested with Pushover as well and the same behavior occurs.

Warning

@ShadowArcanist I want to flag this as a concern — this feels like a core feature for a self-hosting platform. Knowing when a container goes down is critical for production reliability. Without this, users have no way to be alerted of outages unless they set up external monitoring tools.

What works:

• Deployment success/failure notifications ✅
• Container restart notifications ✅

What doesn't work:

• Container going offline / stopping — no notification sent ❌

This happens regardless of the notification channel (tested Telegram and Pushover) and regardless of how the container is stopped:

• Via docker kill <container> from terminal
• Via the Stop button in Coolify UI

It seems the "container offline" event itself is not being fired/detected, not a notification delivery issue. The restart event fires correctly when the container comes back up, but the preceding "down" event is missing.

[ShadowArcanist]

Hey @mattiacolombomc the code that triggers the notification for container exits are commented out by Andras in a commit year ago.

So right now notifications are actively sent in these scenarios:

• Coolify Proxy container restart
• TCP Proxy restart for public databases

He mostly disabled it due to some issue that time, I have notified Andras about this issue, will post an update here soon.

[mattiacolombomc]

Thank you @ShadowArcanist !

Are there anyworkaround at the moment without using external container or services? Thanks again

[ShadowArcanist]

Thank you @ShadowArcanist !

Are there anyworkaround at the moment without using external container or services? Thanks again

As far as I know, no.

I personally only use backup related notifications on Coolify, for uptime/availability checking I use external tool.

[ShadowArcanist]

Got an update from Andras few days ago (forgot to update here)..

This notification feature needs an refactor to prevent notification spam and the refactor didn't happened yet..

[mattiacolombomc]

@ShadowArcanist thank you for the update. maybe a flag would be a good temporary solution? I personally prefer spam of such important things than no notification

or maybe as soon as I got some time I could work on a PR...

[ShadowArcanist]

@ShadowArcanist thank you for the update. maybe a flag would be a good temporary solution? I personally prefer spam of such important things than no notification

or maybe as soon as I got some time I could work on a PR...

The best solution I can think of for now is to setup an external uptime monitor like uptime kuma or beszel.

I can add a notice on the UI about this so users will be aware of this