How to Set Up a VPS on Vultr Step-by-Step

Choosing the Right Vultr Plan Type

For a WordPress or general PHP site, pick Vultr's High Frequency Compute plan over Regular Cloud Compute. The premium is small, and you get local NVMe storage and higher clock-speed CPU cores in return, both of which matter more to a PHP request than raw vCPU count does.

Vultr sells three broad compute tiers. Regular Cloud Compute uses shared vCPUs and block or shared storage, and it is the cheapest way to get a VPS online — fine for a staging box, a small internal tool, or a low-traffic static site where cost is the deciding factor. High Frequency Compute runs on NVMe SSDs and CPUs clocked noticeably higher than the regular tier, which directly speeds up PHP-FPM request handling and MariaDB query execution — the two things a WordPress site spends most of its server time doing. High Performance plans go further with dedicated (not shared) vCPU cores, aimed at sites with sustained heavy traffic or CPU-intensive background jobs. For the vast majority of production PHP sites, High Frequency is the sweet spot: you are not paying for guaranteed dedicated cores you don't need yet, but you are not leaving NVMe speed on the table either.

Picking OS and Datacenter Location

Select Ubuntu 22.04 LTS as the operating system, and choose the datacenter region closest to the majority of your visitors. Both choices are made on the same Vultr "Deploy New Instance" screen, right after you pick the plan type.

Ubuntu 22.04 LTS matters specifically if you intend to run CloudStick's server stack: Nginx 1.24 (packaged as nginx-cs), Apache 2.4.53 (apache2-cs, listening on port 81 for PHP handoff), PHP-FPM, MariaDB 10.6, Redis, and the CSF firewall are all built and tested against this LTS release. Choosing a different distribution or a newer, unsupported Ubuntu version adds a compatibility variable to your setup that simply isn't necessary. On location, Vultr operates dozens of datacenters worldwide — pick the one geographically nearest your actual audience, not necessarily where you personally sit. Every hop of network distance between your visitor and your server adds latency to the initial connection, before a single line of PHP has even executed, so getting the region right at deployment time is one of the cheapest performance wins available.

Adding an SSH Key at Creation

Generate an SSH key pair on your own machine before you reach Vultr's deployment screen, then paste the public key into Vultr's "SSH Keys" section so it's installed on the server the moment it boots. This means you never have to type — or email yourself — a root password.

In the Vultr control panel, go to the SSH Keys section under your account, add a new key, and paste in the public key contents you just copied. Back on the instance deployment screen, tick that key under "SSH Keys" before you deploy. Vultr writes it into /root/.ssh/authorized_keys automatically during first boot, so key-based login works immediately without any manual copying over the network.

Deploying the Instance and Getting the IP

With plan type, OS, region, and SSH key all set, give the instance a hostname and label, then click Deploy Now. Vultr typically finishes provisioning in under a minute, and the instance's public IPv4 address appears on its overview page as soon as it's ready.

Copy that IP address down — you'll use it in the very next step to connect over SSH, and again afterward whether you're pointing DNS at it or handing it to CloudStick to manage. The instance status will show "Installing" briefly before flipping to "Running"; wait for "Running" before attempting to connect, since the SSH daemon isn't listening yet during the install phase.

First SSH Connection and Verification

Connect as root using the IP from the previous step. Your local machine already holds the private half of the key you added, so no password prompt should appear.

If the connection is refused rather than prompting for a fingerprint, give the instance another minute — cloud-init may still be finishing boot tasks. Once you're in, lsb_release -a confirms you actually got the Ubuntu 22.04 image you selected rather than a stale template, and uname -a confirms the kernel and architecture match what you expect. At this point you have a bare, verified Ubuntu 22.04 VPS with key-only root access — everything from here is about turning it into a working web server.

Connecting Vultr to CloudStick

You can hand this server to CloudStick two ways: connect the instance you just built manually using its IP and SSH key, or skip the manual Vultr console entirely and provision straight from inside CloudStick using a Vultr API key.

In the manual path, add a new server in the CloudStick dashboard, paste in the IP address from the deployment step, and point it at the same SSH key you generated earlier. CloudStick connects over SSH and installs its full stack automatically — Nginx 1.24 (nginx-cs), Apache 2.4.53 (apache2-cs on port 81 for PHP), PHP-FPM, MariaDB 10.6, Redis, and CSF — so you never have to hand-configure any of that yourself on a fresh box.

The faster route is CloudStick's direct Vultr integration: link a Vultr API key once in the CloudStick dashboard, and CloudStick can list, provision, and connect Vultr instances for you without you ever opening Vultr's own control panel again. This collapses everything covered above — plan type, OS, region, SSH key, deployment — into a single flow inside CloudStick itself. See the CloudStick knowledge base: How to Integrate Vultr with CloudStick for the full API key walkthrough.

Either way, the practical next step is the same: once CloudStick reports the server as connected and the stack is installed, create your first site from the dashboard, point its DNS at the instance IP you copied earlier, and issue SSL. From there, deploying WordPress, a PHP application, or a static site takes a few clicks rather than another round of manual server configuration.