The safest Ubuntu LTS upgrade is a rehearsed change, not a single command. For a VPS you can reproduce from code or an image, deploy a new server with the target LTS, restore data, move traffic, and keep the old server for rollback. Use an in-place do-release-upgrade only when the existing machine contains configuration that cannot be recreated. In either case, take a restorable backup, confirm the supported release path, keep console access available, and schedule a maintenance window.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
Choose the safer upgrade strategy first
Ubuntu LTS releases are upgraded sequentially. Canonical supports moving from one supported release to the next LTS in order; you cannot safely jump over an LTS without performing the intermediate upgrades. Older LTS and interim systems may therefore need staged upgrades before reaching a newer target, as noted in the Ubuntu 26.04 release documentation.
As an Amazon Associate I earn from qualifying purchases.
Outdated 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 matchWindows 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 reinstallThere are two valid operating models. A redeployment replaces the VPS with a fresh image and migrates workloads. An in-place upgrade changes the operating system, packages, repositories, services, and configuration on the existing machine. The right choice depends less on the command itself than on how confidently you can reproduce and restore the service.
| Decision factor | Redeploy a new VPS | In-place upgrade |
|---|---|---|
| Configuration | Best when infrastructure, users, firewall rules, services, and application settings are documented or automated. | Useful when the server has manual or undocumented configuration that is difficult to recreate. |
| Downtime and cutover | Can support a controlled DNS, load-balancer, or floating-IP cutover after testing the new host. | Requires a maintenance window while packages are replaced and the server reboots. |
| Rollback | Keep the old VPS online and reverse traffic if validation fails. | Depends on a tested snapshot or image restore and may require rebuilding the machine. |
| Third-party software | Install supported versions afresh instead of carrying unsupported PPAs forward. | Every external repository and package must be reviewed before the upgrade. |
| Console access | Helpful for provisioning and testing, but the old server remains available during migration. | Essential insurance if SSH, networking, boot, or authentication fails. |
| Database migration | Requires replication, dump/restore, or a planned application cutover. | Leaves the database in place but still requires backup and post-upgrade checks. |
Canonical’s cloud guidance recommends redeploying new instances for fully automated deployments. Its server documentation recommends do-release-upgrade for manually configured Server editions and cloud images. Treat those as operating principles: reproduce what you can, and change an existing production host only when there is a clear reason.
#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.
Map the current server and the supported release path
Record the current release and architecture
Make an inventory before changing packages. Store the output outside the VPS so it remains available if the machine becomes unbootable.
lsb_release -a
cat /etc/os-release
uname -a
dpkg --print-architecture
lsblk -f
df -h
systemctl --failed
ss -tulpn
sudo ufw status verboseAlso record the kernel in use, disk and partition layout, mounted volumes, swap, service accounts, cron or systemd timers, firewall rules, DNS settings, TLS certificate locations, application ports, monitoring agents, backup jobs, and enabled package sources. Capture the versions of the application runtime, web server, database, and any agents that must be reinstalled on a replacement VPS.
Read the target release notes
Release notes identify package transitions, architecture limitations, removed components, known upgrade blockers, and any required intermediate release. Do not assume that an older LTS can move directly to the newest LTS. If the documented path requires two upgrades, plan and test each one separately.
Check the support window
Ubuntu LTS releases receive five years of standard security maintenance for packages in the main repository. Ubuntu Pro can add a further five years of extended maintenance. This is a lifecycle planning option, not a substitute for upgrading an unsupported operating system: confirm the dates and package coverage for your release before deciding to defer the change.
Back up for a real rollback
Use more than a provider snapshot
Take a provider snapshot when the platform offers one, but copy critical data to an independent backup location as well. A snapshot tied to the same account, region, storage system, or billing failure is not a complete disaster-recovery plan.
Back up application data, databases, configuration files, deployment manifests, secrets and TLS keys, user-uploaded content, package and repository lists, and any files needed to recreate the service. Preserve ownership and permissions where they matter. If the database supports a consistent dump or backup mode, use it rather than copying live files blindly.
Recommended Free Tools
Prove that restoration works
Check that backup files can be read from the independent location. Document the exact restore order: create the operating system, install dependencies, restore secrets and configuration, restore the database, restore application data, and start services. A backup that has never been restored is only an assumption about recoverability.
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.
Before the change, write down the recovery decision. If validation fails, stop traffic, restore the tested snapshot or previous image, reattach data, and document the failure. For a redeployment, retain the original VPS until the replacement has passed all checks.
Protect SSH and console access
Prepare for a dropped connection
Use tmux or a persistent screen session before starting package work, and keep a second administrative SSH session open. The Ubuntu server upgrader itself uses GNU screen, so a transient SSH drop can often be reattached rather than aborting the upgrade. A persistent shell is still useful for your own logs and preflight commands.
tmux new -s upgradeDo not close the provider’s web console, serial console, or rescue-console tab. Confirm that you know how to reach it without relying on the VPS’s normal network stack. If your provider supports it, Canonical’s cloud guidance describes running an additional SSH daemon on a different port as a mitigation during an in-place upgrade. Restrict that port to trusted source addresses and remove the temporary listener afterward.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesConfirm authentication before the maintenance window
- Test a new SSH login with the intended administrative account.
- Confirm that your key, sudo access, and emergency credentials work.
- Verify the firewall permits SSH and that you know the provider’s recovery path if it does not.
- Tell other administrators when the change begins so they do not restart services or edit configuration mid-upgrade.
Bring the current release to a clean package state
Update package metadata and all current packages
Run the preflight from the current, supported release. Canonical documents the following sequence:
sudo apt update
sudo apt dist-upgrade -o APT::Get::Always-Include-Phased-Updates=trueResolve every error instead of proceeding with a partially configured package database. If the system creates /run/reboot-required, reboot during the maintenance window and reconnect before continuing. Confirm that the machine returns with the expected kernel, network, mounts, and services.
Understand “held back” packages
APT may temporarily hold phased updates. Canonical says phased packages are normally released gradually and that security updates are never phased. The documented upgrade preflight includes APT::Get::Always-Include-Phased-Updates=true so the release-upgrade preparation sees the complete current package set; do not globally disable safeguards without understanding why a package is held.
There is a different case: an administrator may have placed a package on hold. Inspect holds and the reason for each one before changing it. A kernel, database, driver, or vendor agent may be held intentionally because an application depends on a specific version. Remove a hold only after confirming compatibility, then rerun the update and check for dependency errors. Never force a mass upgrade simply to make the “held back” count disappear.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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
Review repositories, storage, and network requirements
Disable unsupported third-party sources
Third-party PPAs and repositories are a common cause of release-upgrade failures. Record what each source provides, then disable or remove sources that do not publish packages for the target Ubuntu release. Re-enable only a vendor-supported repository after the upgrade, and install the target-release version of its packages where available.
Do not delete configuration or data merely because a repository is disabled. Export the repository list and package ownership first so you can reinstall an equivalent supported package or restore the service from your deployment documentation.
Confirm free space and writable filesystems
The upgrader downloads and unpacks hundreds of packages. Confirm several gigabytes of free space on the root filesystem and on any separate /boot partition, and check inode availability if the server has many small files. Remove only known-safe caches or old kernels; never delete application data to create space during an emergency.
df -h
df -i
findmnt
mountVerify network access
Ubuntu server upgrades require network access to an official Ubuntu mirror or a correctly configured local mirror. There is no offline server-upgrade mode. Confirm DNS resolution, outbound HTTPS, routing, and any proxy or egress firewall rules before starting. If the VPS relies on a private mirror, make sure that mirror already contains the target release and required metadata.
Run the supported in-place upgrade
Set the release prompt deliberately
When the target is an LTS release, inspect /etc/update-manager/release-upgrades and set the prompt to the LTS channel if required:
sudo editor /etc/update-manager/release-upgradesThe relevant setting is:
Prompt=ltsUse the value appropriate to the release path you have confirmed. Do not change this setting to reach an unsupported jump.
Start the upgrader
Launch the supported server command:
sudo do-release-upgradeRead every prompt. The upgrader can propose removing, replacing, or keeping packages and configuration files. Review service restarts, changed configuration files, disk-space warnings, and package removals before accepting. If a configuration file has local changes, compare the old and new versions and preserve a known-good setting only when it remains valid for the target release.
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.
Do not use do-release-upgrade -d on production merely to obtain an unreleased development path. Canonical does not recommend development upgrades for production systems.
Let the process finish
Do not reboot, close the console, or terminate the upgrader because a package download appears slow. If SSH disconnects, reconnect through the provider console or SSH and reattach to the upgrader’s GNU screen session as instructed on screen. If the process reports an error, capture the exact package and log details before attempting a repair; random retries can leave the package database in a less understandable state.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Validate the upgraded VPS before declaring success
A successful reboot is only the midpoint. Compare the live system with the inventory you created before the change.
Operating system and package state
- Confirm the Ubuntu release and architecture with
lsb_release -aor/etc/os-release. - Check the running kernel and confirm that the expected target-release kernel is installed.
- Run the package manager’s consistency checks and verify that no configuration or dependency operation remains unfinished.
- Review
systemctl --failedand the journal for boot and service errors.
Network, security, and storage
- Test SSH from a new session and confirm the intended port is reachable.
- Check listening sockets, firewall policy, routes, DNS resolution, and outbound connectivity.
- Confirm every expected filesystem and volume is mounted with the correct options.
- Verify ownership and permissions on application, database, backup, and TLS directories.
- Remove any temporary second SSH daemon or emergency firewall rule created for the upgrade.
Applications and data
- Start or restart the web server, application workers, queues, database, and supporting agents in their documented order.
- Run local health checks and an end-to-end request through the normal hostname or load balancer.
- Check database connectivity, migrations, scheduled jobs, background workers, and file uploads.
- Renew or reload TLS certificates only if validation shows a problem; confirm the certificate chain and expiration date.
- Verify monitoring, alerting, log shipping, and backup jobs are reporting normally.
Keep the maintenance window open until external connectivity and the application’s real health checks pass. A service that answers on a port can still be unusable because of a missing mount, changed permission, expired credential, failed migration, or disabled worker.
Rollback when validation fails
If you redeployed
Stop or drain traffic to the new VPS, point DNS, a load balancer, or a floating address back to the old instance, and preserve the failed host for diagnosis. Do not overwrite the only copy of logs or data before determining whether the failure is recoverable. Once the old service is stable, correct the build or migration procedure and repeat the cutover.
If you upgraded in place
Use the tested provider snapshot or previous image only after stopping traffic and deciding what data changed during the failed attempt. Restore the operating system and reattach data according to the documented recovery order. If the snapshot cannot be restored confidently, use the provider console to rescue data and rebuild from the known-good release rather than repeatedly forcing package repairs on an uncertain system.
Troubleshoot common failure points
APT reports unresolved dependencies
Stop the release process if it is still asking for a decision, record the error, and return the current release to a consistent package state. Check for interrupted configuration, held packages, unsupported repositories, and insufficient disk space. Do not remove core packages simply to satisfy one dependency; identify which source and version introduced the conflict.
A PPA or vendor repository blocks the upgrade
Disable the source, refresh package metadata, and rerun the preflight. Keep a record of the software it supplied. After the OS upgrade, install a target-release package from a repository that explicitly supports that Ubuntu version, or redeploy the application from a clean image.
The upgrader says there is not enough space
Check the specific filesystem named in the error, including /boot. Remove safe package caches and obsolete kernels according to your normal maintenance procedure, clear old logs only when retention policy permits, and recheck both bytes and inodes. If the layout cannot provide enough working room, redeployment may be safer than resizing a production disk during the upgrade.
SSH stops working after reboot
Use the provider’s serial, web, or rescue console. Check the network interface configuration, routes, firewall, SSH service status, authentication configuration, disk mounts, and boot logs. Keep the console session active while correcting the problem so a second restart does not remove your only access path.
A service starts but behaves incorrectly
Compare its package and configuration versions with the pre-upgrade inventory, inspect the service journal, and verify mounts, credentials, sockets, database schema, and file permissions. Restore the last known-good image when the cause is not clear and the service is customer-facing; prolonged experimentation on the only production copy weakens rollback options.
Make the next upgrade easier
After the change, update the inventory and recovery documentation with the final release, kernel, repository list, service versions, firewall rules, and any manual decisions made during prompts. Convert repeatable settings into configuration management or image-building code. Test a restore on a separate VPS before the next maintenance window, and keep an additional administrative path documented.
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 →Plan upgrades before standard LTS maintenance ends. The five-year standard period and optional additional five years through Ubuntu Pro give you time to schedule migration, but neither period removes the need to test application compatibility and maintain recoverable backups.
Practical decision checklist
- Is the target release on a supported sequential path from the current release?
- Can the entire server be recreated from documented automation or an image?
- Is there a tested backup in an independent location, plus a provider snapshot if available?
- Can you reach a provider console if SSH or networking fails?
- Are current packages fully updated, with required reboots completed?
- Have unsupported PPAs and third-party repositories been disabled or replaced?
- Is there enough free space for hundreds of package downloads and unpacking?
- Can you keep the old VPS or a previous image available until validation passes?
- Have you scheduled time to test ports, mounts, certificates, databases, jobs, monitoring, and external requests?
If any answer is no, postpone the in-place command and fix that gap or choose a redeployment with a controlled migration. The command is short; the safety comes from the path, backup, access, and rollback decisions around it.
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.
