VPS Server Setup

Last updated: March 23, 2026 · 2 min read

Server & Infrastructure

VPS Server Setup

A freshly provisioned VPS is a blank server with a root password and a clock running against your security exposure window. Every hour it sits unconfigured with default settings and password authentication enabled, automated scanners are probing it. Most VPS providers hand you an IP address and say good luck – the setup is your problem.

We provision VPS servers from the initial OS image to a production-ready state: hardened, configured for your application, with backups running and a documented deployment workflow.

SSH hardening, UFW firewall, fail2ban
Apache or Nginx, PHP, MySQL/MariaDB
Let’s Encrypt SSL with HTTPS redirect and HSTS
Daily backups to S3, Backblaze B2, or equivalent
Application installed and verified running
Configuration document delivered on completion

Need a VPS provisioned?

[mmedia_services_wizard id=”vps-server-setup”]

How it works
Step 1
Scope the setup

Provider, OS preference, what you’re hosting, PHP version, and any specific requirements (multisite, Redis, etc.).

Step 2
Harden and install stack

Non-root user, SSH key auth, UFW firewall, fail2ban, then Apache/Nginx, PHP (version for your app), MySQL/MariaDB.

Step 3
SSL, backups, app deploy

Let’s Encrypt with auto-renewal, daily off-server backup configuration, application installation and verification.

Step 4
Documentation delivery

Full configuration document: what was installed, every decision made, all file locations, and what credentials to rotate and when.

Provider Compatibility

DigitalOcean, Linode/Akamai, Vultr, Hetzner, and AWS EC2. We provision on Ubuntu LTS and Debian; CentOS/AlmaLinux available on request. If you have a preferred provider not listed, ask — we’re familiar with most major VPS platforms.

Why M Media
Hardened from the start

SSH key auth, password auth disabled, non-standard port, and fail2ban – before any application is installed.

Production-tuned stack

PHP production php.ini, OPcache, MySQL sized for your server RAM – not tutorial defaults.

Backups to off-server storage

Daily dumps and file backups to S3 or B2 — not just to a different folder on the same server.

SSL and HSTS included

Let’s Encrypt with auto-renewal, HTTPS redirect, and HSTS header – part of every engagement.

App deployed and verified

WordPress or your PHP application is installed and confirmed working before handoff – not just a stack with no app on it.

Documented baseline

Future developers start with a known configuration – not archaeology from a server someone set up once and never documented.

←
Back to Server & Infrastructure

🤖
Support Bot
"Have you tried restarting your computer? Please check our knowledge base. Your ticket has been escalated. Estimated response: 5-7 business days."
❌ Corporate Script Theater
👨‍💻
Developer (M Media)
"Checked your logs. Line 247 in config.php — the timeout value needs to be increased. Here's the exact fix + why it happened. Pushed a patch in v2.1.3."
✓ Real Technical Support

Support From People Who Understand the Code

Ever contact support and immediately know you're talking to someone reading a script? Someone who's never actually used the product? Yeah, we hate that too.

M Media support means talking to developers who wrote the code, understand the edge cases, and have probably hit the same problem you're dealing with. No ticket escalation theatrics. No "have you tried restarting?" when your question is clearly technical.

Documentation written by people who got stuck first. Support from people who fixed it.

We don't outsource support to the lowest bidder or train AI on canned responses. When you ask a question, you get an answer from someone who can actually read the logs, check the source code, and explain what's happening under the hood.

✓ Real troubleshooting, not corporate scripts
✓ Documentation that assumes you're competent
✓ Email support that doesn't auto-close tickets
✓ Updates based on actual user feedback
// real.developer.js
const approach = {
investors: false,
buzzwords: false,
actualUse: true,
problems: ['real', 'solved']
};
// Ship it.

Built by People Who Actually Use the Software

M Media software isn't venture-funded, trend-chasing, or built to look good in pitch decks. It's built by developers who run their own servers, ship their own products, and rely on these tools every day.

That means fewer abstractions, fewer dependencies, and fewer "coming soon" promises. Our software exists because we needed it to exist — to automate real work, solve real problems, and keep systems running without babysitting.

We build software the way it used to be built: practical, durable, and accountable. If a feature doesn't save time, reduce friction, or make something more reliable, it doesn't ship.

✓ Every feature solves a problem we actually had
✓ No investor timelines forcing half-baked releases
✓ Updates add value, not just version numbers
✓ Documentation written by people who got stuck first

This is software designed to stay installed — not be replaced next quarter.