The correct Uptime Kuma update procedure depends on how it was installed. A Docker deployment is updated by pulling a newer image and recreating the container with the same persistent data volume. Docker Compose uses docker compose pull followed by a forced recreation. A Git/Node.js installation requires fetching tags, checking out the selected release, reinstalling production dependencies, downloading the prebuilt frontend, and restarting PM2. A move from v1 to v2 is a major migration: back up the data directory first, use the v2 image, and watch the migration logs.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
The official documentation does not establish one globally latest release for October 15, 2026. Select and verify the image tag or Git tag you intend to run before changing a production monitor.
As an Amazon Associate I earn from qualifying purchases.
Choose the update path that matches your installation
Do not mix procedures. The commands and rollback options are different for a container, a Compose-managed service, and a process running directly from a Git checkout.
| Installation | Routine update action | Where your data must remain | Special scope |
|---|---|---|---|
| Docker container | Pull the selected image, stop and remove the old container, then run a new container with the same volume mapping | The existing persistent local volume mapped to /app/data |
Use the v2 image for a v1-to-v2 migration |
| Docker Compose | Run docker compose pull, then docker compose up -d --force-recreate |
The data volume or bind mount declared in docker-compose.yml |
Confirm the Compose file’s image tag before pulling |
| Git/Node.js installation | Fetch tags, check out the deliberately selected tag, install production dependencies, download the distribution, and restart PM2 | The installation’s data directory, protected by a restorable backup | Direct non-Docker v1-to-v2 migration is not supported |
Prepare before changing anything
An update is only reversible if you know what is running and can restore its data. Complete these checks while the current instance is still healthy.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
- Record the current Docker image and tag, Compose image reference, or Git commit/tag.
- Identify the persistent data location. For Docker, preserve the volume mapped to
/app/data; for a non-Docker installation, locate thedatadirectory used by that checkout. - Create a backup of the data directory before a major-version migration and verify that the backup can actually be restored.
- Confirm the target image tag or Git release tag. The
2.5.6value shown in the non-Docker example is an example checkout, not proof that it is the newest release. - Check that the deployment uses a local Docker volume. The installation documentation says local volumes are supported and that alternatives such as NFS are not supported.
- Schedule enough time for the service to stop, the image to download, and the application to start. A new image may not be immediately available after a release.
Keep the old tag, the backup location, and the exact commands used in your change record. Those details make a rollback possible if the new process fails to start or monitors do not load.
Update a standard Docker installation
The Docker procedure keeps the existing data by recreating only the container. The image changes; the volume containing Uptime Kuma’s configuration and monitor data does not.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
1. Pull the selected v2 image
docker pull louislam/uptime-kuma:2The :2 tag selects the v2 image stream. If your operating procedure requires a specific release tag, substitute the tag you have deliberately verified instead of assuming that a floating tag represents a particular point release.
2. Stop and remove the current container
docker stop uptime-kuma
docker rm uptime-kumaRemoving the container does not remove a separately named volume. Do not add a volume-removal command: deleting the data volume would defeat the preservation step.
3. Recreate the container with the same storage and networking
docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:2This documented example exposes container port 3001 on host port 3001 and mounts the named volume uptime-kuma at /app/data. If your original container used a different host port, volume name, bind mount, restart policy, or other custom option, preserve those values rather than copying the defaults above. The essential rule is that the replacement container must point at the same persistent data location.
4. Allow time for the image to become available
The project update documentation warns that each new release takes time to build into a Docker image. If a pull cannot find the expected image immediately after a release, wait and retry rather than switching tags at random.
Windows 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 reinstallOutdated 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 matchUpdate a Docker Compose deployment
Compose recreates the service from the definition in docker-compose.yml. Run the commands from the directory that contains that file.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
1. Change to the Compose directory
cd "<YOUR docker-compose.yml DIRECTORY>"Use the real directory path. Running the commands elsewhere can update a different project or fail because no Compose file is present.
2. Check the image tag in the Compose file
Before downloading anything, inspect the Uptime Kuma service definition and make sure its image points to the release stream or version you intend to deploy. This is the control point for Compose updates; editing an unrelated service does not update Uptime Kuma.
3. Pull the new image
docker compose pullCompose downloads the image referenced by the file. It does not, by itself, replace a running container.
4. Force recreation in detached mode
docker compose up -d --force-recreateThe forced recreation ensures that the service is rebuilt from the pulled image. Because the Compose file retains the existing volume or bind-mount declaration, the application starts with the same data location.
Update a non-Docker Git and Node.js installation
The official non-Docker procedure assumes that Uptime Kuma is installed from its Git directory and managed by PM2. Node.js, Git, and PM2 are listed as requirements. This path involves both the backend dependencies and the prebuilt frontend distribution, so skipping a step can leave an apparently running process with incomplete files.
1. Enter the Uptime Kuma directory
cd <uptime-kuma-directory>Replace the placeholder with the directory containing the checkout and its package files.
2. Fetch all branches and release tags
git fetch --all --tagsFetching tags makes the release you intend to use available locally. It does not choose a release for you.
Recommended Free Tools
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
3. Check out the deliberate target tag
git checkout 2.5.6 --forceThe documentation uses 2.5.6 as an example. It is not an assertion that 2.5.6 is the globally latest version at this timestamp. Replace it with the verified tag selected for your change. The --force option makes the checkout match the tag even when the working tree contains local changes, so preserve any required local modifications before running it.
4. Install production dependencies
npm install --omit dev --no-auditThis installs the production dependency set while omitting development packages and disabling the audit step used by this documented command.
5. Download the prebuilt frontend
npm run download-distRun this after dependency installation so the checkout has the distribution files expected by the selected release.
6. Restart the PM2 process
pm2 restart uptime-kumaThe restart makes PM2 launch the newly checked-out code. A successful command only shows that PM2 accepted the restart; you still need to verify the web interface and monitors.
Free tools Windows power users keep installed
One-click scans. No signup required.
Understand the v1-to-v2 migration
Moving from Uptime Kuma v1 to v2 is not an ordinary patch update. Treat it as a schema and application migration with a tested backup and a planned observation window.
Supported migration sequence
- Stop the running Uptime Kuma container.
- Back up the complete
datadirectory. - Change the container image to
louislam/uptime-kuma:2. - Start the container with the existing persistent data attached.
- Follow the container output with
docker logs -f uptime-kumaand watch for migration activity or startup errors.
The migration guide specifically describes this Docker sequence. It does not support a direct v1-to-v2 migration using the non-Docker update procedure.
Node.js requirement for v2
For v2, the migration documentation identifies Node.js 20.4 as the minimum supported version. Check the runtime before attempting a non-Docker v2 installation, but do not use the non-Docker procedure as a direct v1-to-v2 migration path.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Rootless image caution
Rootless images are not recommended for upgrading from v1 to v2 because startup problems may occur. Use the migration approach documented for the standard image, retain the backup, and inspect logs before declaring the migration complete.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Verify the update after the process restarts
Verification should test both the process and the data that matters to monitoring.
- Confirm that the Docker container or PM2 process is running after the restart.
- Open the Uptime Kuma web interface on the configured host and port.
- Confirm that the existing dashboard, settings, and monitor list load instead of presenting an empty first-run setup.
- Open representative monitors and check that their current status and history are visible.
- Review container or process logs for migration messages, repeated crashes, permission errors, or database failures.
- Leave the old image tag, Git reference, and backup available until the updated instance has operated normally for the observation period your team requires.
These checks are operational safeguards rather than a claim of a live test. They are the minimum evidence that the replacement process is using the intended data and serving the expected application.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Rollback planning and recovery
A rollback has two independent parts: restoring the software version and restoring data if a migration changed it. Keep the prior image or Git tag known before updating, and do not overwrite the only backup with post-migration data.
Docker rollback decision
If the new container will not start, stop it, recreate the container from the previously recorded image tag, and attach the same persistent volume. If the v1-to-v2 migration has modified data and the older application cannot read it safely, stop and restore the pre-migration data backup before starting the older version. The correct sequence depends on whether the failure is only a process startup problem or a data-format change.
Compose rollback decision
Change the Compose file back to the previously recorded image tag, pull that image, and run the same forced-recreation command. Preserve the existing volume declaration. If the migration changed stored data, use the verified backup rather than repeatedly switching images against an uncertain data state.
Non-Docker rollback decision
Check out the prior recorded Git tag, reinstall production dependencies, run the distribution-download step, and restart PM2. For a v1-to-v2 attempt, remember that the documented direct non-Docker migration is unsupported; restoration of the backed-up data and a supported Docker migration path may be required.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Troubleshoot common update failures
The image cannot be pulled immediately after release
New releases require time to build into a Docker image. Wait for the image publication to complete, then retry the pull. Do not delete the persistent volume while waiting.
The web page shows a first-run setup
This usually indicates that the replacement process is pointed at a different or empty data location. Recheck the Docker volume name and /app/data mapping, or the data-directory path used by the non-Docker process. Stop the new process before changing storage mappings so you do not create additional data in the wrong location.
The container starts and exits repeatedly
Read the startup output, confirm that the intended image tag was used, and verify the data mount and permissions. During v1-to-v2 migration, follow docker logs -f uptime-kuma specifically for migration errors. For a rootless v1-to-v2 attempt, move to the documented standard-image procedure rather than repeatedly restarting the rootless image.
The non-Docker process restarts but the frontend is incomplete
Return to the selected Git checkout, run npm install --omit dev --no-audit, run npm run download-dist, and then restart PM2. Also confirm that the host meets the documented Node.js requirement for v2.
Existing monitors are missing
Stop the replacement process and verify the data source before making further changes. A missing monitor list is consistent with an incorrect or empty volume/data-directory mapping, not proof that the update deleted the original configuration. Use the pre-update backup if the data location was altered or a migration cannot be safely reversed.
How to choose a target version safely
“Latest” is a moving label, while an update requires a reproducible target. The official material available for this procedure does not establish the exact globally latest release on October 15, 2026. For production, record the exact image tag or Git tag you selected, the date of the change, and the deployment method.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →- Use a release tag when you need an auditable, repeatable deployment.
- Use the image stream documented by your installation procedure only when your maintenance policy accepts its update behavior.
- Do not treat the example checkout
2.5.6as a current-release guarantee. - For v1-to-v2, plan a migration rather than a routine update and retain the backup until verification is complete.
Quick command reference
Docker
docker pull louislam/uptime-kuma:2
docker stop uptime-kuma
docker rm uptime-kuma
docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:2Docker Compose
cd "<YOUR docker-compose.yml DIRECTORY>"
docker compose pull
docker compose up -d --force-recreateGit/Node.js with PM2
cd <uptime-kuma-directory>
git fetch --all --tags
git checkout 2.5.6 --force
npm install --omit dev --no-audit
npm run download-dist
pm2 restart uptime-kumaIn the non-Docker block, replace 2.5.6 with the verified release tag you intend to deploy. In the Docker and Compose blocks, retain your original custom port and storage mappings.
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.
