You set up Plex, opened a port on your router, shared it with friends and family, and moved on. Sound familiar? Most Plex servers are running with default security settings that expose more than they need to. Let’s fix that.
This isn’t a paranoia guide. It’s practical steps that protect your server, your network, and your data without making Plex harder to use.
The Biggest Risk: Your Open Port
When you enable remote access, port 32400 on your router is open to the entire internet. Anyone who finds it can reach your Plex server. Plex’s authentication handles the “who can log in” part, but the port itself is discoverable by port scanners in minutes.
What to Do
- Change the default port. In Plex Settings → Remote Access, set a custom port (any number between 1024-65535 that’s not already in use). Update your router’s port forward to match. This doesn’t prevent targeted attacks but eliminates drive-by scanning that specifically looks for 32400.
- Consider Tailscale or Cloudflare Tunnel. These tools let remote users connect without any open ports on your router. Tailscale creates an encrypted mesh VPN; Cloudflare Tunnel routes traffic through their network. Both are free for personal use.
Authentication: Beyond the Basics
Plex accounts are your first line of defense. Here’s what most people miss:
Enable Two-Factor Authentication (2FA)
Go to plex.tv/users/edit and enable 2FA on your admin account. If someone gets your Plex password (phishing, data breach, password reuse), 2FA stops them from accessing your server.
Use Managed Users for Sharing
When you share your server with friends and family, use “managed users” (Home → Manage Users) rather than sharing via their full Plex accounts. Managed users:
- Can’t see your server settings or admin pages
- Can be restricted to specific libraries
- Can have content rating filters applied
- Can be removed instantly without affecting their Plex account
Network Segmentation
Your Plex server has access to your entire home network by default. If it’s compromised, an attacker can reach every device on your LAN.
The Fix: VLAN or Separate Subnet
If your router supports VLANs (most prosumer routers and all enterprise gear), put your Plex server on its own VLAN. It only needs:
- Internet access (outbound for plex.tv communication and updates)
- Access to your media storage (if on a NAS, allow traffic to the NAS IP only)
- Inbound on its streaming port (32400 or custom)
Block everything else. If someone exploits a vulnerability in Plex, they’re stuck on an isolated network segment.
Keep Plex Updated
This sounds obvious but we see servers running versions from 2024 regularly. Plex has had real security vulnerabilities — including one in 2022 that allowed unauthenticated access to server data. Updates fix these.
- Docker users: Pin to
latesttag or use Watchtower for automatic updates - Bare metal: Enable automatic updates in Plex Settings → General
- Manual: Check plex.tv/media-server-downloads monthly
HTTPS and Encryption
Plex supports encrypted connections but the default behavior is “preferred” not “required.” This means connections can fall back to unencrypted HTTP.
The Fix
In Plex Settings → Network, set “Secure connections” to Required. This forces all connections to use HTTPS. Note: this may cause issues with very old clients that don’t support TLS. If a specific device stops connecting, you can add it to the “List of IP addresses and networks that are allowed without auth” for local-only access.
Disable DLNA and GDM If Not Needed
Plex has two discovery protocols enabled by default:
- DLNA: Lets non-Plex devices discover and stream from your server without authentication. Turn this off unless you specifically use DLNA devices (some smart TVs, PlayStation).
- GDM (G’Day Mate): Plex’s server discovery protocol. Safe on a trusted LAN but unnecessary if your clients are configured to connect to a specific server.
Disable both in Settings → DLNA and Settings → Network → “Enable local network discovery (GDM).”
Monitor Access Logs
Plex doesn’t have great built-in logging, but Tautulli (free, open-source) gives you detailed logs of who connected, from where, and what they watched. Set up notifications for logins from unfamiliar IPs.
Quick Security Checklist
- ☑ 2FA enabled on admin Plex account
- ☑ Custom port (not 32400) or zero-port solution (Tailscale/CF Tunnel)
- ☑ Secure connections set to “Required”
- ☑ DLNA disabled (unless actively used)
- ☑ Plex server is on latest version
- ☑ Managed users for shared access (not full account shares)
- ☑ Tautulli monitoring active
- ☑ Server on its own VLAN or subnet (advanced)
Want a Security Audit?
Not sure what’s exposed? Our remote sessions include a full review of your Plex server’s security settings, network exposure, and access controls. We lock it down and walk you through what we changed.