Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
To roll back a Coolify application, open the application in the dashboard, choose Rollback, select a retained older image under Available images, and choose Roll back to this image. Then inspect Deployment Logs, confirm the domain and health check, and exercise a critical user flow. This changes the application image only: it does not undo database migrations, restore persistent files, or revert external services. The complete behavior is documented in Coolify’s rollback documentation.
What a Coolify rollback actually changes
Coolify rollback deploys an older application image that is still retained on the server. It is not a rebuild of any arbitrary historical source revision, and it cannot select an image that cleanup has already removed. Coolify’s definition is precise: “A rollback deploys an older application image retained on the server. It does not reverse database migrations, restore persistent storage, or change external services.”
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallThe selected image runs with the application’s current runtime configuration. Environment variables, mounts, resource settings, commands, domains, and health-check settings changed after the image was built are not automatically taken from the older release. Review those settings before starting the rollback, especially if the failed release included configuration changes.
Only images associated with commit and pull-request tags appear in the rollback selector. The image currently running cannot be selected as the rollback target. These limitations explain why a deployment may be visible in history but unavailable as a target.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.
Pre-rollback checks
A rollback is safest when the old application code can operate with everything that remained in place after the failed release. Complete these checks before you queue one:
- Confirm the target image exists. It must appear under Available images. If the list looks stale, use Reload images.
- Check image eligibility. The target must be a retained commit or pull-request image; the running image and deleted images are not selectable.
- Review current runtime settings. Compare environment variables, mounts, commands, ports, resource limits, domains, and health-check configuration with what the older application expects.
- Check schema compatibility. If the failed release changed a database schema, verify that the older code can read the newer schema. Plan a separate database restore or corrective migration if it cannot.
- Identify persistent state. List databases, volumes, uploaded files, queues, object-storage keys, and external APIs touched by the release. None of these are restored by an image rollback.
- Confirm retention settings. Review the application’s Image retention setting and its Images to keep value. Check whether a server-level setting overrides the application value.
- Preserve incident context. Record the failed deployment, target image or commit, operator, reason, and any data-recovery action so the later fix remains traceable.
Roll back from the Coolify dashboard
Use the dashboard when an operator needs to inspect the available images and watch the deployment interactively.
- Sign in to Coolify and open the affected application.
- Select Rollback in the application deployment controls.
- Under Available images, locate the last image that is known to work. If it is not listed, select Reload images and check again.
- Review the image tag and associated source revision. Do not choose the image that is currently running; Coolify excludes it from the selector.
- Select Roll back to this image to queue the deployment.
- Open Deployment Logs immediately. Follow the source revision, image pull or build, generated configuration, and container actions.
- When deployment completes, open the public application domain, inspect container and application logs, check the health-check status, and perform at least one critical user flow such as signing in, creating a record, or completing the service’s primary transaction.
The rollback uses the runtime configuration that exists at the moment you start it. If environment variables, mounts, or health checks were changed in the failed release, correct or intentionally retain those settings before step 5 rather than assuming the older image restores them.
Why a previous deployment is missing
The image was removed by cleanup
Rollback targets are local images retained on the server. Coolify’s image-retention controls determine how many remain: open the application, go to Image retention, and review Images to keep. A server-level retention value can override the application value. Once cleanup removes an image, it no longer appears as a local rollback target; rollback does not recreate it.
The deployment is not an eligible image
The selector supports commit and pull-request image tags. A release represented only by another tag type, or the image currently running, cannot be selected there. Use the API or CLI only when you have a valid target identifier and the corresponding image is still available to Coolify.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
The list has not refreshed
Select Reload images in the rollback view. If the image remains absent after a refresh, treat retention or image eligibility as the likely issue rather than repeatedly submitting the rollback.
Rollback through the API
Automation can call Coolify’s authenticated rollback endpoint:
POST /api/v1/applications/{uuid}/rollbackThe request must include a JSON field named commit. Coolify defines this value as the image tag or commit to roll back to. A successful response includes a deployment_uuid, which gives your automation a deployment record to log and monitor. See the endpoint reference at Rollback application by UUID.
A minimal request shape is:
POST /api/v1/applications/APP_UUID/rollback
Content-Type: application/json
Authorization: Bearer YOUR_TOKEN
{"commit":"TARGET_IMAGE_TAG_OR_COMMIT"}Replace the application UUID, authentication mechanism, and target value with those used by your Coolify instance. The endpoint queues a deployment; it does not by itself prove that the replacement container passed its health check. After receiving the deployment UUID, follow the deployment in Coolify and apply the same domain, log, health, and critical-flow checks as a dashboard rollback.
Rollback with the Coolify CLI
The CLI command is:
coolify app rollback run <uuid>To provide a Git commit SHA explicitly, add the optional --commit argument:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
coolify app rollback run <uuid> --commit <git-commit-sha>The installed CLI’s help output is authoritative for the exact syntax and options of your version; run the command’s help before scripting it if your installation may differ. The CLI still queues an application deployment, so capture its result and inspect deployment logs rather than treating command completion as application recovery. The command reference is at Rollback run.
Dashboard, API, or CLI: which path should you use?
| Method | Operator access | Target identifier | Audit trail | Recovery scope |
|---|---|---|---|---|
| Dashboard | Interactive Coolify UI | Retained image selected under Available images | Deployment Logs and the resulting deployment record | Application image; database, storage, and external services require separate recovery |
| API | Authenticated API client | commit JSON field containing an image tag or commit |
Response includes deployment_uuid; inspect its deployment logs |
Application image; separate data and service restoration remains necessary |
| CLI | Configured Coolify CLI | Application UUID, with optional --commit Git commit SHA |
CLI result plus the queued deployment’s logs | Application image; separate data and service restoration remains necessary |
Choose the dashboard for an urgent, human-supervised incident; the API when a deployment system already authenticates to Coolify and needs a machine-readable deployment UUID; and the CLI for operator scripts or terminal-based runbooks. In every case, the recovery scope is the same image replacement, not a full environment restore.
How to read the deployment logs
Coolify deployment logs show the selected source revision, image build or pull, generated configuration, and container actions. Start at the first failing command, not at the final error line: later messages are often consequences of the first failure. The deployment overview documentation describes this log-driven workflow at Coolify’s deployment overview.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If the source build fails
A failed source build does not replace the running application. Keep the existing service under observation, correct the build or target selection, and retry only after the target image is known to be usable.
If failure occurs after the build
Failures during replacement can depend on the deployment path and health-check configuration. Inspect generated configuration, container start output, and health-check results. Compare the active environment variables, mounts, ports, and commands with the older image’s requirements.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
If the container starts but the application is broken
Check the public domain and application logs, then run a critical user flow. A process that starts successfully can still reject requests because of incompatible schema, missing files, changed secrets, or an external dependency that was not reverted. Those conditions require the relevant data or service recovery procedure, not another image selection.
What rollback does not restore
Image rollback changes application code and image contents only. Plan and execute separate recovery for each stateful or external component:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Database migrations and rows: a rollback does not reverse migrations or restore an earlier database snapshot. Confirm backward-compatible schema and data before using an older image. If compatibility is impossible, follow your database backup and restore plan.
- Persistent volumes and uploaded files: files written to mounted storage remain as they were. Restoring an earlier application image does not remove or recreate them.
- Queues and jobs: queued work is not rewound. Determine whether workers running the older image can safely process existing messages.
- Object storage and keys: objects, buckets, credentials, and external key state are unchanged. Restore or rotate them through their own procedures when required.
- External services: payment providers, email systems, webhooks, DNS, and other services are not changed by the rollback. Reverse an external configuration separately and record that action with the incident.
This separation is why a rollback plan should be designed with each release. A release that changes persistent data needs a tested restore or forward-fix plan before it reaches production.
Common failure modes and fixes
| Symptom | Likely explanation | Action |
|---|---|---|
| Target image is not listed | Cleanup removed it, retention is too low, a server setting overrides the application value, or the image is not a supported commit or pull-request tag. | Refresh with Reload images; inspect Image retention and Images to keep; verify the image’s tag type. A deleted local image cannot be selected. |
| Rollback request succeeds but the service is unhealthy | The old image is running with current runtime settings, or its code is incompatible with current database or persistent state. | Read logs from the first failing command, inspect generated configuration and health checks, and verify environment variables, mounts, schema, and files. |
| Build step fails | The selected source or image cannot complete the build. | Keep the running application under observation, correct the build issue, and retry with a known-good retained image. |
| Application loads but a key action fails | Database rows, queues, files, credentials, or an external service remained at the failed release’s state. | Use the relevant database, storage, queue, credential, or external-service recovery plan; an image rollback alone cannot change that state. |
After the rollback: verification and follow-up
- Confirm the deployment completed and record its deployment identifier or dashboard record alongside the failed release.
- Open the configured public domain and verify that routing reaches the replacement container.
- Review container and application logs for startup errors, repeated restarts, and request failures.
- Check the health-check status and leave enough time to observe the service under normal traffic.
- Execute at least one critical user flow, including authentication or the primary write path where safe.
- Record any separate database, persistent-storage, queue, object-storage, or external-service actions.
- Keep the rollback and incident details linked to the failed release so a later forward fix does not erase the operational history.
Application rollback versus downgrading Coolify itself
Rolling back an application image is different from downgrading the self-hosted Coolify control plane. A Coolify downgrade does not roll back applications, databases, services, managed servers, or their data. It changes the platform that manages them.
Before a control-plane downgrade, Coolify advises creating an instance backup, reviewing release notes, checking active deployments, and considering database compatibility. If the downgrade fails, restoring a known-good instance backup may be required. Follow the dedicated Downgrade Coolify procedure rather than using application rollback as a substitute.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
A practical incident runbook
For a production incident, use this order to avoid changing more state than necessary:
Free tools Windows power users keep installed
One-click scans. No signup required.
- Freeze unrelated releases and identify the failed deployment and the last known-good retained image.
- Check image availability, retention, runtime configuration, schema compatibility, and the separate data-recovery plan.
- Queue the rollback through the dashboard, API, or CLI, recording the selected image tag or commit and any deployment UUID.
- Watch Deployment Logs from the first command through container start and health checks.
- Verify the domain, logs, health status, and critical user flow.
- If application code is restored but state remains wrong, execute the appropriate database, storage, queue, or external-service recovery without assuming another image rollback will fix it.
- Document the result and design the forward fix so the next release remains compatible with existing data and retained-image policy.
Frequently Asked Questions
Can Coolify recreate an image that retention cleanup deleted?
No. Rollback targets are older images retained on the server. Once cleanup removes an image, it is no longer a local rollback target; use a separately preserved image or another recovery plan.
Does a successful rollback API response prove the application is healthy?
No. The API response confirms that Coolify queued the operation and returns a deployment UUID. Check deployment logs, health-check status, the public domain, and a critical user flow.
Will downgrading Coolify restore an application to an earlier release?
No. Downgrading the Coolify control plane is separate from rolling back an application image and does not revert application code, databases, services, managed servers, or their data.
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.
