Rollbacks

A rollback deploys an older application image retained on the server. It does not reverse database migrations, restore persistent storage, or change external services.

Open the application and select Rollback to see the images Coolify can still use.

Before rolling back

Confirm:

• the image for the version you want to restore appears under Rollback
• the current environment variables and runtime settings are compatible with that image
• any database schema changes are backward compatible
• persistent data has a separate restore plan when the release changed it

Deploy an older image

1. Open Rollback.
2. Under Available images, identify the previous working deployment. Select Reload images if the list needs refreshing.
3. Select Roll back to this image. Only commit and pull-request image tags support rollback; the running image cannot be selected.
4. Open Deployment Logs and follow the new operation.
5. Verify the application domain, logs, health check, and critical user flow.

The rollback uses current Coolify runtime configuration with the selected older image. If a variable or mount changed after that image was built, review it before starting.

Image retention

Rollback availability depends on image retention. Set Images to keep under Image retention and select Save changes. A server-level setting can disable retention and override the application value.

An image removed by cleanup no longer appears as a rollback target. A registry may retain another copy, but restoring it requires deploying an available image reference rather than using a missing local rollback entry.