How to install WordPress on a VPS?

Key takeaways

• Moving WordPress from shared hosting to VPS hosting for WordPress is one of the biggest performance upgrades you can make.
• With a VPS, you get dedicated resources (CPU/RAM) and can tune caching, PHP, and your database for real-world load.
• Proper VPS server setup (updates, firewall, SSH security, backups) makes WordPress installation smoother and safer.
• Choosing the right stack (LAMP/LEMP) and post-install hardening improves speed, security, and long-term stability.

VPS vs shared hosting for WordPress

Many WordPress sites start on shared hosting. That’s fine for small projects—but as traffic, plugins, and marketing campaigns grow, shared limits become visible. A VPS is the “next step” when you need predictable performance and stronger isolation.

Criteria	Shared hosting	VPS hosting
Resources	Shared with other accounts	Allocated (more predictable)
Performance tuning	Limited	Full control (stack, caching, PHP, DB)
Security isolation	Depends on provider, neighbors can affect risk	Stronger isolation per VPS
Scalability	Often limited by plan constraints	Easier upgrades (CPU/RAM/storage)
Best for	Small sites, early stage	Growing businesses, stores, content-heavy sites

Recommended VPS specs for WordPress

WordPress can run on small servers, but performance, caching, backups, and updates require headroom. Use this sizing table as a practical starting point.

Site type	vCPU	RAM	Storage	Notes
Blog / small company site	1–2	1–2 GB	20–40 GB SSD	Use caching + image optimization
Growing content site	2–4	2–4 GB	40–80 GB SSD/NVMe	Better for page builders + more plugins
WooCommerce / high-traffic	4–8	8–16 GB	100+ GB NVMe	DB performance + backups become critical

If you want WordPress-specific optimizations with less manual tuning, you can also consider WordPress hosting. For maximum control, go with VPS hosting.

Preparing your VPS hosting environment

Solid preparation prevents most “mysterious” WordPress issues later (timeouts, permissions errors, security incidents). Below is a clean and safe baseline for a new VPS.

VPS preparation checklist

• ✅ Choose a plan: VPS hosting with enough RAM for PHP + database + caching
• ✅ Update the OS packages (security patches)
• ✅ Create a non-root admin user (use sudo) and disable password SSH where possible
• ✅ Configure a firewall (allow only required ports)
• ✅ Set up automatic backups and test restore procedures
• ✅ Enable HTTPS (SSL/TLS) once the domain points to the server
• ✅ Monitor resources (CPU/RAM/disk) and set alerts for disk usage

Example: first steps on a Linux VPS (Ubuntu/Debian)

# Update packages
sudo apt update && sudo apt upgrade -y

# (Optional) create a new admin user
sudo adduser wpadmin
sudo usermod -aG sudo wpadmin

# Enable firewall (open SSH first, then enable)
sudo ufw allow OpenSSH
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw enable

For Linux-based WordPress deployments, Linux VPS hosting is the most common and flexible option.

Choosing your VPS operating system

WordPress runs best in most modern deployments on Linux, but Windows can be valid for specific Microsoft-focused stacks.

Setting up the stack: LAMP vs LEMP

Your “stack” is the set of services that power WordPress: web server + database + PHP runtime. The two most common options on Linux are LAMP (Apache) and LEMP (Nginx).

Stack	Includes	Best for	Notes
LAMP	Linux + Apache + MySQL/MariaDB + PHP	Classic compatibility, easy .htaccess workflows	Great default choice for many admins
LEMP	Linux + Nginx + MySQL/MariaDB + PHP-FPM	High performance, efficient resource usage	Popular for speed-focused WordPress hosting

If you’re optimizing for speed and concurrency, LEMP (Nginx + PHP-FPM) is a strong choice. If you need Apache rules and broad compatibility, LAMP remains excellent.

Installing WordPress on a Linux VPS

