VPS Full Disk Checklist for WordPress Websites

halfbrain_logo512adminJune 12, 2026
170 lượt xem

VPS Full Disk Checklist for WordPress Websites

A full disk can break WordPress, MySQL, Nginx, SSL renewal, backups and log writing. On small VPS servers, disk usage can grow quickly because of logs, backups, cache files, uploads or database bloat.

Common causes

  • Backup files stored on the same VPS.
  • Nginx logs grow too large.
  • WordPress cache grows too much.
  • Uploads folder is too large.
  • Database grows from revisions or plugin logs.
  • Docker images and logs consume disk space.

Checklist

  1. Check disk usage with df.
  2. Find large top-level folders with du.
  3. Check /var/log size.
  4. Check Nginx logs.
  5. Check WordPress backup folders.
  6. Check wp-content/uploads.
  7. Check cache plugin folders.
  8. Clean apt cache safely.
  9. Move old backup files outside the VPS.
  10. Set log rotation and backup retention.

Final check

Do not delete random system files. Find what is large first, then clean logs, cache, old backups or unused Docker data carefully.

Checklist Type Troubleshooting
Level Beginner
Risk Level High Risk
Estimated Time 20–60 minutes

When to Use This Checklist

Use this checklist when a WordPress VPS is out of disk space or close to full disk usage.

Required Tools

SSH access, Linux terminal, Nginx log path, WordPress root path, backup folder access, basic file management

Before You Start

Do not delete files until you identify what is consuming disk space. If possible, create an external backup before cleanup.

Verification Steps

  1. Disk usage drops to safe level.
  2. Website loads normally.
  3. Database can write again.
  4. Nginx log still works.
  5. Backup process does not fill disk again.

Rollback Plan

If cleanup removes something important, restore from backup. For risky cleanup, move files to a temporary folder first instead of deleting immediately.

Common Mistakes

  • Deleting system folders randomly.
  • Keeping all backups on the same VPS.
  • Ignoring log rotation.
  • Not checking Docker disk usage.
  • Letting cache grow without limits.

Related Commands

df -h
sudo du -h --max-depth=1 / | sort -h
sudo du -h /var/log/* | sort -h
sudo apt clean
sudo apt autoremove -y

Share:

Disclaimer: The guides, checklists, commands, and examples on HalfBrain.net are provided for educational and operational reference only. Server environments, hosting providers, software versions, security settings, and WordPress configurations can vary, so you should always review commands before running them on your own system. We do our best to keep the content accurate and useful, but we cannot guarantee that every command, configuration, or recommendation will fit every environment. Always back up your website, database, and server configuration before making changes. HalfBrain.net is not responsible for data loss, downtime, security incidents, misconfiguration, or other issues that may result from applying the information on this website. Use the material at your own discretion.

Leave a Reply

Your email address will not be published. Required fields are marked *