The short answer: updating packages (apt upgrade) and upgrading to a new release (for example, from one LTS version to the next) are different things. The second touches the whole system, PHP and the database included, and can go wrong. Do it with a backup made, in a session that does not drop and with time to test afterwards.
Before you start
| Check | Why |
| Backup or snapshot | It is your only way back: Backing up a VPS. |
| Up-to-date system | Do the normal updates first and reboot. |
| Disk space | The upgrade downloads a lot. You need plenty of free space. |
| LTS to the next LTS | Do not skip releases. The tool offers the next one. |
| What runs on the server | Note the PHP, database and web server versions, and what is scheduled (cron). |
Step by step
|
|
|
|
|
|
| If the VPS has a control panel installed (cPanel or another), do not upgrade the system this way: the panel only works on certain systems and has its own process. Read its documentation first. And do not upgrade a production server without rehearsing on a copy. |
| The cleaner alternative is to create a new VPS with the new system and move the sites there. More work and much less risk: Reinstalling or changing your VPS operating system. |
|
The upgrade stopped halfway or you lost access? See I have lost SSH access to my server and open a ticket. Open a support ticket |
RECOMMENDED PRODUCT VPS server with root access Resources of your own, the OS you choose, reinstall whenever you like. from £6.72/mo (3-year plan, with coupon) See plans |
- 0 Users Found This Useful











