VPS & ServersVPS & Servers · Intermediate
A new server is scanned within minutes of going online. The first steps that stop almost every attack on an Ubuntu 24.04 VPS (SSH keys, no root login, a firewall, fail2ban and automatic updates) in one tested script, plus the cloud-init trap, Ubuntu's support dates and a best-practice checklist.
VPS & ServersVPS & Servers · Intermediate
Nginx, Apache and LiteSpeed compared in plain words: how they work, performance, PHP and WordPress, .htaccess, reverse proxy, how they differ from Tomcat, Traefik and Caddy, which big sites use what, and a tested PHP page that shows which server any website runs.
VPS & ServersVPS & Servers · Intermediate
Run n8n on your own server for the price of a small VPS: what it needs, self-hosted vs n8n Cloud, a tested Docker Compose setup with automatic HTTPS, running it free on your laptop or Oracle's free server, the 2026 security lessons, backups and updates.
VPS & ServersVPS & Servers · Intermediate
Run your own chat and video call server: ejabberd 24.12, MySQL, a free SSL certificate and the coturn TURN server on Ubuntu, step by step, with the ports, tests and common fixes.
VPS & ServersVPS & Servers · Intermediate
Install WordPress on your own VPS: database, files, permissions, virtual host, SSL and security keys — plus an honest look at whether it beats shared hosting.
VPS & ServersVPS & Servers · Beginner
Set up Apache, MySQL and PHP on a fresh Ubuntu server, with the security steps most guides leave out. Every command explained, and a check after each one.
VPS & ServersVPS & Servers · Intermediate
A complete NextCloud install on Ubuntu: PHP extensions, MySQL, Apache virtual host, SSL, and the four post-install settings that stop it being slow.
VPS & ServersVPS & Servers · Beginner
Get HTTPS on your Ubuntu server with a free Let's Encrypt certificate. Install, force redirect, test auto-renewal properly, and fix the errors that stop it working.
VPS & ServersVPS & Servers · Intermediate
Install your own chat server on Ubuntu. Java, MySQL, the admin panel, SSL and the ports that have to be open — with the plugin list that makes it actually useful.
A VPS is a server you control completely. For about $5 to $10 a month you get root access, your own PHP settings, and no neighbours slowing you down.
You also become the system administrator. These guides cover both sides of that trade.
Is a VPS actually better than shared hosting?
| Your own VPS | Shared hosting |
| Speed | Much faster | Depends on neighbours |
| Control | Complete | Whatever the panel allows |
| Security updates | Your job | Handled for you |
| Broken at 2am | Your problem | Their support |
| Cost | $5–10 / month | $3–5 / month |
Choose a VPS to learn, to run several sites, or to run software shared hosting simply cannot host — NextCloud, a chat server, anything that runs as a continuous service.
Stay on shared hosting if the site matters commercially and you do not want responsibility for patching an operating system. That is a perfectly sensible answer.
The first ten minutes on a new server
Do these before installing anything. Most compromised servers skipped at least one:
- Update everything —
apt update then apt upgrade. In that order; the second does little without the first.
- Create a normal user with sudo and stop logging in as root. Every automated attack on the internet is trying root right now.
- Allow SSH, then enable the firewall. In the wrong order you lock yourself out and need the provider rescue console.
- Install SSL before putting anything real on the server.
How much server do you need?
- 1 GB RAM — learning, a small static site
- 2 GB — WordPress, NextCloud, an Openfire chat server with a few thousand users
- 4 GB — WooCommerce, group video calls, anything that transcodes media
- 8 GB and up — several busy sites, or video at scale
Memory runs out long before disk does. Storage is the cheapest thing a host sells, which is exactly why it features in the advertising.
One habit worth building
When something breaks, read the log before changing anything:
sudo tail -f /var/log/apache2/error.log
Run that, reload the page, and the real error appears. It is faster than any amount of guessing, and it is the single most useful command in this whole section.