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.

When the application does not push to a Docker registry, an image removed by cleanup no longer appears as a rollback target.

Images in a Docker registry

When the application pushes its images to a Docker registry, Available images also shows the commit images of the last 10 successful production deployments. Thus, you can roll back to an image that cleanup removed from the server.

Coolify shows these images when:

• General > Docker Registry > Docker Image has a value
• the application builds from a Git source (not the Docker Image or Docker Compose build pack)
• the application does not use a Dockerfile that you pasted into Coolify, because those deployments always push the latest tag

Coolify counts each commit one time. Preview deployments are not included.

An image that is only in the registry has the In registry badge, and its date shows when Coolify deployed it (Deployed), not when Docker built it (Built). When the server and the registry both have the same tag, the list shows the image on the server.

When you roll back to an image that the server does not have, the deployment pulls it from the registry first. The deployment log shows not found on the server. Pulling it from the Docker registry. For a private registry, log in to the registry on the server before you roll back. Refer to Authenticate a private registry.

The API endpoint GET /applications/{uuid}/rollback-images returns the same list. Each image has a source field: local for an image on the server, or registry for an image that is only in the Docker registry.