To roll back a Coolify application, open the application in the dashboard, choose Rollback, select a retained image under Available images, and click Roll back to this image. Coolify then deploys that older application image with the runtime configuration currently defined for the application. Check the deployment logs, domain, health check, and a critical user flow immediately afterward.
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
This is an application-image rollback, not a complete release undo. It does not reverse database migrations, restore persistent files, rewind queues or object storage, or change an external service. Those systems need their own restore or compensation plan.
As an Amazon Associate I earn from qualifying purchases.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhat Coolify rollback actually changes
Coolify’s rollback feature selects an older application image that is still retained on the server and queues a new deployment using it. The image contains the older application code and build output. Coolify does not rebuild an arbitrary historical source revision during this action, and an image deleted by cleanup cannot be selected later.
Coolify defines the boundary plainly: A rollback deploys an older application image retained on the server. It does not reverse database migrations, restore persistent storage, or change external services.
See the official rollback documentation.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
The selected image runs with the application’s current Coolify runtime configuration. Environment variables, mounts, commands, ports, proxy settings, and health-check settings may have changed since that image was built. An older image can therefore start with newer configuration, or fail because that configuration is incompatible. Review those settings before you start rather than assuming rollback recreates the entire earlier release.
Check these conditions before starting
A rollback is safest when the target image is present, the runtime settings still fit that image, and the data layer can be used by the older code. Use this checklist before selecting an image:
- Target image: Confirm that the intended previous deployment appears under Available images. A running image cannot be selected as the rollback target, and only images associated with commit and pull-request tags are available in the selector.
- Runtime compatibility: Compare current environment variables, mounted paths, startup commands, exposed ports, resource settings, and health checks with what the older release expects.
- Schema compatibility: Determine whether the release you are leaving applied migrations or changed data formats. The older code must be able to read the current schema and records, or you need a separate database restore or forward-fix plan.
- Persistent data plan: Identify recovery steps for volumes, uploaded files, queues, object-storage keys, and other state. The image rollback will not restore any of them.
- Incident record: Capture the failed deployment identifier and relevant logs. Keep the rollback deployment linked to that incident so a subsequent fix does not erase the history.
Dashboard procedure
1. Open the application and rollback view
Sign in to Coolify, open the affected application, and select Rollback. The page lists images that remain on the server and can be used as deployment targets.
2. Refresh the image list if necessary
Under Available images, use Reload images when the expected deployment is missing from the list. Refreshing only asks Coolify to re-read images that still exist locally; it cannot recreate an image that retention cleanup has already removed.
3. Identify the previous working image
Match the image tag or commit information with the last known-good deployment. Do not choose solely by recency: a later image may have been built successfully while the application was already malfunctioning, and the currently running image is not an eligible selector target.
4. Start the rollback
Select the target and choose Roll back to this image. Coolify queues a deployment using that image and the application’s current runtime configuration. This is a new deployment operation, not a silent switch of the running container.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
5. Inspect deployment logs
Open Deployment Logs for the rollback. Confirm the selected source revision, image pull or build actions, generated configuration, and container operations. If an operation fails, begin with the first failing command in the log; later errors are often consequences of that initial failure.
6. Verify the live application
After the deployment reports success, test the public application domain, review container and application logs, confirm health-check status, and exercise at least one critical user flow such as sign-in, checkout, data creation, or an API request that matters to your service. A container can be running while the application remains unusable, so do not treat a green deployment status as the only verification.
Why the previous deployment may be missing
Image retention removed it
Rollback depends on the image still being stored on the server. In the application’s Image retention settings, review Images to keep. Also check whether a server-level retention value overrides the application’s value. Once cleanup removes an image, it no longer appears as a local rollback target; changing retention later does not reconstruct it.
The image is not an eligible tag
The rollback selector supports images tagged from commits and pull requests. A deployment built or published under a different tagging scheme may not appear even if related source code still exists. The selector also excludes the image currently running.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The list is stale
Use Reload images before concluding that a target is unavailable. If it remains absent after a refresh, verify retention and the image’s tag on the server rather than repeatedly retrying the dashboard action.
Retention planning for future rollbacks
Retention is a recovery control, not merely a storage preference. Set Images to keep high enough to cover your normal release frequency and the time needed to detect incidents. A value that preserves only the latest image can leave no usable target after a bad release. Account for server-level overrides when documenting the policy, because an application setting may not be the effective limit.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Retention protects only deployable application images. It does not create database backups, volume snapshots, object-storage versions, or copies of external service configuration. Pair image retention with backups and a tested restore procedure for every persistent system changed by a release.
Database migrations and persistent state
Rolling back the image does not roll back a migration. If the failed release added a column, changed an enum, rewrote records, or removed a field, the older application may encounter a schema or data shape it does not understand. The container may pass its health check while individual requests fail when they touch the changed state.
Before selecting an image, establish whether the migration is backward compatible. Expand-and-contract designs, in which new code and old code can both operate during a transition, are generally easier to recover from than destructive migrations. If compatibility is not assured, stop and use the database system’s documented restore, down-migration, or forward-fix process. Take care with irreversible data changes: an image rollback cannot recreate deleted rows or restore old values.
The same boundary applies to non-database state. Persistent volumes, uploaded files, queue messages, object-storage keys, caches with business meaning, and records held by external services remain at their current state. Restore or reconcile each system separately, and record which systems were changed during the failed release.
Rollback through the API
For automation, use the authenticated endpoint POST /api/v1/applications/{uuid}/rollback. The required JSON field is commit; it identifies the image tag or commit to deploy. Coolify returns a deployment_uuid when the rollback request is accepted. Consult the endpoint reference for authentication and request details: Rollback application by UUID.
A minimal request has this shape (replace the UUID and target identifier with values from your instance):
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
POST /api/v1/applications/{uuid}/rollback
Content-Type: application/json
Authorization: Bearer <token>
{"commit":"<retained-image-tag-or-commit>"}The endpoint queues the same kind of deployment operation as the dashboard. Store the returned deployment_uuid with the incident, then follow the deployment in Coolify and perform the same domain, log, health-check, and critical-flow verification. An HTTP success response means the request was accepted; it does not by itself prove that the replacement container is healthy.
Rollback through the CLI
The Coolify CLI command is:
coolify app rollback run <uuid>You can optionally provide a Git commit SHA:
coolify app rollback run <uuid> --commit <git-commit-sha>The installed CLI’s help output is authoritative for the exact version you use, including authentication, option names, and output formatting. Use the command’s result to identify the queued deployment, then inspect logs and verify the running application rather than treating command completion as proof of recovery. The command reference is available at Rollback run.
Choosing the dashboard, API, or CLI
All three interfaces queue a deployment; they differ mainly in how an operator identifies the target and records the action.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →| Interface | Operator access | Target identifier | Audit trail | Recovery scope |
|---|---|---|---|---|
| Dashboard | Interactive Coolify UI | Retained image shown under Available images | Deployment logs and the resulting deployment record | Application image only; restore data and services separately |
| API | Authenticated automation or script | commit field containing an image tag or commit |
Response includes a deployment_uuid, followed by deployment logs |
Application image only; restore data and services separately |
| CLI | Authenticated command-line session | Application UUID, with optional Git commit SHA | CLI output plus the resulting deployment logs | Application image only; restore data and services separately |
Use the dashboard when an operator needs to inspect available images visually, the API when a controlled runbook or automation system must initiate the action, and the CLI when the operator already works from a terminal. Whichever interface you choose, preserve the deployment identifier and logs.
Reading logs and handling failures
Coolify deployment logs show the selected source revision, image build or pull, generated configuration, and container actions. When the rollback fails, read from the top and locate the first command that returned an error. This separates a source or image problem from a failure during replacement.
Failure during source build or image preparation
A failed source build does not replace the currently running application. Check the source revision, image availability, registry access, and build command shown in the log. Correct the underlying issue or select another retained image before retrying.
Failure after the image is prepared
Errors during container replacement can depend on the replacement path and health-check configuration. Review generated environment values, mounts, ports, startup commands, and health-check endpoints. Confirm that the older process listens where the current proxy expects it and that required secrets or files are still mounted.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Container starts but requests fail
Check application logs and exercise a critical flow instead of relying on container status. A schema mismatch, changed external API, missing persistent file, or incompatible environment variable can surface only when a request reaches that code path. If data was changed by the failed release, follow the separate restore or forward-fix plan.
Rollback versus downgrading Coolify itself
Do not confuse an application rollback with downgrading the self-hosted Coolify control plane. A control-plane downgrade changes Coolify, not the deployed applications, databases, services, managed servers, or their data. The procedure and risks are different.
Before downgrading Coolify, create an instance backup, read the relevant release notes, check active deployments, and consider database compatibility. Coolify notes that restoring a known-good instance backup may be necessary if the downgrade fails. Follow the dedicated guidance at Downgrade Coolify. Do not use a control-plane downgrade as a substitute for restoring an application’s image or data.
Operational record after recovery
Once the application is stable, retain the rollback deployment UUID or dashboard record, the selected image tag or commit, the incident timeline, and the verification results. Link the rollback to the failed release in your change or incident system. Record any database, volume, queue, object-storage, or external-service actions separately. This history lets you prepare a forward fix without losing the evidence of what changed and which image restored service.
For background on what deployment logs contain and how Coolify executes deployment operations, see the deployment overview.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
