Common VPS task

How to update a VPS safely

VPS updates should be boring. Back up first, update packages deliberately, restart services, check the site, and keep a rollback path.

By WebHostWatch editors Updated April 28, 2026

Use this as a focused checklist for one common hosting task. The larger setup guides still cover full-site and full-server builds.

Difficulty
Intermediate
Time
30 to 90 minutes
Images
3 official examples

1. Back up and check free space

Run or confirm a fresh backup before patching. Check disk space so package caches, logs, or database files don't fill the server during updates.

df -h
free -m
sudo apt update
DigitalOcean production ready Droplet setup
DigitalOcean production Droplet setup: Backups and monitoring should already be part of the server before routine maintenance.

2. Apply package updates

sudo apt update
sudo apt list --upgradable
sudo apt -y upgrade
sudo reboot

For production sites, schedule updates during a quiet window and avoid stacking OS updates, PHP upgrades, database upgrades, and application releases at the same time.

3. Verify services after restart

systemctl --failed
systemctl status nginx
systemctl status php*-fpm
curl -I https://example.com
DigitalOcean firewall notes in production setup
DigitalOcean production Droplet setup: Firewall and server access should be understood before maintenance changes.

4. Watch the server after updates

Monitor CPU, memory, disk, HTTP status, logs, and backup jobs after updates. Some failures appear minutes later when cron, queue workers, or cache warmers run.

DigitalOcean monitoring agent documentation
DigitalOcean monitoring agent: Monitoring gives maintenance changes a before-and-after baseline.

Official sources checked

DigitalOcean production Droplet setup

Used for production update and backup context.

DigitalOcean monitoring agent

Used for monitoring verification context.

© 2026 WebHostWatch. We may earn affiliate commissions from links. Recommendations remain editorially independent.