Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Security

VPS security checklist for a new Linux server

Published August 2026 · 12 min read

A new VPS is usually reachable from the public internet before it contains anything valuable. That makes the first configuration decisions disproportionately important.

Patch before building on top

Install current security updates before deploying the application stack. Reboot when core components require it while the server is still easy to interrupt.

Use controlled administrative access

Prefer SSH keys over reusable passwords, protect private keys, and remove accounts that do not need access. Where the operating model allows it, use a normal administrative user with privilege escalation and reserve direct root login for cases that genuinely require it.

Expose only the services users need

A public web server commonly needs HTTP and HTTPS; it does not automatically need a public database, cache service, metrics endpoint, or management interface.

Use host and provider firewalls deliberately. Binding an internal service to every interface creates unnecessary exposure.

Separate applications and secrets

Run services with appropriate non-root identities and keep application secrets out of public repositories and web-accessible directories. Rotate credentials that were exposed during development or copied through insecure channels.

Make backups independent of the server

A backup stored only on the same VPS is vulnerable to the same disk failure, compromise, deletion, or provider incident. Keep recoverable copies elsewhere and test a restore process.

Monitor the things that fail quietly

Track disk space, memory pressure, service health, certificate expiry, backup success, unusual authentication activity, and availability from outside the server.

Common questions

Is changing the SSH port enough to secure SSH?

No. A non-default port can reduce background noise, but authentication policy, key protection, patching, firewall rules, and account controls are the important security boundaries.

Next step

A practical Linux VPS hardening checklist covering access, updates, firewall rules, service exposure, backups, logs, TLS, secrets, and monitoring.

Explore VPS hosting

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Linux file permissions: ownership, modes, groups and ACLs explained

Understand Unix ownership and rwx modes, then use groups and ACLs where needed so services can access files without opening them to every user.

Read the guide

Moving a DreamHost VPS to Canadian hosting

Inventory the server, copy it safely, test it, and cut DNS over with a rollback plan.

Read the guide

More vps & linux guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move