Set Up Plex Remote Access With Port Forwarding
Published 2026-10-16 · PlexBeam
Plex remote access lets you stream your media library from anywhere — your phone on a commute, a laptop in a hotel, a friend's TV across the country. It works by making your Plex server reachable from the internet through your router. This requires port forwarding: telling your router to send incoming connections on a specific port to your Plex server. This guide covers the complete setup process, from server configuration to router configuration to verification.
How Remote Access Works
When you are away from home and open the Plex app:
- Your Plex app contacts plex.tv to find your server's public IP address and port.
- Your app connects to your public IP on port 32400 (or your custom port).
- Your router receives the connection and forwards it to your Plex server on the local network.
- Your Plex server authenticates you and starts streaming.
For this to work, two things must be true: your router must forward port 32400 to the server, and your Plex server must be configured to accept remote connections.
Step 1: Configure Plex for Remote Access
- Open the Plex web interface:
http://server-ip:32400/web - Go to Settings > Remote Access.
- Check Manually specify public port and set it to 32400 (or a custom port if you prefer).
- Click Retry or Enable Remote Access.
Plex will attempt to establish remote access. If your router has UPnP enabled, Plex may configure port forwarding automatically. If not (or if UPnP fails), you will see a red warning — this means you need to manually configure port forwarding on your router.
Step 2: Assign a Static Local IP to Your Server
Port forwarding rules point to a specific local IP address. If your server's IP changes (via DHCP), the rule breaks. Fix this before configuring port forwarding.
Option A: Static IP on the Server
Configure the server's network interface with a static IP outside your router's DHCP range.
On Linux, edit the network configuration (Netplan, NetworkManager, or /etc/network/interfaces depending on your distribution):
ip: 192.168.1.100
gateway: 192.168.1.1
dns: 1.1.1.1, 8.8.8.8
Option B: DHCP Reservation on the Router
Log into your router and find the DHCP settings. Create a reservation that always assigns the same IP to your server's MAC address. This is simpler than a static IP on the server and is managed centrally.
Find your server's MAC address: on Linux, run ip addr; on Windows, run ipconfig /all.
Step 3: Configure Port Forwarding on Your Router
Every router's admin interface is different, but the process is the same:
- Log into your router's admin page. The address is typically
192.168.1.1or192.168.0.1. Check the sticker on your router for the exact address and default credentials. - Navigate to the port forwarding section. It may be under Firewall, NAT, Port Forwarding, Virtual Servers, or Applications & Gaming depending on the router brand.
- Create a new port forwarding rule with these settings:
- Service/Application Name: Plex (or any descriptive name)
- Protocol: TCP
- External Port: 32400 (or your custom port)
- Internal Port: 32400
- Internal IP: Your Plex server's static local IP (e.g., 192.168.1.100)
- Save the rule.
Router-Specific Instructions
Netgear: Advanced > Advanced Setup > Port Forwarding / Port Triggering > Add Custom Service.
TP-Link: Advanced > NAT Forwarding > Virtual Servers > Add.
ASUS: Advanced Settings > WAN > Virtual Server / Port Forwarding > Add Profile.
Linksys: Security > Apps and Gaming > Single Port Forwarding.
Ubiquiti UniFi: Settings > Routing > Port Forwarding > Create New.
OPNsense / pfSense: Firewall > NAT > Port Forward > Add.
Step 4: Verify Remote Access
- Go back to Plex Settings > Remote Access and click Retry.
- If configured correctly, you will see a green checkmark and the message "Fully accessible outside your network."
- Test from outside your network: use your phone on cellular data (turn off Wi-Fi) and open the Plex app. If you can browse and play content, remote access is working.
External Port Check
If Plex still shows a red warning, verify the port is actually open from the internet. Search "port checker" online and check your public IP on port 32400. If the port shows as closed, the router rule is not working — double-check the internal IP, port numbers, and protocol (must be TCP).
Using a Custom Port
Some ISPs block port 32400 or scan for common server ports. Using a custom port avoids this and adds a thin layer of obscurity.
- In Plex, go to Settings > Network > Custom server access URLs.
- Under Remote Access, check "Manually specify public port" and enter a custom port (e.g., 42400 or 52400).
- Update your router's port forwarding rule: set the external port to your custom port, internal port to 32400.
Plex still listens on 32400 internally — only the external-facing port changes.
Security Considerations
Opening a port to the internet exposes your Plex server to anyone who discovers your IP. Plex requires authentication, but there are additional steps to improve security:
- Keep Plex updated: Plex regularly patches security vulnerabilities. Enable automatic updates or check frequently.
- Use a strong Plex account password with two-factor authentication enabled at plex.tv.
- Enable "Require secure connections" in Plex: Settings > Network > Secure connections: Required. This forces all connections to use HTTPS/TLS encryption.
- Restrict who can access: Under Settings > Network > List of IP addresses and networks that are allowed without auth — keep this empty or limited to your LAN. Do not add 0.0.0.0/0 (which allows unauthenticated access from anywhere).
- Disable UPnP on your router after setting up manual port forwarding. UPnP can be exploited by malicious software to open ports without your knowledge.
Dynamic DNS for Changing IPs
Most residential ISPs assign dynamic public IP addresses that change periodically. When your IP changes, Plex usually detects the new IP automatically through plex.tv. But if you use custom server access URLs or share your server address directly, a dynamic DNS service keeps a hostname pointed at your current IP:
- DuckDNS (free): Create a subdomain like
myplex.duckdns.org. Run a small update script on your server that pings DuckDNS every 5 minutes with your current IP. - No-IP (free tier available): Similar service with more hostname options.
- Cloudflare DNS: If you own a domain, use Cloudflare's API to update a DNS record automatically. Free and fast.
Troubleshooting
Red Warning in Plex: Not Available Outside Your Network
- Port forwarding not configured or incorrect: Verify the rule exists in your router. Check that the internal IP matches your server and the port is 32400 (TCP).
- Double NAT: If your router's WAN IP is a private address (10.x.x.x, 172.16-31.x.x, 192.168.x.x), you are behind double NAT. See our double NAT troubleshooting guide.
- ISP blocking the port: Try a custom port above 10000. Some ISPs block common server ports on residential connections.
- Firewall on the server: If your server runs a software firewall (ufw, iptables, Windows Firewall), ensure port 32400 is allowed for incoming TCP connections.
Intermittent Access
If remote access works sometimes but drops periodically:
- Your public IP may be changing (DHCP from ISP). Set up dynamic DNS.
- Your server's local IP may be changing (DHCP from router). Set a static IP or DHCP reservation.
- Your router may be rebooting or losing its port forwarding rules. Some consumer routers lose custom rules after firmware updates — re-check after any router update.