ElmsPark Guides
Before you start

See the whole route in four minutes

▶ An orientation to the whole route in 4 minutes 21 seconds, narrated, with captions. Deliberately quotes no prices — the plan picker below is the live source — but it does carry the traps, including the Ubuntu image to avoid.
Read the narration instead

The shape of it. About thirty minutes from an empty box to a live site with SSL. There is a by-hand build, and there is a version where you hand the whole thing to Claude Code.

Why a VPS at all. Two things shared hosting tends to take away. PageMotor needs to write its compiled stylesheet to disk, which a locked-down host will refuse, and that is the design-will-not-save problem. And shared hosts often block the outbound mail ports, so a proper email service cannot connect. On your own box, neither is true.

Picking a plan. The shape of the decision is simple: one or two sites want a small High Performance box, and an agency box only starts paying off past roughly five sites. The video deliberately quotes no prices, because Vultr changes plans regularly. The plan picker and cost calculator below are re-verified against Vultr's own public plans API, so read the numbers there.

A trap in the plan list. The agency tier comes in two shapes at each size. The cheaper listing ships almost no local disk and expects you to attach Block Storage separately. The one you want for a box full of PageMotor sites is the local-storage variant. It is also offered in about a dozen regions rather than all of them, so check availability before you settle on a location.

Picking a region. Pick the data centre closest to your visitors, not to yourself. Vultr charges the same price in every region with one exception: São Paulo carries a 50 per cent surcharge on Cloud Compute plans. Everywhere else is flat-priced, so latency is genuinely the only thing that changes.

The trap on the signup screen. Choose Ubuntu 24.04 LTS, not the newest image offered. Vultr now offers 26.04, and it ships PHP 8.5 rather than 8.3. Every php8.3-* install command in this guide fails on it, because those packages are not in 26.04's repositories, and PageMotor is not yet verified against 8.5. 24.04 is supported until 2029. And while you are on that screen, paste your SSH public key into the SSH Keys field before you deploy.

Two routes, one stack: Nginx, PHP 8.3 FPM, MariaDB and Certbot. You can follow the by-hand build, every command listed and explained. Or you can copy the prompt from the guide, edit three lines, and let Claude Code SSH in and do all of it, showing you each command before it runs and stopping on errors.

Four things stay yours, even on the automated route: creating the Vultr account, clicking through to provision the box, pointing your domain's A record at the new IP, and registering your own admin user. Those four cross a human-authorisation line — money, identity, DNS ownership and admin rights. Everything after them is fair game to automate.

Two details this guide is firm about. The timeouts must match: PHP's max_execution_time at 300 seconds, and Nginx's fastcgi_read_timeout at 600. And email: because the SMTP ports are open on your own box, Mailgun simply works here, with proper SPF and DKIM and real inbox placement. That is the thing shared hosting takes away.

Two last things. This server is yours to look after: every mainstream VPS is sold self-managed, so from Ubuntu upwards the patches, the stack and the certificate are your job. Budget about fifteen minutes a month. And if you take the free signup credit, the unused portion expires 30 days after signup, so provision the plan you actually intend to run, not a bigger one to try.

Use this guide with any AI assistant

Download it as a prompt file, paste it into Claude, ChatGPT, Gemini or any LLM, and it will walk you through every step interactively.

Download as LLM prompt
Before you start

Why a VPS, and why Vultr

Shared hosts cap PHP execution time, usually 30 to 60 seconds, and will not lift it. For a brochure site that is fine. For PageMotor with AI plugins, ecommerce, or a busy contact form, that cap becomes a ceiling the plugin keeps hitting.

A plugin waiting on an AI API response can easily spend more than a minute on one request. Shared hosting kills the process halfway through. On a VPS the timeouts are yours to set.

The April 2026 test rig

