How to Set Up Cheap VPS Hosting for Your Website: A 10-Minute Step-by-Step

If you are searching for a reliable yet budget-friendly way to host your website, a VPS cheap hosting plan is one of the smartest options available. It offers the power and flexibility of a dedicated server but at a price that fits most budgets. Many small businesses, developers, and bloggers choose VPS hosting because it provides better performance, scalability, and stability than shared hosting—all without the expensive costs of dedicated hardware.

A working website on a cheap VPS is about ten minutes of decision-making and command-running, not a weekend project. The minimum viable build is a small Linux instance, a web server, a database, and a TLS certificate, with SSH locked down before anything else. The steps below are written for a $5-$7 plan running Ubuntu 24.04, and every command is one you can paste. The focus is on doing the minimum correctly rather than building a stack you will never maintain.

Step 1: Pick the plan and the image before you buy

For a single small site, 1-2 vCPU and 2 GB RAM is the sensible floor, with at least 25 GB NVMe. 1 GB works for a static site but strains once you run MySQL and PHP together. Choose the closest datacenter region to your audience, because a 40 ms network difference is more noticeable than a 200 MHz CPU difference. Pick the plain Ubuntu LTS image, not a one-click app, unless you specifically want its defaults.

Note the IP address and root password when the instance provisions. Then, before touching the server, create a non-root user plan in your head: you will add a sudo user, copy your key, and disable password login. Doing this first prevents the classic mistake of configuring a web server with root and password auth still open to the internet.

Step 2: First login and user setup

Connect as root over SSH, then create your user and give it sudo. Upload your public key with ssh-copy-id from your laptop, or paste it into ~/.ssh/authorized_keys on the server. Test the new login in a second terminal before changing any SSH settings, so you cannot lock yourself out. This two-terminal habit saves recovery time on every server you build.

Add a basic firewall before installing anything: allow OpenSSH, HTTP and HTTPS, then enable it. On Ubuntu, ufw allow OpenSSH, ufw allow 'Nginx Full' and ufw enable is enough. Set automatic security updates with unattended-upgrades and a short timezone. These four minutes of hardening prevent most of the automated intrusion attempts that hit every new public IP within hours.

Step 3: Install the web server and PHP

Install Nginx, PHP-FPM with the extensions WordPress needs, and MariaDB in one command. On Ubuntu 24.04 the packages are current enough for a small site, so you do not need third-party repositories. After install, check that PHP-FPM is running and that Nginx serves the default page. If the default page loads, the network, firewall and web server are all correct, which isolates later faults.

Tune two settings at this point rather than later. In php.ini set memory_limit to 256M and upload_max_filesize to 32M; the defaults are too small for many themes and media uploads. In the PHP-FPM pool, set pm.max_children to a number your RAM supports: roughly 20 MB per idle child and 80 MB per busy one, so a 2 GB plan can safely run 12-16 children if the database is given its own share.

Step 4: Create the database and site directory

Create a database and a dedicated user with a strong password, granting only what the site needs. Never use the root database account for the application. Make a directory under /var/www owned by the web user, and set permissions so Nginx can read files but not write to them, while the uploads folder stays writable. That split is what lets a compromised plugin write only where it should.

Place a short Nginx server block pointing the server_name at your domain and the root at the site directory, with a fastcgi_pass to the PHP-FPM socket. Test with nginx -t before reloading. A placeholder index.html with your domain name lets you confirm DNS and TLS before the CMS is even installed, separating three possible failure points into three quick checks.

Step 5: Point DNS and issue a certificate

Create an A record for your domain and any www variant pointing at the server IP, then wait for propagation, usually under five minutes on modern providers. Install certbot and request a certificate for both names; it will add the HTTPS redirect for you. Confirm that HTTP redirects to HTTPS and that the certificate renews automatically with a dry run. A missing renewal is the most common cause of a site going dark months later.

If DNS is slow to propagate, use a temporary hosts-file entry on your own machine to test the server block without waiting. Set the certificate renewal timer and verify it is active. Budget plans are often the target of port scanners, so an HTTPS-only site with HSTS set is also a small security improvement, as long as you are sure every subdomain will be served over TLS.

Step 6: Install the CMS or app

Download the CMS release to the site directory, unpack it, and set ownership so the web user owns uploads but not the whole tree. Create the config file from the sample and fill in the database details. Run the installer over HTTPS only, because it sends credentials in the clear. If the installer cannot write its config, fix ownership rather than loosening permissions on the whole directory.

For a static or custom app, deploy the built files and skip the installer. Either way, confirm that the front page loads over HTTPS and that the admin path responds. Then immediately remove the default sample content and any install scripts left behind. That cleanup takes a minute and closes the most common cheap-host compromise path, which is an installer directory still reachable a month after setup.

Step 7: Add caching, backups and monitoring

Install a page cache at the web server level if your CMS supports it, and enable compression. Set up a nightly database dump plus a file backup to a second location, not just the same disk, because a disk failure takes both copies. Add a simple uptime check against your HTTPS URL with a 60-second interval. These three additions turn a fragile install into one you can leave alone.

Finish by recording what you built: the plan specs, the region, the installed versions, and where backups live. That note is what lets you rebuild in minutes after a provider failure or an accidental delete. A cheap VPS is only cheap if the setup is repeatable; a carefully documented ten-minute build beats an undocumented all-day one every time.

When to stop at ten minutes and when to invest more

A brochure site, a blog or a small store can run for months on exactly this build. Invest more only when a specific symptom appears: slow admin pages point to database tuning, high load during traffic spikes points to caching, and repeated failed logins point to hardening. Spending days on complex orchestration for a single small site is effort that never pays back at this scale.

If you are still choosing the box, compare the entry plans at affordablevpsserver.com against the 2 GB, 25 GB NVMe floor described here. For a wider starting point on pricing and plan shapes, the VPS hosting overview lists the tiers and what each is sized for. Build the simple version first, measure it, and only then decide whether the next tier is worth it.

Affordable-Vps-Server-Author
Affordable-Vps-Server-Author
Articles: 434

Leave a Reply