Get Early Access

← Blog

How to Access Plex Remotely Without Opening Ports

Port forwarding is not the only option

The standard advice for Plex remote access is to open port 32400 on your router. This works but exposes your Plex server directly to the internet, where automated bots will find and probe it within hours. Any vulnerability in Plex Media Server becomes a direct attack vector into your home network. For a home server shared with family and friends, there are safer alternatives that provide full-speed remote access without punching holes in your firewall or exposing services to the public internet.

Why port forwarding fails for many users

Beyond security concerns, port forwarding simply does not work in several common situations. Carrier-grade NAT assigns your router a private IP address behind the carrier network, making inbound connections impossible. Double NAT from a modem-router combo followed by your own router creates forwarding conflicts. Some ISPs actively block inbound traffic on common ports. In all these cases, you need an alternative approach that creates outbound tunnels rather than relying on inbound connections.

Option one: Plex relay

Plex has a built-in relay that works automatically when direct connections fail. The server routes streams through Plex relay servers without any configuration on your part. The significant limitation is that relay connections are bandwidth-capped at 2 Mbps for Plex Pass subscribers and 1 Mbps for free users. That cap limits quality to roughly 720p at best and makes high-bitrate content unwatchable. The relay exists as a fallback so remote playback does not completely fail, but it is not a viable primary solution for regular use at reasonable quality levels.

Option two: Tailscale or ZeroTier VPN mesh

For most users, a peer-to-peer VPN mesh is the simplest and most secure solution. Tailscale and ZeroTier create encrypted direct connections between your devices without any port forwarding or exposed services.

Install the software on your Plex server and on each client device. Both devices join your private network and receive private IP addresses in a dedicated range. Point the Plex client at the private IP of your server on port 32400, and traffic flows directly between devices through NAT traversal with end-to-end encryption using WireGuard for Tailscale or its own protocol for ZeroTier.

Tailscale is free for up to 100 devices and takes approximately five minutes to configure from scratch. Create an account, install the client on your server and each device, authenticate each one, and you have a private network. The only limitation is that every remote user needs to install the Tailscale app on their device, which limits this approach to technically comfortable friends and family members who are willing to add an app.

ZeroTier provides similar functionality with a slightly different management model. You create a network through the web console and authorize devices as they join. The free tier supports up to 25 devices on one network. Both services handle NAT traversal automatically and fall back to relay servers when direct peer-to-peer connections are not possible.

Option three: Cloudflare Tunnel

Cloudflare Tunnel creates an outbound-only connection from your server to Cloudflare edge servers. Remote users access your Plex through a subdomain on a Cloudflare-managed domain with no ports open on your router and no VPN software required on the client side. You install the cloudflared daemon on your server, configure it to forward traffic from a hostname to localhost port 32400, and set the Custom server access URLs in Plex settings to match.

The advantages are significant: no client-side software needed, DDoS protection from Cloudflare, and the connection works behind any NAT configuration. The concerns are that Cloudflare Terms of Service have historically been interpreted as prohibiting sustained video streaming through their free tier, meaning your tunnel could theoretically be terminated. Additionally, all your video traffic routes through Cloudflare infrastructure which adds a small amount of latency to every stream compared to a direct connection.

Comparison of remote access methods

MethodSetup difficultyClient setup required4K capableSecurity
Plex RelayNoneNoneNo, 2 Mbps capEncrypted by Plex
TailscaleEasyApp on each deviceYes, full speedWireGuard encrypted
ZeroTierMediumApp on each deviceYes, full speedEnd-to-end encrypted
Cloudflare TunnelMediumNoneYes with caveatsHTTPS encrypted
Port ForwardingEasyNoneYesExposes port publicly

Setting Custom server access URLs

Whichever method you choose, configure the Custom server access URLs field in Plex Settings under Network. This tells Plex how remote clients should reach your server through the tunnel or VPN. Without this setting, Plex tries its default remote access mechanism which requires port forwarding and marks the server as unreachable even when the tunnel is working perfectly.

For Tailscale, set the URL to your server Tailscale IP on port 32400. For Cloudflare Tunnel, set it to your subdomain on port 443 with HTTPS. For ZeroTier, use the ZeroTier-assigned IP on port 32400.

Choosing the right method

For sharing with your own devices and household members, Tailscale provides the simplest secure path. For sharing with friends who will not install extra software, Cloudflare Tunnel makes access transparent from the client side. For users behind CGNAT who need the most reliable connection, a VPN mesh handles NAT traversal automatically where port forwarding is impossible. All of these methods are substantially more secure than exposing port 32400 directly to the public internet.

Ready to offload your transcodes?

Join the pre-beta waitlist and lock in 50% off for life.

Claim My Early-Adopter Spot →
More from LuxuriousComputers: LuxuriousComputers · Computer Repair · Remote Fix · Phone Repair · HVAC · Plex Support