Coolify 4.3.19
Coolify 4.3.19 introduces an important infrastructure change by making Sentinel mandatory on regular servers, with existing servers automatically enabled and the setting becoming read-only. The release also adds team persistence, Docker restart-limit controls, expanded domain-management options, and numerous deployment, authentication, Docker Compose, S3, and UI fixes. Deployment behavior is improved by pulling image-based Docker Compose services before stopping the existing deployment, reducing downtime and preventing unnecessary service interruption when image pulls fail.
What's new
Coolify 4.3.19 introduces new server, deployment, domain-management, and team capabilities together with numerous reliability and usability fixes.
What's new- Sentinel is now mandatory on regular servers. Existing regular servers are automatically enabled, and the Sentinel enable/disable setting is now read-only.
- Restores each user's last active team after login and provides a team picker when no previously active team is available.
- Adds Docker restart-limit configuration for service applications and databases, including API support for max_restart_count.
- Adds indexing, redirect, and hostname regeneration controls to application, preview, and service domain editors.
- Prevents duplicate two-factor authentication challenge submissions that could result in HTTP 419 errors.
- Adds support for custom usernames in SCP-style SSH Git repository URLs.
- Allows uppercase letters in existing S3-compatible bucket names.
- Improves Docker Compose domain conflict detection and treats HTTP and HTTPS variants as the same routing identity.
- Saves Docker Compose environment files atomically to prevent partial or truncated configuration files.
- Fixes Restart Limit Reached email notifications and several UI, domain, metrics, terminal, and 2FA status issues.
- Upgrades Coolify Sentinel from version 0.0.22 to 1.0.1.
- Image-based Docker Compose services are now pulled before the current deployment is stopped.
- Failed image pulls stop the deployment before the existing workload is interrupted.
- This change reduces deployment downtime and improves deployment reliability.
- DNS checks are now queued only when relevant hostname or URL scheme changes occur.
Sentinel is now mandatory for regular Coolify servers. Existing servers are enabled automatically, and administrators can no longer disable Sentinel through the UI or API. Organizations should verify that Sentinel 1.0.1 starts successfully and remains healthy on all managed servers after the upgrade.
RecommendationOrganizations running Coolify 4.3.18 or earlier should upgrade to version 4.3.19 after standard validation. Particular attention should be given to Sentinel health, Docker Compose deployments, domain routing, S3-compatible storage, and authentication workflows after the upgrade.
๐ฌ Comments (0)
Share any installation issues, compatibility changes, or fixes you noticed.