Description
Error Message and Logs
Summary
Sentinel and Proxy containers on a specific server cannot be permanently disabled. Even after unchecking the options in the server configuration and stopping the containers manually, they restart after some time, consuming significant CPU resources.
Expected Behavior
When Sentinel and Proxy are disabled via the UI and stopped via the Proxy tab, they should remain permanently stopped on that server unless explicitly re-enabled.
Actual Behavior
Despite being disabled and stopped manually, the Sentinel and Proxy containers automatically restart after approximately 10–20 minutes. The Proxy container in particular exhibits high CPU usage.
Steps to Reproduce
1. Go to the Servers section.
2. Create a new server (or open an existing one).
3. In the Configuration tab, uncheck the box next to Sentinel.
4. Click Save.
5. Navigate to the Proxy tab.
6. Click the Stop Proxy button.
7. Open a terminal and run "docker stats" to verify that both Sentinel and Proxy containers are stopped.
8. Wait for 10–20 minutes.
9. Run "docker stats" again — the Sentinel and Proxy containers are now running again, with the Sentinel consuming significant CPU resources.
Example Repository URL
No response
Coolify Version
v4.0.0-beta.419
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
debian 11
Additional Information
Impact
This behavior prevents users from disabling unnecessary services on specific servers, leading to unwanted resource consumption and reduced performance.
Requested Fix
Please provide a reliable way to permanently disable Sentinel and Proxy containers per server. They should not restart unless explicitly re-enabled by the user.