You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No error log is presented, executions keep halted at the end of the step 10 only to be timed out after 10 minutes or so.
It happens at random, it happens with manual executions and with git hooks as well.
Server CPU usage keeps spiked until the timeout like the build process kept going (not an issue with the app itself built with Angular v19).
Version 370 was working fine, but after upgrade past version 377, it stopped working and downgrade to version 370 is not possible due to incompatibilities.
Steps to Reproduce
Update to ver 379
Hit deploy with Nixpacks in node app
Wait about 10 minutes
Get timedout
Example Repository URL
No response
Coolify Version
v4.0.0-beta-377~379
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Ubuntu 22.04
Additional Information
No response
The text was updated successfully, but these errors were encountered:
vitusan
added
🐛 Bug
Reported issues that need to be reproduced by the team.
🔍 Triage
Issues that need assessment and prioritization.
labels
Dec 27, 2024
Error Message and Logs
No error log is presented, executions keep halted at the end of the step 10 only to be timed out after 10 minutes or so.
It happens at random, it happens with manual executions and with git hooks as well.
Server CPU usage keeps spiked until the timeout like the build process kept going (not an issue with the app itself built with Angular v19).
Version 370 was working fine, but after upgrade past version 377, it stopped working and downgrade to version 370 is not possible due to incompatibilities.
Steps to Reproduce
Example Repository URL
No response
Coolify Version
v4.0.0-beta-377~379
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Ubuntu 22.04
Additional Information
No response
The text was updated successfully, but these errors were encountered: