-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Open
Labels
🔍 TriageIssues that need assessment and prioritization.Issues that need assessment and prioritization.
Description
Error Message and Logs
Even when:
- the new container is created correctly,
- the application starts,
- the healthcheck passes (healthy),
- the rolling update completes,
Coolify still marks the deployment as failed and removes the newly deployed version.
This happens after the healthcheck succeeds.
New Logs (2025-Dec-12)
Relevant excerpt from the deployment logs:
2025-Dec-12 10:09:51.700518
New container started.
2025-Dec-12 10:09:51.720221
Waiting for healthcheck to pass on the new container.
2025-Dec-12 10:09:57.186612
"healthy"
2025-Dec-12 10:09:57.621911
New container is healthy.
2025-Dec-12 10:10:01.211972
Rolling update completed.
Immediately after the rolling update completes, the deployment fails:
2025-Dec-12 10:10:01.669615
Deployment failed: SQLSTATE[42P01]: Undefined table: 7
ERROR: relation "webhook_notification_settings" does not exist
(Connection: pgsql, SQL:
select * from "webhook_notification_settings"
where "webhook_notification_settings"."team_id" = 0
and "webhook_notification_settings"."team_id" is not null limit 1)
Full error details:
Error type: Illuminate\Database\QueryException
Error code: 42P01
PDOException: SQLSTATE[42P01]: Undefined table: 7
Location: /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php
After this error:
Deployment failed. Removing the new version of your application.
Steps to Reproduce
Example Repository URL
No response
Coolify Version
454
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
No response
Additional Information
No response
coderabbitai and Inaztm
Metadata
Metadata
Assignees
Labels
🔍 TriageIssues that need assessment and prioritization.Issues that need assessment and prioritization.