Ubuntu VPS Setup Checklist for New Hosting Sites

Start with the account, not the server

If you just bought a new VPS, the quickest way to create problems is to install software before you know what the site actually needs. A clean Ubuntu VPS setup checklist starts with the basics: who manages DNS, where email will live, and whether the site needs cPanel, Plesk, or DirectAdmin.

For many customers, the simplest route is to pair a VPS with Hostperl VPS hosting and choose the control panel before migration day. If your site is still on shared hosting, compare the mailbox plan and traffic profile first using Shared Hosting vs VPS for Email: What Actually Changes in 2026. That one decision shapes DNS records, mail routing, and the work you will need later.

• Confirm the operating system version. Ubuntu 24.04 LTS is the practical default in 2026 for new hosting builds.
• List every domain, subdomain, and mailbox that must move.
• Decide whether the VPS will host email, or whether you will keep mail on shared hosting.
• Check whether your site uses cPanel, Plesk, or DirectAdmin on the old server.

Write those answers down before you touch the new server. It saves time during migration and keeps support tickets shorter.

Prepare Ubuntu before installing the panel

On a fresh Ubuntu VPS, update the base system first. It is a small step, but it helps avoid package conflicts later.

sudo apt update && sudo apt -y upgrade
sudo reboot

After reboot, check the server time, hostname, and available disk space. Many hosting problems start with a generic hostname or a full root partition.

hostnamectl
lsblk
df -h
 timedatectl

If you manage the server through a panel, keep the hostname aligned with the panel’s requirements. For example, many mail and SSL setups work better when the hostname is a proper fully qualified domain name such as server1.example.com.

Choose the panel that matches the customer workflow. If you want a practical comparison before committing, Hostperl’s panel comparison for hosting buyers explains the operational differences without the jargon.

Install only what the site needs

A common mistake is installing every available service because it feels safer. It usually is not. A hosting server should run the stack the site will actually use, nothing more.

For a standard PHP site, that usually means your panel, web server, PHP version, database server, and mail stack if you host email locally. If you run WordPress, keep the stack simple and predictable. Hostperl’s shared hosting plans are often the cleaner option for small brochure sites, while a VPS makes more sense once you need custom PHP versions, staging, or tighter resource control.

• Web server: Apache, Nginx, or the panel’s managed stack
• PHP: the version required by your site and plugins
• Database: MariaDB or MySQL, with backups enabled
• Mail: local only if you intend to manage deliverability properly

If you run a business site, check the mail plan before launch. The article Email Hosting on Shared Plans: What Matters in 2026 helps when you are deciding whether to move mail with the website or keep it separate.

Set DNS before the switch, not after

DNS is where many migrations slow down. You do not need to memorize every record, but you do need a clean checklist.

At minimum, copy the A, AAAA, MX, TXT, and CNAME records for each domain. Lower the TTL on important records a day before the move, ideally to 300 seconds. That gives you faster propagation when you point the domain at the new server.

example.com.      300   IN A     203.0.113.10
mail.example.com. 300   IN A     203.0.113.10
example.com.      300   IN MX 10 mail.example.com.
_dmarc.example.com. 300 IN TXT   "v=DMARC1; p=none; rua=mailto:dmarc@example.com"

If your DNS is managed inside the panel, make sure you know where the zone file lives and who has access. For new customers, the practical rule is simple: if you cannot explain where DNS is edited, stop and document it before migration.

For a fuller launch checklist, use SSL, DNS, and Email Setup Checklist for Hosting Customers in 2026 alongside this tutorial.

Move the site in a test window first

Do not switch live traffic until you have tested the site on the new VPS. That means copying the files, restoring the database, and loading the site through a temporary hostname or hosts-file test.

If you are moving between panels, Hostperl’s migration guide for hosting sites between panels is the better companion article. It covers the practical steps customers actually run into: database paths, mailboxes, PHP settings, and SSL reissue timing.

1. Copy the website files to the new server.
2. Import the database and confirm the site opens without errors.
3. Test login, forms, and checkout flows.
4. Check image uploads, cron jobs, and scheduled backups.
5. Review PHP errors and file permissions before DNS changes.

If you want to avoid downtime during the cutover, use Move a Hosting Site Between Panels Without Downtime. It is especially useful when an agency or small business cannot afford a broken contact form during business hours.

SSL, mail, and backups are launch-day items

These three items should be ready before you tell anyone the site is live. SSL protects the browser connection, mail keeps your business reachable, and backups protect you from the first bad plugin update or admin mistake.

Issue the SSL certificate after DNS points to the new server. If the panel supports automatic issuance, use it. If not, verify the certificate chain and make sure the redirect to HTTPS works for both the root domain and www.

curl -I http://example.com
curl -I https://example.com

For email, confirm SPF, DKIM, and DMARC are published correctly. Then send test mail to Gmail, Outlook, and one business mailbox you control. If mail bounces or lands in spam, fix that before the client notices.

Use Hostperl’s email deliverability setup guide if the domain previously lived on shared hosting, because those records often need adjustment during a move.

Backups should include both files and databases. Keep one copy on the server for quick restores and another off-server copy. A backup that sits next to the live site is not enough.

Check performance before launch

Once the site loads, do a short reality check. You are looking for slow admin pages, high CPU spikes, or database timeouts. These usually show up before visitors complain.

• Open the homepage three times and watch response consistency.
• Log into the CMS and load the editor.
• Run a basic speed check from your region and one APAC location.
• Review PHP workers, memory use, and disk space if the server feels sluggish.

If the site is growing or the team wants more headroom, compare hosting tiers before you outgrow the box. Hostperl’s VPS vs Dedicated Servers guide is useful when traffic, database load, or mailbox volume starts pushing a single VPS too hard.

For customers in New Zealand and the wider APAC region, latency to your audience matters. A small VPS in the right location often feels faster than a larger server in the wrong one.

Keep the first 48 hours simple

The server is not finished when DNS flips. It is finished when the site gets through its first two days without avoidable support issues. Watch access logs, email queues, SSL renewal status, and backup jobs. Then fix anything that looks unstable while the change is still fresh.

If the move exposed a panel mismatch, mailbox problem, or DNS record you forgot to copy, do not improvise. Revisit the test copy, update the live zone, and confirm the fix with a fresh browser session. That is slower for ten minutes and much faster than a rollback later.

FAQ

Should I move email with the website?
Only if you are ready to verify SPF, DKIM, DMARC, and mailbox routing. If mail is business-critical, separate planning helps.

What Ubuntu version should I use for a new hosting server?
Ubuntu 24.04 LTS is the safest default in 2026 for most hosting builds.

Do I need cPanel, Plesk, or DirectAdmin on a VPS?
Use the panel your team can actually manage. The right choice depends on workflow, not brand familiarity.

How do I know if a VPS is enough?
If the site is small, the traffic is steady, and resource use stays low after migration, a VPS is usually fine. If the server keeps hitting limits, move up before users feel it.

What should I test before pointing DNS live?
Test the homepage, login, checkout or enquiry forms, SSL, email sending, uploads, and any cron jobs the site depends on.