I’ve been using remote access just fine via port 32400 (manually checked off in the remote access settings) since day 1. Today I tried to change it to a different port (52400) by doing the following:
Change the NAT rule in pfSense from a destination port of 32400 to the 52400.
Change the manually specified public port in the Remote Access settings to 52400 and hit Apply
This did not work as it just said connecting for the longest time and then came back saying the following:
Meanwhile, while it is “connecting” I see incoming connections from Plex’s servers 54.x.x.x on port 32400 (being blocked of course since the NAT rule was changed). I’ve tried creating simultaneous NAT rules, one for port 52400 and 32400 in case maybe it just needs to talk over both the first time the change is made but no dice.
I’m at a loss for why this is not working. I see no reason why Plex’s servers should be trying to connect to my server over any port other than 52400 once I’ve manually changed it and confirmed it as such in the Preferences.xml.
Meanwhile I have a second Plex server running on a different manually specified port just fine and has been since day 1.
The server itself is only going to look at 32400 no matter what you do. The setting in that box is for external connections (IE plex.tv and apps). So when you specify a port you need to use pfsense to forward traffic from 52400 to 32400 on the server’s IP address.
@jmckee said:
The server itself is only going to look at 32400 no matter what you do. The setting in that box is for external connections (IE plex.tv and apps). So when you specify a port you need to use pfsense to forward traffic from 52400 to 32400 on the server’s IP address.
Already done this, that’s how my NAT rules have been since day one. Destination port of 32400 forwards to local port 32400. I tried changing that to destination port 52400 forwards to local port 32400 but no dice.
@drinehart said:
Sign out of your server on the General tab, then sign back in.
Will try this once my server is idle and report back.
@jmckee said:
The server itself is only going to look at 32400 no matter what you do. The setting in that box is for external connections (IE plex.tv and apps). So when you specify a port you need to use pfsense to forward traffic from 52400 to 32400 on the server’s IP address.
Already done this, that’s how my NAT rules have been since day one. Destination port of 32400 forwards to local port 32400. I tried changing that to destination port 52400 forwards to local port 32400 but no dice.
I must have misread. Do you also have a router before your server or is your server connected directly to the WAN?
The connection is initiated from your server telling Plex.tv your settings so you would not need to have both ports forwarded. Your logs should tell you what is happening when your server is trying to connect to plex.tv to report its change. But even without that with the ports properly forwarded you should be able to goto canyouseeme.org and hit your WAN:52400 port and get the We can see your service message
@jmckee said:
The server itself is only going to look at 32400 no matter what you do. The setting in that box is for external connections (IE plex.tv and apps). So when you specify a port you need to use pfsense to forward traffic from 52400 to 32400 on the server’s IP address.
Already done this, that’s how my NAT rules have been since day one. Destination port of 32400 forwards to local port 32400. I tried changing that to destination port 52400 forwards to local port 32400 but no dice.
I must have misread. Do you also have a router before your server or is your server connected directly to the WAN?
The connection is initiated from your server telling Plex.tv your settings so you would not need to have both ports forwarded. Your logs should tell you what is happening when your server is trying to connect to plex.tv to report its change. But even without that with the ports properly forwarded you should be able to goto canyouseeme.org and hit your WAN:52400 port and get the We can see your service message
My WAN comes into my router (pfSense) and my server is connected via the LAN interface on my router. The NAT rule is setup properly as canyouseeme.org’s test does work. I will try logging out and back into my server as drinehart recommended shortly.
Ok logging out and back in doesn’t work. Even though I’m specifying port 52400 and it’s listed in my Preferences.xml, it’s still trying to use port 32400 as seen in this log entry when I try to apply it. Logging out and back in and restarting the server does nothing.
Jun 02, 2016 13:05:16 [0x7fdb1a7ff700] DEBUG - MyPlex: Sending Server Info to myPlex (user=MY_EMAIL_ADDRESS, ip=, port=0) Jun 02, 2016 13:05:16 [0x7fdb1a7ff700] DEBUG - HTTP requesting POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx Jun 02, 2016 13:05:20 [0x7fdb38bfe700] DEBUG - EventSource: Got event [data] '<Message address="MY_WAN_IP" port="32400" connectivity="0" command="notifyConnectivity"/>'
Was there any Error 52 in the Plex Media Server.log - normally that would be the clue to look for MTU Size and Jumbo Frames
The checklist on the Troubleshooting Remote Access support page does have Jumbo Frames listed as something to check when there are issues with setting up Remote Access
@sa2000 said:
Was there any Error 52 in the Plex Media Server.log - normally that would be the clue to look for MTU Size and Jumbo Frames
The checklist on the Troubleshooting Remote Access support page does have Jumbo Frames listed as something to check when there are issues with setting up Remote Access
I found the Jumbo Frames issue listing in the Remote Access troubleshooting that’s how I fixed it. I just don’t understand why that’s an issue.
A message used in the remote access setup dialogue with the plex servers hosted in the Amazon Cloud must be bigger than the size that can be handled at the Amazon end - hence the need to ensure MTU Size must not be more than 1500.