Below is a straightforward, production-friendly flow on Ubuntu/Debian using Nginx + PHP-FPM + MariaDB. (Commands can be adjusted for other distributions.)

1) Install Nginx, PHP-FPM, and MariaDB

sudo apt update

# Web server
sudo apt install -y nginx

# Database
sudo apt install -y mariadb-server

# PHP + common extensions for WordPress
sudo apt install -y php-fpm php-mysql php-curl php-gd php-mbstring php-xml php-zip php-intl

2) Create a database and user for WordPress

sudo mariadb

CREATE DATABASE wordpress DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
CREATE USER 'wpuser'@'localhost' IDENTIFIED BY 'STRONG_PASSWORD_HERE';
GRANT ALL PRIVILEGES ON wordpress.* TO 'wpuser'@'localhost';
FLUSH PRIVILEGES;
EXIT;

Tip: Use a strong unique password and store it securely. Database credentials are one of the first things attackers try to exploit in compromised environments.

3) Download WordPress and configure wp-config.php

cd /tmp
curl -LO https://wordpress.org/latest.tar.gz
tar xzf latest.tar.gz

# Create a web root
sudo mkdir -p /var/www/example.com

# Copy WordPress files
sudo rsync -avP /tmp/wordpress/ /var/www/example.com/

cd /var/www/example.com
sudo cp wp-config-sample.php wp-config.php
sudo nano wp-config.php

# Set:
# DB_NAME     = wordpress
# DB_USER     = wpuser
# DB_PASSWORD = STRONG_PASSWORD_HERE

4) Fix permissions

# Set ownership to the web server user (often www-data on Debian/Ubuntu)
sudo chown -R www-data:www-data /var/www/example.com

# Safer default permissions
sudo find /var/www/example.com -type d -exec chmod 755 {} ;
sudo find /var/www/example.com -type f -exec chmod 644 {} ;

5) Configure Nginx site and enable HTTPS

Create an Nginx server block for your domain and point it to /var/www/example.com. After DNS is set, enable SSL (Let’s Encrypt or your preferred certificate). HTTPS is mandatory for secure WordPress admin logins.

If you want a simpler managed environment where WordPress is already optimized, compare with WordPress hosting. If you want full control and custom tuning, keep going with VPS hosting.

Post-install hardening and performance tuning

Getting WordPress running is step one. Making it fast and secure is what separates a “working site” from a stable production platform.

Security essentials

• ✅ Enable automatic updates (at least security updates) for the OS and keep WordPress core/plugins/themes updated
• ✅ Use 2FA for admin accounts and avoid “admin” as a username
• ✅ Limit login attempts and use a firewall/WAF where possible
• ✅ Backups: schedule + retention + restore testing (don’t just “have backups”)
• ✅ Disable unused services and keep only necessary ports open

Performance essentials

• ✅ Page caching + browser caching
• ✅ Image optimization and lazy loading
• ✅ PHP OPcache enabled
• ✅ Database hygiene (clean revisions, transients, spam, logs)
• ✅ CDN for global audiences

Common WordPress-on-VPS issues (and fixes)

Problem	Typical cause	Fix
White screen / 500 error	PHP error, missing extension, wrong permissions	Check logs, install needed PHP modules, fix ownership/permissions
Slow admin panel	Heavy plugins, low RAM, no object cache	Disable heavy plugins, upgrade RAM, add caching, tune PHP-FPM
Updates fail	File permissions, low disk space	Fix permissions, free disk, ensure enough inode/disk headroom
Site becomes slow under traffic spikes	No caching, limited CPU, database bottleneck	Add caching, optimize DB, consider upgrading VPS resources

Conclusion: build WordPress on a VPS for growth

Running WordPress on a VPS gives you the performance ceiling, isolation, and control that shared hosting often can’t provide. With a clean VPS setup, the right stack (LAMP/LEMP), and strong security practices, you get a scalable foundation for a fast and reliable website.