Skip to sign-up
Plex remote access

Access your Plex server from anywhere.

Portless gives your Plex server a stable public HTTPS URL without router port forwarding. It works behind CGNAT, double NAT, blocked port 32400, and dynamic IPs.

Start free trial Read setup guide
No router setup Works behind CGNAT 7-day free trial
why port forwarding fails

Most Plex remote access failures are inbound network problems

Plex's normal remote-access path expects inbound traffic to reach your server. Many residential networks do not allow that anymore.

CGNAT

Your ISP shares one public IPv4 address across many customers. Your router cannot receive unsolicited inbound traffic.

Double NAT

Two routers or modem/router layers both need forwarding rules. One missed layer breaks Plex remote access.

Blocked port 32400

Some ISPs and routers block or rewrite inbound ports. Plex's default public port never reaches the server.

Dynamic IPs

Your home IP changes after a reboot or lease renewal, and remote access disappears until discovery catches up.

Router security

Opening inbound ports creates another surface to manage. Many users would rather keep the home router closed.

Plex Relay fallback

Relay is useful, but it is a fallback path with documented stream constraints. It is not the same as direct remote access.

portless path

Portless flips the connection direction

Instead of waiting for the internet to reach your home, the Portless client connects out from your home to Portless. Viewers use your public HTTPS URL, and Portless forwards requests through that existing tunnel.

01

Run the Portless client next to Plex

The Portless client reaches Plex locally through PORTLESS_PMS_URL, such as http://127.0.0.1:32400, http://plex:32400, or a LAN IP.

02

Connect outbound to Portless

The Portless client uses your PORTLESS_DEVICE_TOKEN to establish authenticated control and tunnel sessions.

03

Use your public Plex URL

Your assigned subdomain receives browser-trusted HTTPS and forwards Plex traffic through the Portless client. There is no public inbound port on your router.

when to choose portless

Use Portless when normal Plex remote access is not available

If port forwarding works and you are comfortable maintaining it, it is still a valid option. Portless is for the cases where it does not work or is not worth the router exposure.

option good fit not ideal when
Port forwarding You have a real public IPv4 address and control the router. You are behind CGNAT, double NAT, or blocked inbound 32400.
Plex Relay You need a quick fallback and can accept Relay limits. You want normal remote Plex streaming quality.
Tailscale You control every viewer device and want a private mesh. Family watches on TVs, Roku, consoles, or devices that should not join your tailnet.
Cloudflare Tunnel You want a general-purpose HTTP tunnel. You want a setup built specifically around Plex remote access and streaming behavior.
Portless You want a stable public HTTPS Plex URL without router changes. You do not want to run the Portless client next to Plex.

Access your Plex server from anywhere

Claim a subdomain, run the Portless client, and point Portless at your local Plex URL. Start with a 7-day free trial; Pro is $2.99/mo or $29.99/yr after that.

Start free trial Setup guide
faq

Plex remote access questions

How does the free trial work?
Start with a 7-day free trial. Pro is $2.99/mo or $29.99/yr after that.
Does Portless need port 32400 open?
No. Plex can keep listening locally on 32400, but your router does not need to forward 32400 from the internet.
What if my Plex server is in Docker?
Run the Portless client in the same Docker environment. Use http://plex:32400 if both containers share a Docker network, or http://127.0.0.1:32400 with host networking.