Shared hosting is where most WordPress sites begin, and for a first blog it is usually enough. Sooner or later you meet its ceiling: a busy neighbour on the same machine eats the processor time, you cannot enable the PHP extension a plugin needs, and you have no root access to fix either problem. A virtual private server answers all three. A VPS is a partition of a physical machine that behaves like a machine of its own, with its own operating system, its own reserved memory and processor share, and an administrator login that actually belongs to you.
The trade-off is that nothing arrives configured. Nobody has created a database for you, nobody has set the clock, and nobody will patch the server if you do not. This guide walks through installing WordPress on a VPS in nine steps, from opening the hosting account to logging into a working dashboard. It covers both routes people take — the automatic one-click installer and the manual command-line install — and explains what each step is actually doing, so that when something misbehaves you know which part to look at. If you are still deciding whether WordPress is the right platform at all, our overview of the WordPress content management system is the better place to start.
Why Put WordPress on a VPS?
A VPS is not automatically better than shared hosting. It is better for particular reasons, and if none of them apply to you, the extra administration is simply extra work. The usual reasons are:
- Predictable resources. Memory and processor share are allocated to your instance rather than pooled across hundreds of accounts, so traffic spikes on other sites do not slow yours.
- Root access. You choose the PHP version, the database engine, the web server and the caching layer, and you can install anything the stack requires.
- Isolation. A compromised neighbour is not your problem in the way it can be on a crowded shared box.
- Room to tune. Object caching, a content delivery network origin, image processing libraries and staging copies are all easier when the server is yours.
The responsibility that comes with that control is real. Operating system updates, firewall rules, backups and WordPress core updates are all yours to run. The project's own security documentation is worth reading before you put anything important on a server you administer yourself.
Two Routes: Automatic and Manual
Almost every WordPress installation on a VPS follows one of two paths. The automatic path uses an application installer supplied with a control panel: you pick a domain, fill in a short form, and the installer creates the database, uploads the files and runs the setup for you. The manual path does the same work by hand over an SSH session. Automatic is faster and perfectly respectable. Manual takes longer and teaches you where everything lives, which is exactly the knowledge you need the first time a site breaks.
The automatic route in outline
- Log in to the control panel on your server.
- Open the application installer and choose WordPress.
- Select the protocol and the domain or subdirectory to install into.
- Fill in the site title, administrator username and a strong password.
- Choose a starting theme and any bundled plugins, or skip both and add them later.
- Run the install, then check the site loads and the admin login works.
The manual route in outline
- Set up the VPS hosting account.
- Log into the server over SSH.
- Set the server time zone.
- Create a database for WordPress.
- Create a database user and grant it permissions.
- Download the WordPress release and unpack it.
- Move the files into the web root and set ownership.
- Copy the sample configuration file and fill in the database details.
- Run the browser installer.
- Finish setup and harden the installation.
The Nine Steps in Detail
Step 1: Set Up a VPS Hosting Account
Choose an instance size, an operating system image and a data centre region close to your readers. A small instance is enough for a new site; you can resize later. When the server is provisioned you will receive an IP address and either a root password or an SSH key. Point your domain's A record at that IP address now, because propagation takes time and you will want the domain resolving by the time you run the installer.
Step 2: Log Into Your VPS
Open a terminal and connect with SSH, using the account name and the server address your host gave you: ssh username@your-server-ip. If the host issued an SSH key rather than a password, point at the key file with the -i flag. The first connection asks you to accept the server's fingerprint. Once you are in, create a non-root user with administrative rights and disable password logins for root — it is five minutes of work that removes the single most common way small servers are taken over.
Step 3: Set the Server's Time Zone
A fresh server almost always runs on UTC. That is a perfectly good choice, but it must be a deliberate one, because the server clock decides when scheduled posts publish, when cron events fire and what timestamps appear in your logs. Set it from the command line or from the control panel's time settings, then set the matching time zone inside WordPress under Settings once the site is running. Mismatched clocks produce scheduling bugs that are maddening to diagnose later.
Step 4: Create a Database for WordPress
WordPress stores every post, page, setting and comment in a database; the files on disk are only the software. Create an empty database with a name you will recognise later. In a control panel this is a form under the databases section. From the command line, connect to the database server and issue a create statement. Note the exact name, including any prefix your host adds automatically — a mistyped database name is the most common cause of a failed install.
Step 5: Create the Database User and Grant Permissions
Never let WordPress connect as the database root account. Create a dedicated user with a long random password and grant it privileges on that one database only. If the site is ever compromised, the attacker inherits access to a single database rather than to every database on the server. Record the database name, user name, password and host value; you need all four in the next step.
Step 6: Download and Place the WordPress Files
Fetch the current release from the official source, unpack the archive, and move the contents into the directory your web server serves for that domain. Whether the files sit in the root of the domain or in a subdirectory is a decision worth making deliberately, because it becomes part of every URL on the site. Set file ownership to the web server user so that uploads and updates work, and keep directory permissions restrictive rather than opening everything up to solve a permissions error.
Step 7: Edit the Configuration File
Copy wp-config-sample.php to wp-config.php and open it in an editor. Fill in the four database values from step five, then replace the block of authentication keys and salts with fresh random values — leaving the placeholder text there weakens every login cookie the site issues. The file is also where you set the debug constant while you are building and switch it off before launch. The developer documentation lists every constant the file accepts.
Step 8: Run the Browser Installer
Visit your domain in a browser. If the configuration file is correct, WordPress presents its setup screen: site title, administrator username, password and an email address for administrative notices. Avoid an obvious administrator name, and use a password manager rather than something memorable. Submitting the form writes the database tables and creates your account.
Step 9: Complete the Install and Harden It
Log in and work through the essentials before you write anything: set the permalink structure, set the site time zone to match the server, install a TLS certificate and force HTTPS, take the first backup, and remove any sample content. Then read the installation and configuration sections of the official WordPress documentation for the maintenance tasks that follow. From here the site is ordinary WordPress: you can pick a theme, learn the Gutenberg block editor or add a page builder from our roundup of WordPress website builders.
Problems That Come Up, and What They Mean
- Error establishing a database connection. One of the four values in the configuration file is wrong, or the database user has no privileges on that database.
- A blank white page. Usually a fatal PHP error. Enable debugging temporarily, or read the server error log.
- Uploads fail, updates ask for FTP details. File ownership is wrong; the web server user cannot write to the content directory.
- Mixed content warnings after adding a certificate. The site address is still recorded with the insecure protocol in settings, or old URLs are hard-coded in content.
Frequently Asked Questions
Can I run WordPress on a VPS? Yes. WordPress needs a web server, PHP and a compatible database, all of which run comfortably on a modest virtual server.
Which route is better, manual or automatic? If your host offers an installer and you simply want a working site, use it. Install manually when you want to know how the pieces fit together, or when you are building a stack the installer does not support.
Do I need a control panel? No. A control panel makes databases, mail and certificates easier to manage, but every step above can be done from a terminal.
Conclusion
Installing WordPress on a VPS is not difficult; it is simply a sequence that has to be followed in order. Create the account, get in over SSH, fix the clock, build the database and its user, place the files, fill in the configuration, run the installer, then secure what you have built. Work through the nine steps once and the process stops feeling like server administration and starts feeling like ordinary setup. More tutorials in this series are collected in our CMS section.