[Bug]: App keeps crashing

[haysquareA]

Error Message and Logs

Hello, I keep getting something like (24x restarts)
Stopped after reaching restart limit (24/10). then the server stop/exit on production, no idea what the issue is because everything works fine and it only happens if I have the cooly opened, if no one visit it for days it will continue to run until we log in to it and immediately the server will exit, it doesn't do that before until recent update and this has been very frustrating especially as it's production

Steps to Reproduce

Example Repository URL

No response

Coolify Version

v4.1.2

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

No response

Additional Information

No response

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• [Bug]: Restart threshold goes beyond the max amount set #10761

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[Cinzya]

it only happens if I have the cooly opened, if no one visit it for days it will continue to run until we log in to it and immediately the server will exit

Is Coolify installed on that same server? Have you checked the resource usage yet on your server? This sounds like as if you are hitting resource limits as soon as there is traffic. It does slightly increase when you open the Coolify Dashboard.

[haysquareA]

No I'm not, not even upto 50% of the resource server

That's it, it just exited after 10x and the whole project server down

[haysquareA]

@Cinzya please anyway I can downgrade to previous version, this current version is the issue, I have 5 different servers using coolify , I updated 3 to the latest version and all three are failing as the screen shot I shared, while the other two works perfectly

[Cinzya]

@haysquareA I am personally not able to replicate your problem. We need a reproducible example repo from you. Otherwise we cannot fix, if it's actually a problem with Coolify itself.

Can you also share the container logs (not deployment logs)?
Under the Advanced settings you can set the restart count to 0 then it will continue restarting.

[haysquareA]

Thank you so much, I believe this is exactly what I need.
thanks

[mr-tm]

@Cinzya Same thing happening with our container. When going to website it says (no available server).
Need to redeploy to make it work again. I have noticed it happening few times with the latest coolify version 4.1.2.
The container keeps restarting and stops after reaching limit. I think it happens when coolify panel is used, not by itself.

[Cinzya]

@mr-tm Can you check the following for any errors during that window and provide their outputs:

1. Container logs (under the Logs tab, not Deployments). You might need to disable the restart count as mentioned above already.
2. Your Server metrics: CPU, RAM, Disk and Network usage. docker stats gives a breakdown per container, htop per process. df -h shows disk usage.
3. The Proxy logs (under Servers > [YourServer] > Proxy > Logs). Errors like no available server, Bad Gateway or similar, can indicate a problem with the proxy. You could potentially adjust the log level to get a more verbose output by adding a --log.level=DEBUG in the commands section of the proxy configuration.
4. Your apps container data: docker inspect your-container-name. Make sure to censor sensitive data, it will print your environment variables.
5. Docker deamon logs: journalctl -xu docker.service