Install Plex on a VPS (Media Server Guide)

Plex on VPS: What Works and What Is Risky

Yes — with one honest caveat about copyright. What works on a VPS: remote access everywhere, family-account sharing, no home-upload bottleneck, and a server that never sleeps. What needs care: transcoding is CPU-hungry (one 1080p transcode ≈ 2 fast cores; 4K transcodes are for dedicated hardware), storage fills faster than home NAS, and — the real constraint — your library must be content you have the rights to host; VPS providers terminate accounts for pirated media, and we are no exception.

• Sizing — 1–2 GB per SD movie, 4–8 GB per 1080p film, 15–60+ GB per 4K remux.

• Bandwidth — a 1080p stream pulls 3–8 Mbps sustained; concurrent viewers multiply it.

• Direct play beats transcode — matching client formats avoids CPU cost entirely.

Install steps follow below; the managed media option sits on Plex hosting, raw boxes on the VPS server tiers.

Sizing: Storage, Bandwidth and CPU for Transcodes

On Plex Media Server, the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

Step 1: Install Plex Media Server on Ubuntu

On media library storage, the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

Step 2: Claim Your Server (Port 32400)

Claim Your Server (Port 32400). Allow 80 and 443 to the world, and restrict SSH (22) or RDP (3389) to known IPs. A site that times out after a firewall change is usually a closed web port, not a dead server. If you lock yourself out, use the console in the client area or email support@webji.services before you reboot in a loop.

Step 3: Remote Access and Library Setup

On port 32400, the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

Storage Plans and Bandwidth Math

Bandwidth is how much data the site may transfer; disk is how much you may store; inodes are how many files you may have. A backup plugin that never deletes old copies fills inodes before it fills gigabytes. Check the panel's usage page before you upgrade on a guess.

Plex vs Jellyfin (Self-Hosted Picks)

The honest comparison. Plex: polished clients on every platform, remote access that mostly just works, but account sign-in, some paywalled features (hardware transcoding sits behind Plex Pass) and metadata phones home. Jellyfin: fully open source, no accounts or fees, hardware transcode free — at the cost of client apps that are good rather than great and remote access that wants manual tunnel or reverse-proxy setup.

Pick Plex for family-scale use where the least technical member must also succeed; pick Jellyfin when licence purity and zero fees outrank polish. Both run on the same VPS spec — the deciding factor is your household, not the hardware. Either way, snapshot before version upgrades; media servers are the classic case for a quick rollback path.