Centos 7 and Plex remote access problems with version 1.13.9.5439-7303bc002.
Been reading the forums here seems that last two version of Plex has had a remote access problems. With it saying that not connected when it was connected and could be accessible outside my home network. Today I did update to latest version which happened to be 1.13.9.5439-7303bc002 and it seemed to work for couple hours and then boom nothing works now outside of my home network.
I tried port forwarding that has not help in my router and tried making sure that firewall ports on the server where open and everything still nothing works outside of my home network. When I press the connect button in the server it connect for minute and disconnect after a really long time has well.
Right now when I check the box to use specific public port it will say that it is connected:
Private 200.100.1.107 : 32400 Public : 32400 Internet, But can’t access anything out my home network now. I tried rebuild the server to see if my been a problem with the update that has not worked either and I can access in my home network fine. I was wondering if other people had this problem was well or if anyone has older rpm download of plex before the remote access problems where I can download it.
There was an issue on some back end servers (pubsub servers) that impacted remote access connectivity tests for Plex Media Servers in a number of territories. That was addressed and resolved. The logs posted by @jgingry do show that this was happening at 20:03 GMT on 13th October
The problem was fixed at about 8am GMT on the 14th October
If there are still issues, would need to kow which pubsub server the Plex Media Server is using as these are geographically aligned. We can find out which is used from fresh logs after a restart of Plex Media Server - and can also pick the current value in the server Preferences.xml (for NAS/Linux) or registry for windows - see advanced settings page https://support.plex.tv/articles/201105343-advanced-hidden-server-settings/
The IP address of the current pubsub server can be found in PubSubServer
Restart the server
When the problem occurs, go to server settings for remote access
If remote access is enabled. Refresh the page with F5 button
Wait 5 minutes and then capture screenshot and logs and the setting value for PubSubServer so that we can look into that pubsub server - in the event of failing connectivity tests
Hello looks like their is still a problem with remote access in the software and couple of my users are saying they are getting limited connections now with my server. When I look in remote access in plex app says that not available outside my network when it is configured the same has before I tried with a remote port and without a remote port forwarding enable on my router and still no luck. I uploaded some fresh logs from my server has well for you to look at has well. But at least remote access is working somewhat better than this weekend.
There is no longer any evidence of delays in processing connectivity requests.
The logs show that you are switching between different ports and between manual and automatic port mapping. I would suggest sticking to one approach as the switching between different methods would in itself introduce other potential issues - eg the remote apps may need to be killed off and restarted to pick any changes in the route to the server.
What i can see is that between 18:26 and 18:21 on the 15th October you were using automatic port mapping and the logs show every attempt to get the router to map a port failed. I do not know if you tried restarting the router - there is no evidence of that in this period.
I suspect the issue at this time was a router issue
Oct 15, 2018 18:26:04.326 [0x7fbb8f3ff700] DEBUG - NAT: UPnP, attempting port mapping.
Oct 15, 2018 18:26:16.337 [0x7fbb8f3ff700] DEBUG - NAT: PMP, attempting mapping.
Oct 15, 2018 18:26:16.588 [0x7fbb8f3ff700] DEBUG - NAT: UPnP, attempting port mapping.
Oct 15, 2018 18:26:29.453 [0x7fbb8f3ff700] DEBUG - PublicAddressManager: Mapping failed.
Oct 15, 2018 18:28:55.297 [0x7fbb7d7fe700] DEBUG - PublicAddressManager: Obtaining public address and mapping port.
Oct 15, 2018 18:28:55.297 [0x7fbb8d3ff700] DEBUG - NAT: UPnP, attempting port mapping.
Oct 15, 2018 18:29:07.310 [0x7fbb8d3ff700] DEBUG - NAT: PMP, attempting mapping.
Oct 15, 2018 18:29:07.561 [0x7fbb8d3ff700] DEBUG - NAT: UPnP, attempting port mapping.
Oct 15, 2018 18:29:19.572 [0x7fbb8d3ff700] DEBUG - PublicAddressManager: Mapping failed.
After the restart of the server at 18:33 you switched to manual port mapping and again switching between public port 32400 at one point and 8080 at another. Of course each of these would have needed a port forward to be setup and active in the router forwarding public 32400 at 18:34:46 pm to local port 32400 on and then removing that port forward in the router at 18:34:52 and replacing it with a port forward for public 8080 to local port 32400 as you switched to 8080 - all too close in time and possibly prone to error and not doing it right or allowing the port forward to get established and the route communicated to plex.tv
So my advice is to stick with one method of port forward and one port and get that to work. Do not flip flop between different setups.
So lets go with 32400
Forward that public port in the router to local port 32400 for tcp to go to 200.100.1.107
Delete any uPnP routes you may see in tables in the router for 32400
Ensure that 200.100.1.107 is a DHCP reservation or static outside dhcp range
Reboot the router
On the server, enable remote access, select show advanced and tick manually specify port and enter public port 32400 and select apply
Then Enable Remote Access if it got disabled (this happens when switching between automatic and manual )
At this point I suggest restarting the server
It is very possible that there was a router issue at some point which may have resolved itself by restarting the router
For your manual port selections, these log entries suggest that there was a router issue at the time or you did not have the port forwards for 32400 and 8080 setup in the router. they are only 30 second a part so did you change port forward in the router in this time?
(I notice your local network subnet has non standard IP range 200.100.1.xx - any reason for that ? Use of Non Private Subnet range brings in complications and they get treated as WAN)