We set up a three-way rig across Vultr (New Jersey), DigitalOcean (New York) and Linode (Newark). Same PageMotor version, same plugins, same scenario on each. In this run, Vultr led on every metric we measured, and on price.

  • Sequential disk write higher is better: Vultr 2,930 MB/s, DigitalOcean 1,223 MB/s, Linode 587 MB/s
  • Random 4K IOPS higher is better: Vultr 139,264, DigitalOcean 68,894, Linode 94,856
  • PHP benchmark lower is better: Vultr 0.076s, DigitalOcean 0.211s, Linode 0.154s
  • 500 DB inserts lower is better: Vultr 1,484ms, DigitalOcean 5,445ms, Linode 4,233ms
  • Anthropic API latency* lower is better: Vultr 23.8ms, DigitalOcean 45.5ms, Linode 35.8ms
  • Full pipeline time lower is better: Vultr 7m 17s, DigitalOcean 10m 38s, Linode 7m 58s
  • Monthly cost lower is better: Vultr $60, DigitalOcean $63, Linode $72

Read it as directional, not a benchmark suite, and note the date. A single April 2026 run on comparable mid-tier plans in the regions above, not re-run since — treat the shape of the result as the signal, not the individual figures. The monthly cost row is what those plans cost in April 2026; current Vultr pricing is in Pick your plan, below. *The Anthropic API latency row is dominated by network distance from each data centre to Anthropic's endpoint, not the VPS itself, so treat it as a region and routing signal. Other low-cost hosts (Hetzner, for example) were out of scope.

For PageMotor specifically, three numbers matter most. DB inserts, because the admin is database-heavy. Disk IOPS, because the page cache, CSS compiler and uploads all hit the disk constantly. API latency, because AI plugins round-trip to Anthropic dozens of times per session.

Stage 1 Choose your plan and region

Stage 1 of 5 Choose

  • Where On this page
  • You finish with A plan and a data centre picked

Pick your plan

Vultr charges the same USD price in every data centre bar one, so location almost never changes the bill. Only the plan does. Tap what you are running:

The one exception: São Paulo carries a 50 per cent surcharge on Cloud Compute plans — the $12 box is $18 there, the $24 box is $36. Every other region is flat-priced.

  • Solo, 1-2 sites: $12/mo Cloud Compute, High Performance, 1 vCPU / 2 GB RAM / 50 GB NVMe. A capable box for a couple of brochure sites, a contact form, EP Email, EP Newsletter and a Stripe-backed shop. AI plugins run, though heavy generations may hit the 2 GB ceiling.
  • Solo with AI plugins: $24/mo Cloud Compute, High Performance, 2 vCPU / 4 GB RAM / 100 GB NVMe. Step up from the $12 box when AI plugins do real work. Generations run without hitting the RAM ceiling.
  • SME, one busy site: $24/mo Cloud Compute, High Performance, 2 vCPU / 4 GB RAM / 100 GB NVMe. The sweet spot for one serious site: consultancy, small shop, a service business with booking and contact forms all day. 100 GB is years of images and database growth.
  • SME, heavy traffic: $48/mo Cloud Compute, High Performance, 4 vCPU / 8 GB RAM / 180 GB NVMe. When sustained daily traffic regularly exceeds a few thousand visitors. AI plugins run without drama.
  • Agency, 50-100 sites: $55.48/mo VX1 (General Purpose), 2 vCPU / 8 GB RAM / 120 GB NVMe. The agency pick, and the shape our April test rig used. Dedicated vCPU is the critical difference: 50 to 100 sites per box depending on traffic. Take the local-storage variant, not the cheaper block-storage one, and enable Auto Backups on a shared agency box.
  • Agency, 100-200 sites: $111.69/mo VX1 (General Purpose), 4 vCPU / 16 GB RAM / 240 GB NVMe. For agencies past about 60 active sites; roughly doubles the ceiling of the $55 box.

Estimate the cost per site

$0.55
per site / month
~46p
roughly, in GBP
$5-15
shared hosting, per site (and AI still won't run)

Single-site owners: the $12 High Performance plan is the right answer for one or two sites, not the VX1 one. The VX1 box only pays off past roughly five sites.

Auto Backups add 20 per cent to whichever plan you pick. On production, enable them.

VX1 comes in two shapes. The cheaper listing at each size ships almost no local disk and expects you to attach Block Storage separately; the one quoted above is the local-storage variant, which is what you want for a box full of PageMotor sites. VX1 is also offered in about a dozen regions rather than all 36, so check availability before you settle on a location.

Plans, prices and specifications above re-verified on 29 August 2026 against Vultr's public plans API (api.vultr.com/v2/plans), which is the same catalogue the console deploys from. Vultr changes plans regularly, so cross-check before signing up.

Pick a region

Same price everywhere except São Paulo, which carries a 50 per cent surcharge. Otherwise latency is the only thing that changes, so pick the closest Vultr data centre to your visitors, not yourself.

  • UK & Europe: London, Manchester, Frankfurt, Paris, Amsterdam, Madrid, Milan, Stockholm, Warsaw. For most UK and Irish users, London is the obvious pick. Frankfurt fits significant German-speaking traffic or a central-European footprint reaching Berlin, Vienna and Prague at similar latency.
  • USA: New Jersey, Miami, Atlanta, Chicago, Dallas, Seattle, Silicon Valley, Los Angeles, Minneapolis, Ohio, St. Louis, Honolulu. New Jersey (our test rig choice) covers the eastern US at low latency and reaches the west coast around 70 ms. For a heavily west-coast audience, pick Silicon Valley or Los Angeles. Dallas is the sensible coast-to-coast middle ground.
  • Rest of the world: Toronto, Mexico City, São Paulo, Santiago, Tokyo, Osaka, Seoul, Singapore, Tel Aviv, Mumbai, Delhi, Bangalore, Sydney, Melbourne, Johannesburg. Vultr has regions across every populated continent. Pick the one closest to your audience; there is almost always one within 100 ms. Note São Paulo is the one region that costs 50 per cent more.

Vultr has 36 regions as of August 2026, across every populated continent: 14 in North America, 9 in Europe, 8 in Asia, 2 each in Australia and South America, and Johannesburg. There is almost always one within 100 ms of your audience.

Stage 2 What to tick on the Vultr signup screen

Stage 2 of 5 Sign up

  • Where In the Vultr console
  • You finish with A running server and its IP address

Once you have signed up and are inside the Vultr console, click Compute in the left sidebar, then Instances, then Create Instance.

Vultr Compute Instances dashboard with Create Instance button
The Compute Instances dashboard. Click Create Instance (top right) to begin.

Step 1: Choose Type — select Shared CPU

On the Deploy a Server screen, choose Shared CPU. It is the right shape for a PageMotor host at all but the very largest scale.

Deploy a Server — Choose Type screen with Shared CPU selected
Choose Type. Select Shared CPU.

Step 2: Location and Plan

Filter to Europe and pick London (or the region closest to your visitors). In the plan table below, select the plan you picked in stage 1. For one or two sites that is the High Performance row with 1 vCPU and 2 GB, at $12/mo. AMD and Intel cost the same. You can resize up later with no reinstall.

Vultr Deploy — Europe/London selected, vc2-1c-2gb plan highlighted in the plan table
Filter to Europe and pick London. This screenshot has the vc2-1c-2gb row highlighted, a $10 plan. Select the row for your own plan instead. The Deploy Summary on the right confirms your choices.

Step 3: OS, SSH Keys, and Backups

Click Configure to move to Step 2. Select Ubuntu as the OS and choose 24.04 LTS from the Image Version dropdown, not the newest one offered. Then paste your SSH public key into the SSH Keys field — this is the most important security step.

Vultr Step 2 — Ubuntu OS selected, SSH Keys field visible
Select Ubuntu and the 24.04 LTS image, not the newest one offered. Paste your SSH public key into the SSH Keys field before deploying.

Full settings reference

  • Server type: Shared CPU. Right shape for a PageMotor host at all but the very largest scale.
  • Location: Closest to visitors. Same price everywhere bar São Paulo (+50%). Pick by audience latency.
  • Plan: The plan you picked in stage 1. For one or two sites that is High Performance at $12/mo. Resize up later without reinstalling.
  • Image: Ubuntu 24.04 LTS. Ships PHP 8.3, which is what every command below installs. Supported to 2029. Not “latest LTS” — see the note under this list.
  • Auto Backups: Enable for production. 20 per cent on top of plan price. Skip for a pure test rig.
  • SSH Keys: ed25519, before first boot. The most important security click on the page.
  • Hostname: Descriptive, e.g. pm-prod-01. Readable in logs and the dashboard.
  • Everything else: Default. No startup script, no VPC, no DDoS add-on at this scale.

Pick Ubuntu 24.04 LTS, not 26.04. Vultr now offers Ubuntu 26.04 LTS, and it ships PHP 8.5 rather than 8.3. Every apt install php8.3-* command in this guide fails on it, because those packages are not in 26.04's repositories, and PageMotor is not yet verified against PHP 8.5. 24.04 LTS is supported until 2029 and is what our own production boxes run, so it is the safe pick today. If you deliberately want 26.04, expect to substitute php8.5-* throughout and to test PageMotor yourself first.

No ed25519 key yet? Generate one on your Mac with ssh-keygen -t ed25519, then paste the public key (~/.ssh/id_ed25519.pub) into Vultr's SSH Keys section before launching.

🎁 $300 of free Vultr credit: signing up through our referral link gives you $300 of credit to test the platform, at no extra cost. On the $12 plan that is roughly 25 months; on the $24 plan about 12; on the $55 VX1 box about 5. You need to link a valid card or PayPal to activate it, and the unused portion expires 30 days after signup, so pick the plan you actually intend to run. Full disclosure: if you stay past 30 days and spend at least $100, we earn a $100 referral credit. It costs you nothing and does not change your price.

Stage 3 Build the server

Stage 3 of 5 Build

  • Where On your new server
  • You finish with PageMotor live at your domain, with SSL

There are two ways to do this stage. Both end with the same server, so pick one and skip the other.

Route A · Claude Code does it

Let Claude Code do the heavy lifting

This guide recommends a complete, Claude-Code-driven stack: Vultr for the server, Cloudflare for DNS, Mailgun for email. You say what you want; Claude Code provisions the box over SSH, manages DNS through Cloudflare's API, and configures email through the EP Mailgun plugins.

If "bash commands" and "edit the Nginx vhost" made your eyes glaze over, you are the reason this section exists. Claude Code is a command-line tool from Anthropic that SSHes into your Vultr box, runs every command in this guide, and explains each step in plain English as it goes. You do not need to understand the commands. You need to know what you want: PageMotor running at your domain, with SSL, on a fresh box.

What Claude Code does for you

  • Runs every apt install, config edit, chmod and systemctl command
  • Shows you each command before running it
  • Checks each step's output, stops on errors, asks before retrying
  • Reads this guide as the reference, so the box matches the docs
  • Never deletes anything without asking first
  • Uses British English and plain language

What it will NOT do automatically

  • Create your Vultr account (you sign up as a human)
  • Provision the VPS (you click through Vultr's screen)
  • Point DNS at the new IP (you edit your domain's DNS)
  • Create your admin account (you register at /admin/)
  • Install EP plugins in the same unattended run (a quick second prompt)

The first four cross a human-authorisation line: money, identity, DNS ownership, admin rights.

Before Claude Code takes over: 7 manual steps

  1. Buy a domain if you do not have one. Any registrar works; we recommend Cloudflare (free DNS, wholesale renewals, Claude-Code-manageable). Full setup is in the Cloudflare DNS guide. You need to be able to edit the DNS A record.
  2. Install Claude Code on your Mac from claude.com/claude-code. Free to install; you pay only for Anthropic API usage, a few pence for this setup.
  3. Generate an SSH key, one time ever: ssh-keygen -t ed25519, then press Enter three times. Your public key is at ~/.ssh/id_ed25519.pub.
  4. Sign up for Vultr and provision the VPS via our referral link ($300 credit). Use the choices in the "Sign up" stage above. Paste your SSH public key (cat ~/.ssh/id_ed25519.pub | pbcopy) into the SSH Keys field during signup.
  5. Note the VPS IP address once provisioning finishes (30 to 60 seconds). You need it for the next step and the prompt.
  6. Point your domain's A record at the VPS IP. Set it DNS only (grey cloud) if on Cloudflare, so certbot can issue SSL without obstruction. Quick check: dig yoursite.com +short should return the VPS IP. Claude Code can do this for you if it has Cloudflare API access.
  7. Download the current PageMotor core ZIP from the forum download area, unzip to somewhere easy like ~/Downloads/pagemotor/, and note the path. It should contain pagemotor.php, index.php, lib/, config-sample.php and license.txt.

The prompt (copy, paste, edit three lines)

Open Claude Code in Terminal, paste this, edit the three bracketed placeholders, then hit Enter and watch it run.

Or fill in your three details here and the prompt below updates itself. What you type stays in this browser.
I have a fresh Ubuntu 24.04 VPS at [VPS_IP_FROM_VULTR].
I can SSH as root using my ed25519 key at ~/.ssh/id_ed25519.

My domain is [yoursite.com]. The A record already points at the VPS IP.

My PageMotor core files are in [~/Downloads/pagemotor/].
The folder contains pagemotor.php, index.php, lib/, config-sample.php, license.txt.

Please follow the "From empty box to live PageMotor" procedure at
https://documentation.elmspark.com/hosting/vultr/

Do this end-to-end:
1. Bootstrap the server (nginx, PHP 8.3 FPM with required extensions,
   MariaDB, certbot, fail2ban, UFW allowing only 22/80/443, and
   unattended-upgrades for automatic security patches)
2. Configure a fail2ban [sshd] jail and confirm it is active
3. Run mysql_secure_installation (set root auth, remove anonymous users
   and the test database, disallow remote root) and confirm MariaDB
   listens only on localhost
4. Configure MariaDB to default to utf8mb4
5. At an interactive mariadb prompt (never put the DB password on the
   shell command line), create the database and a dedicated DB user
   scoped to it
6. Upload my PageMotor core to /var/www/mysite on the VPS,
   create user-content subfolders, set ownership to www-data,
   755 directories / 644 files (no 777 or 775; www-data owns the tree)
7. Write config.php with my four database constants:
   DB_NAME, DB_USER, DB_PASSWORD and DB_HOST (localhost). Leave the rest blank.
8. Create the Nginx vhost with fastcgi_read_timeout 600,
   client_max_body_size 64M, and the /lib/ php denial rule
9. Set PHP max_execution_time to 300 and memory_limit to 256M
10. Run certbot --nginx for SSL, then verify renewal with
    certbot renew --dry-run and confirm the certbot timer is active
11. Verify the Nginx config is valid and services are running
12. Hit the homepage once with curl to trigger PageMotor's first-load
    table creation
13. Confirm the tables exist in the database

Stop after step 13. Do NOT register an admin account. Do NOT install
EP plugins. I will register via /admin/ in a browser, then ask you to
install plugins as a separate next task.

Rules:
- Tell me what you are about to do before doing it
- Show me the output of each step
- Stop on any error and ask me before continuing
- British English (organise, behaviour, colour)
- No em dashes in any file you write. Use commas or full stops.
- Ask before anything destructive

What to edit: [VPS_IP_FROM_VULTR] with your VPS IP; [yoursite.com] with your domain (appears twice); [~/Downloads/pagemotor/] with the path where you unzipped the core.

After the prompt finishes

  1. Open https://yoursite.com/admin/ in your browser.
  2. Register your first account. Whoever registers first becomes the administrator.
  3. Come back to Claude Code and paste the plugins prompt below.
Please install EP Email, EP Newsletter, EP Email Mailgun, EP Newsletter Mailgun,
EP GDPR, EP Password Reset, EP Diagnostics and EP Assistant on yoursite.com.
Then configure EP Email to send through Mailgun: set the Email Transport to
Mailgun EU (api.eu.mailgun.net, GDPR-clean routing) using my Mailgun sending
key [paste-sending-key] and sending domain mg.yoursite.com.

One thing the prompt does not cover: email delivery needs a Mailgun account (free plan, 100 emails/day, no card) and a verified sending subdomain mg.yoursite.com with its SPF and DKIM records. See the Email stage below, or the dedicated Mailgun setup guide.

Route B · you do it

From empty box to live PageMotor, by hand

Using the Claude Code prompt? You can skip this. This documents the exact sequence Claude Code runs, kept here for transparency and for anyone who prefers to do it themselves. About 30 minutes once DNS has propagated.

1. Bootstrap the server

SSH in as root using your ed25519 key.

apt update && apt upgrade -y
apt install -y nginx php8.3-fpm php8.3-mysql php8.3-curl php8.3-gd \
  php8.3-mbstring php8.3-xml php8.3-zip php8.3-intl php8.3-bcmath \
  php8.3-opcache mariadb-server certbot python3-certbot-nginx \
  fail2ban ufw unattended-upgrades unzip

# Confirm PageMotor's required PHP extensions
php -m | grep -iE 'mysqli|mbstring|curl|zip|fileinfo|openssl'

# Turn on automatic security updates
dpkg-reconfigure -plow unattended-upgrades

ufw allow OpenSSH
ufw allow 'Nginx Full'
ufw enable

This leaves only ports 22, 80 and 443 open. Fail2ban installs inactive, so enable an SSH jail:

cat > /etc/fail2ban/jail.local <<'EOF'
[sshd]
enabled = true
maxretry = 5
bantime = 1h
EOF
systemctl enable --now fail2ban
fail2ban-client status sshd
2. Make MariaDB speak utf8mb4 by default

Without this, emojis land in the database as ?. Create /etc/mysql/conf.d/utf8mb4.cnf:

[mysqld]
character-set-server = utf8mb4
collation-server = utf8mb4_unicode_ci

[client]
default-character-set = utf8mb4

Then systemctl restart mariadb.

3. Harden MariaDB, then create the database

Run mysql_secure_installation: set or confirm root authentication, remove anonymous users, disallow remote root, drop the test database. Ubuntu 24.04's MariaDB already listens only on localhost. Then create a scoped database and user at an interactive prompt so the password never lands in shell history:

mariadb -u root -p
CREATE DATABASE mysite_pm CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
CREATE USER 'mysite_db'@'localhost' IDENTIFIED BY 'your-strong-password';
GRANT ALL ON mysite_pm.* TO 'mysite_db'@'localhost';
FLUSH PRIVILEGES;
EXIT;

Use a dedicated user scoped to this database only. Never put root credentials in config.php.

4. Drop PageMotor into place
mkdir -p /var/www/mysite
cd /var/www/mysite
# Copy pagemotor.php, index.php and lib/ from your local core
mkdir -p user-content/{themes,plugins,images,uploads,css,tmp,logs}

Copy config-sample.php to config.php and fill in the four database constants: DB_NAME, DB_USER, DB_PASSWORD and DB_HOST (stays localhost). Leave the rest at their defaults; PageMotor uses utf8mb4 automatically.

chown -R www-data:www-data /var/www/mysite
find /var/www/mysite -type d -exec chmod 755 {} \;
find /var/www/mysite -type f -exec chmod 644 {} \;
# setgid so files created later keep the www-data group
find /var/www/mysite/user-content -type d -exec chmod g+s {} \;
5. The Nginx vhost

Create /etc/nginx/sites-available/mysite:

server {
    listen 80;
    server_name yoursite.com;
    root /var/www/mysite;
    index index.php index.html;

    fastcgi_read_timeout 600;
    proxy_read_timeout 600;
    send_timeout 600;
    client_max_body_size 64M;

    add_header X-Content-Type-Options nosniff;
    add_header X-Frame-Options SAMEORIGIN;

    location / { try_files $uri $uri/ /index.php?$query_string; }
    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/run/php/php8.3-fpm.sock;
        fastcgi_read_timeout 600;
    }
    location ~ ^/lib/.*\.(js|css|woff|woff2|ttf|eot|svg|png|jpg|gif)$ {
        try_files $uri =404;
    }
    location ~ ^/lib/.*\.php$ { deny all; }
    location ~ /\.(ht|git|env) { deny all; }
}
ln -s /etc/nginx/sites-available/mysite /etc/nginx/sites-enabled/
nginx -t && systemctl reload nginx

fastcgi_read_timeout 600 is the critical line. Nginx defaults to 60 seconds, which any AI plugin will blow through.

6. PHP settings that match Nginx

Edit /etc/php/8.3/fpm/php.ini:

max_execution_time = 300
memory_limit = 256M
upload_max_filesize = 64M
post_max_size = 64M

systemctl reload php8.3-fpm. PHP timeout shorter than Nginx means surprise 504s; longer means processes running past when Nginx gave up. Keep them aligned. On the $12 / 2 GB plan, cap php-fpm pm.max_children and add a small swap file so a burst of AI calls cannot take the box down.

7. SSL with Certbot

With your A record pointing at the Vultr IP and DNS propagated:

certbot --nginx -d yoursite.com
systemctl list-timers | grep certbot
certbot renew --dry-run

If you put Cloudflare's proxy in front: issue the cert first with the record DNS-only (grey cloud), so certbot's HTTP-01 challenge reaches nginx. DNS-only also means PageMotor sees a true HTTPS connection and emits correct https:// links. Turn the orange proxy on only after the cert is live, and set SSL/TLS mode to Full (strict). Never use Flexible: it talks to your origin over plain HTTP, making PageMotor emit http:// links and risk a redirect loop.

8. First page load creates the tables

Load your domain in a browser. PageMotor's first front-end request auto-creates its database tables, so there is no SQL file to import. Then visit /admin/ to reach Admin Registration; the first account becomes the administrator.

Blank page here? PageMotor keeps PHP errors off the screen and writes them to /var/www/mysite/user-content/logs/php-errors.log. Read that file rather than turning display_errors on.

9. Install essential plugins

Through the admin, install and activate: EP Email, EP Newsletter, EP Email Mailgun, EP Newsletter Mailgun, EP GDPR, EP Password Reset, EP Diagnostics and EP Assistant. Configure EP Email to send through Mailgun (see the Email stage below).

Settings people forget (and later regret)

  • fastcgi_read_timeout 600 or higher. Default 60 kills AI plugins mid-call.
  • max_execution_time = 300. Match PHP to Nginx or expect 504s.
  • MariaDB character-set-server = utf8mb4. Without it, emojis corrupt silently.
  • UFW before anything else. A new server gets scanned within minutes.
  • Run mysql_secure_installation. A default install leaves an open test database and anonymous users.
  • Enable the fail2ban [sshd] jail. The package installs inactive.
  • ed25519 keys, then harden login. Set PasswordAuthentication no and PermitRootLogin prohibit-password, then reload ssh.
  • unattended-upgrades on. A one-time apt upgrade is not enough for a box that lives for years.
  • opcache on. Default on Ubuntu 24.04; verify with php -m | grep -i opcache. 3 to 5 times the page speed for free.

Stage 4 Email: Mailgun (recommended)

Stage 4 of 5 Email

  • Where At Mailgun and your DNS
  • You finish with A verified sending domain, so your site's mail gets delivered

Vultr gives you the box, not email, and it blocks outbound port 25, so traditional SMTP is out anyway. Mailgun is the production recommendation across both EP Email (transactional) and EP Newsletter (campaigns), via the EP Email Mailgun and EP Newsletter Mailgun driver plugins.

  • The port-25 block does not matter. The drivers POST to Mailgun's HTTPS API on port 443, not SMTP.
  • EU region for GDPR. Pick Mailgun EU (api.eu.mailgun.net) for EU and UK audiences. The region is locked per domain for life, so choose it when you create the domain. North America picks Mailgun US (api.mailgun.net).
  • Free to start. 100 emails a day with one verified custom sending domain, no card.

Never put Mailgun's MX records on your root domain. Verify mg.yourdomain.com in Mailgun, never yourdomain.com itself. Mailgun's MX records are for inbound mail only; on your apex they hijack delivery away from your existing mailbox and incoming mail silently stops. Sending needs only the SPF and DKIM records on mg..

What to add in Cloudflare

For the mg.yourdomain.com subdomain, all set DNS only (grey cloud), never the orange proxy:

  • One SPF TXT record at mg.yourdomain.com
  • Two DKIM CNAME records at pdk1._domainkey.mg… and pdk2._domainkey.mg…
  • One tracking CNAME at email.mg…
  • The two MX records only if you want Mailgun to receive mail (you usually do not, and never on the apex)

For the full end-to-end walkthrough (signup, region, DNS, DKIM activation, sending key, inbox-placement verification), follow the dedicated Set up reliable email with Mailgun guide.

Fallback: if you cannot use Mailgun, Brevo's free tier (300/day) is a workable second choice via the EP Brevo drivers, with a deliverability trade-off. SendGrid is now legacy for new setups (Twilio ended permanent free plans for new accounts on 25 March 2025).

Stage 5 Who looks after this server?

Stage 5 of 5 Look after it

  • Where On your new server
  • You finish with A server that stays patched and safe

You do. A Vultr VPS is self-managed, the same as every mainstream provider. Hostinger word it most plainly, and it holds across the board: “As our VPS solutions are self-managed, you will get full freedom to configure and manage the virtual server.”

Vultr looks after the hardware, the network, DDoS filtering at the edge, and whatever backups your plan includes. Everything from Ubuntu upwards is yours: security patches, your control panel, PHP, the database, your TLS certificate, and PageMotor itself.

That is not a catch. It is the same freedom that makes a VPS fix the problems shared hosting gives PageMotor. But nobody emails you when a patch is published, and a server left alone for a year is running a year of known, catalogued, publicly indexed vulnerabilities. Budget about fifteen minutes a month.

Keeping your PageMotor VPS healthy covers the routine in full, and includes a ready-made Claude Code prompt that turns on automatic security patching, runs the monthly checks, and proves your site still loads afterwards. Read the maintenance guide.

Finish

The whole guide in one paragraph

Summary: Vultr for the host, Cloudflare for DNS, Mailgun for email, Ubuntu 24.04 LTS (not 26.04) with Nginx + PHP 8.3 FPM + MariaDB + Certbot, PHP 300s / Nginx 600s timeouts matched, about 30 minutes from an empty box.

Plans, prices and regions re-verified 29 August 2026 against Vultr's public plans API; the three-way benchmark table is a dated April 2026 run and has not been repeated. Vultr changes plans regularly, so cross-check vultr.com/pricing/ before signing up. Spotted a mistake or outdated price? Open an issue on GitHub. Published by ElmsPark.

← All ElmsPark guides