Since each region is a little different,
-
On any command line, lookup the IP addresses..
-
You’ll get the IP addresses in the response.
( Don’t confuse www.plex.tv or forums.plex.tv with ‘plex.tv’. They are all distinct services. (main web page, our forum server, and ‘plex.tv’)
[chuck@lizum ds.2028]$ nslookup plex.tv
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: plex.tv
Address: 54.216.77.33
Name: plex.tv
Address: 34.251.159.167
Name: plex.tv
Address: 18.202.201.67
[chuck@lizum ds.2029]$
- You’ll also need to read through your Plex Media Server.log (right after startup) to get the IP addresses used for Remote Access. This log file entry shows me I need to go back and add this IP address to my PlexRemoteAccess alias list.
You will probably iterate on this a few times until you get it but that’s what it takes for keeping the firewall tight.
Apr 19, 2023 19:02:46.757 [0x7f98d210e0] WARN - [EventSourceClient/pubsub/172.104.213.234:443] MyPlex: attempted a reachability check but we're not yet mapped.
Apr 19, 2023 19:02:46.757 [0x7f98d210e0] DEBUG - [EventSourceClient/pubsub/172.104.213.234:443] Successfully connected to 172.104.213.234.
Everyone’s firewall is different and we all use them differently.
I use PfSense and I control access to my server.
Here’s my process. Your process should be kinda similar in that you specify
– Source addresses (plex.tv)
– You’re port forwarding (NAT)
– The redirected (target) IP address and port are that of your Plex server
-
I create an Alias (Name) for all Plex.tv
-
I create the NAT (port forwarding) rule to forward
– traffic coming in on the WAN adapter
– coming from any hosts in the “PlexRemoteAccess” alias list
– forward it to my server at 192.168.0.20:32400
That’s it. Now I’ll test.
I’ll flip remote access on and off a few times then pull the logs.
If I’ve missed any IP addresses, I’ll go back, add them to the Alias, and retest until I have sustained success.
When all done,
