Server remote reachable … unavailable … reachable … unavailable … reachable … unavailable … etc. When will you finally solve this problem? Please stop the development of these online media and focus on making the ESSENTIAL work! We do not need your web shows if we can not access our OWN media remotely. Not cool 
4 Likes
As of today…I too have a problem with nobody able to access my Plex remotely even though the server reports that remote access is “Fully Accessible”. The server was regularly dropping remote connections since the last update but would be OK after I forced a new connection. Today remote access simply not working at all. 
Any help would be appreciated.
2 Likes
My server is showing it is fully accessible remotely. Checked the ports were open, rebooted router and I still cant get remote access from multiple devices.
I wonder why I still pay for this service? They could at least update there plex status page and state there is a problem but as usual it states everything is up and running fine on there side!
I’m beginning to think they really don’t give a _____! Absolutely no recognition of the issue!
4 Likes
Kinda insane they dont even say they r aware of it and looking
Oddly enough, since leaving my message I was playing with various settings in Plex and Windows. Since my Plex was fine locally, on a lark I created a Windows firewall rule to fully open the Plex server port for use by any apps…and…now my Plex is working fine!! I had NOT previously touched ANY of the firewall setting in the past!!!
It seems to me that for Plex, there is no longer an important goal for us to be able to remotely stream our media. Plex wants to place his web shows.
Logs please covering time when it becomes unavailable
Ensure debug logging enabled
See https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
restart the server to get fresh logs set created
when the issue arises, note down the times and capture logs
See https://support.plex.tv/articles/200250417-plex-media-server-log-files/
Attach logs together with details of the problem including times
I know you’re just doing your job and I commend you for it, but PLENTY of logs have been posted in the past week. It’s just not true that everyone at once changed their system and port forwarding rules and changed their networks.
The issue is on Plex’s side, fix it.
Yes and issues have been identified - not everyone’s issue is the same
users would be very disappointed if they just wait for a fix only to find that the fix does not address their specific issue.
Having issues with remote access as well.
See my earlier post Remote Access not working - #8 by sa2000
Plex Media Server Logs_2018-11-10_12-27-45.zip (5.0 MB)
Plex Media Server Version 1.13.9.5456
OS X 10.13.6
Thanks for the logs. They show error being returned when PMS attempts to map a port through uPnP
Nov 10, 2018 12:26:18.943 [0x70000ee82000] WARN - NAT: UPnP, error mapping port 17240, error: Invalid Args, controlURL: http://192.168.1.1:5000/Public_UPNP_C3.
Nov 10, 2018 12:26:19.211 [0x70000ee82000] WARN - NAT: UPnP, error mapping port 13927, error: Invalid Args, controlURL: http://192.168.1.1:5000/Public_UPNP_C3.
Nov 10, 2018 12:26:21.456 [0x70000f00b000] WARN - NAT: UPnP, error mapping port 29096, error: Invalid Args, controlURL: http://192.168.1.1:5000/Public_UPNP_C3.
Nov 10, 2018 12:26:21.721 [0x70000f00b000] WARN - NAT: UPnP, error mapping port 13122, error: Invalid Args, controlURL: http://192.168.1.1:5000/Public_UPNP_C3.
Could you check that uPnP and NAT are enabled in the router
If the problem persists, could you look into using wireshark to capture the Plex Media Server communication with the router
Download Wireshark · Download
Please save to pcap file and zip and send me in private message
and upload corresponding logs
Once you have done that, you could try to set it up through a manually created port forward in the router
- make sure 192.168.0.2 is dhcp reserved or static outside dhcp range
- choose a public port - it could be 32400
- create a port forward in the router for the public port to forward using tcp protocol to port 32400 to 192.168.0.2
- in remote access server settings with show advanced, tick manually specify port and enter the public port you forwarded to 32400
further to my earlier reply, found a reference to this router uPnP error here miniupnp.tuxfamily.org :: View topic - Trying to add port forward but get: 402 Invalid args
If the problem is the same and due to number of uPnP mapped ports, a restart of the router ought to resolve - but suggest you also restart the Mac after restarting the router
And do consider switching to a manually specified port and a port forward setup by you in the router. it is a more reliable option
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
