I’m having this same issue with a manual port being set. I’m running the plexms docker container on a host whose lan IP does not change, behind a router with no double NAT. Port forwarding rule is set to TCP only.
This morning I woke up to the remote access page looking like this:
Once I clicked the retry button it came back:
I guess I’ll dig through the plex logs to see what I can find…
yeah, i know, i was talking to “idontwantaname” who said he was using UPnP.
I’m seeing a lot of log lines like:
Jul 19, 2018 10:16:49.429 [0x7f362dfff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (a[redacted], expected b[redacted])
This older post seems hint that it’s caused by either time skew or the request being routed strangely through multiple network interfaces: Remote Access is still not working
This post seems to acknowledge the issue but the plex person never responded back with an ETA: Problem with remote connect & UFW firewall
A far more recent post seems to indicate that Tautulli (What I’m using to monitor the remote accessibility status) should not be performing the check every minute, but that’s kind of the point: Random loss of remote - hundreds of pubsub async errors
I’m going to follow that other latest post and suggest the rest of you do the same since a plex employee is actively engaged.
Since I discovered that this problem happens to me when using uPNP, I’ve switched to manually specifying the port and I haven’t had a problem since (7 days ago)
I am also running Tautulli and I do see these PubSub “warnings” as well
Note that these are older logs:
Jul 11, 2018 21:28:04.625 [0x7fe9837f7700] WARN - NAT: UPnP, error mapping port 23297, error: Unknown Error, controlURL: http://192.168.1.253:56867/ctl/IPConn.
Jul 11, 2018 21:28:06.376 [0x7fe9837f7700] WARN - NAT: PMP, got an error: Network Error.
Jul 11, 2018 21:28:11.427 [0x7fe9837f7700] WARN - NAT: UPnP, error mapping port 15431, error: Unknown Error, controlURL: http://192.168.1.253:56867/ctl/IPConn.
Jul 11, 2018 21:28:12.954 [0x7fe9b43ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (bb06cc87-e04f-4a94-99b4-0f03e87d1719, expected 93c38372-10b0-4db4-a170-8343db19b6d1)
Jul 11, 2018 21:37:37.225 [0x7fe9b3bfe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (23ae6534-3092-4e6d-8dee-34b8fcfe4e18, expected c27caa95-e88c-4797-af78-a3511c5d9e40)
Jul 11, 2018 21:37:45.372 [0x7fe999bff700] WARN - NAT: UPnP, error mapping port 25899, error: Unknown Error, controlURL: http://192.168.1.253:56867/ctl/IPConn.
Jul 11, 2018 21:37:49.124 [0x7fe999bff700] WARN - NAT: PMP, got an error: Network Error.
EDIT: I see that in my Tautulli configuration, I am not monitoring Plex for updates or remote access.
EDIT 2: I also noticed in my Tautulli configuration to use SSL with Plex, but I have that disabled on the Plex side. I have disabled that now.
EDIT 3: I just downloaded/installed PMS 1.13.4.5271 and will enable debugging/uPNP and will update if remote access goes wonky again
I have been experiencing a port forwarding issue as well. I have received Pushover iOS notifications via Tautulli constantly re the disconnection and reconnection of plex remote access loss and reconnection.
It also seems that Tautulli does not like connecting to Plex under ‘Tautulli settings > Plex Media Server > Use SSL’ without it being enabled. I am not able to disable the SSL option and have Tautulli still work and be interconnected with PMS. Unsure if it might be related to the same underlining issue?
Hi,
can you check under the “Network” section if you have a custom URL configured?
ciao
luigi
Since installing PMS 1.13.4.5271 last night:
plexmediaserver.service - Plex Media Server for Linux
Loaded: loaded (/etc/systemd/system/plexmediaserver.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2018-07-20 00:34:21 EDT; 7h ago
I can see that uPNP has cycled through 6 external ports; nearly every hour.
Plex Media Server.log (677.2 KB)
And now remote access is not working
Jul 20, 2018 10:34:28.972 [0x7f5d64fff700] DEBUG - NAT: UPnP, found device http://192.168.1.253:49062/rootDesc.xml with private address <192.168.1.250>
Jul 20, 2018 10:34:28.985 [0x7f5d64fff700] DEBUG - NAT: UPnP, usable device http://192.168.1.253:49062/rootDesc.xml with private address <192.168.1.250>.
Jul 20, 2018 10:34:33.992 [0x7f5d64fff700] WARN - NAT: UPnP, error mapping port 25058, error: Unknown Error, controlURL: http://192.168.1.253:49062/ctl/IPConn.
Jul 20, 2018 10:34:33.993 [0x7f5d64fff700] DEBUG - NAT: PMP, attempting mapping.
Jul 20, 2018 10:34:34.137 [0x7f5d58fff700] DEBUG - NAT: UPnP, not an IGD: http://192.168.1.253:49062/rootDesc.xml.
Jul 20, 2018 10:34:34.137 [0x7f5d58fff700] DEBUG - NAT: UPnP, getPublicIP didn’t find usable IGD.
Jul 20, 2018 10:34:37.745 [0x7f5d64fff700] WARN - NAT: PMP, got an error: Network Error.
Jul 20, 2018 10:34:37.745 [0x7f5d64fff700] DEBUG - NAT: UPnP, attempting port mapping.
Jul 20, 2018 10:34:37.755 [0x7f5d64fff700] DEBUG - NAT: UPnP, usable device http://192.168.1.253:49062/rootDesc.xml with private address <192.168.1.250>.
Jul 20, 2018 10:34:37.889 [0x7f5d58fff700] DEBUG - NAT: PMP::getPublicIP, Received public IP from router: X.X.X.X
Jul 20, 2018 10:34:37.890 [0x7f5d58fff700] DEBUG - MyPlex: Last published value didn’t change, we’re done.
Jul 20, 2018 10:34:42.762 [0x7f5d64fff700] WARN - NAT: UPnP, error mapping port 25058, error: Unknown Error, controlURL: http://192.168.1.253:49062/ctl/IPConn.
Jul 20, 2018 10:34:42.762 [0x7f5d64fff700] DEBUG - PublicAddressManager: Mapping failed.
Jul 20, 2018 10:34:42.767 [0x7f5d64fff700] DEBUG - MyPlex: Sending Server Info to myPlex (user=myemail@domain.com, ip=, port=0)
I have the same issue with 1.13.4.5271 need help to fix this it also shows offline on my iPhone also
If you’re running Tautulli, you might want to watch: Random loss of remote - hundreds of pubsub async errors
I am having the identical problem as @weezypenguin
Was having the same issue, powered down the modem & router, (restarted) the problem persisted.
I then opened the port forwarding settings of both modem & router and erased port forwarding for port 32400, also reset my admin passwords for modem and router.
Powered down modem and router again, log back in to both, reset port forwarding on port 32400, power down modem & router, (re-started) and for now Remote Access seems to be working again.
Can’t explain it, other than I had a really weird crash on my Mac Pro 12 core, that forced the OS to shutdown on its own and ever sense that, couldn’t get remote access working till I did all of the above.
Just powering down the router and modem didn’t work by itself.
If anything changes, I’ll post!
Update:
I went through all the troubleshooting guides and went step by step redoing all the stuff I did to set this up originally and somehow my port forwarding protocol got changed to UDP. So I changed it to TCP and restarted everything and I have the green check mark now and it all seems to be working.
Hope this helps someone.
Plex has now released another PMS update, being Version 1.13.5.5332. It would be great to know if you guys are able to now resolve this remote access issue, thanks
having the same issue, i just had my isp order me a new modem router, as i thought it was the modem/router acting up
been going on for me for 2 weeks now, but i usually dont download new updates as soon as they come out,
remote access continually disconnects multiple times a day, only way i can get it back on is to, unplug my modem, plug it back in, delete my port forwarding and than redo teh port forwarding and than sometimes plex picks it up, if not rinse and repeat a few times till it does,
i just received a new update, right before writing this, thought it would fix it, but looks like its a no go as still having the issue
Update 1.13.6.5339 resolved the issues on my server.
I would mention that I did some work on my firewall, but reverted all changes. I assume the update was what resolved the issue. I also disabled “Manually specified public port”, and re-enabled.
It did not show “Fully Accessible” initially, but a few minutes after the update it looks like it is finally working.
Hopefully this fixes the issue for other users as well…
update did not fix the issue for me tried reverting to a previous version to see if that helps with it but not sure how far back to go as i skipped a few updates before i went to this one, found a site with previous versions of plex on it and chose one, will keep going back versions till i get it to work
Try reverting to 1.13.4.5271-200287a06
It’s the last version that worked for me before all networking failed (in docker).
With uPnP the port mapping is refreshed periodically and if the attempt to do it or communicate with the router control interface fails then Plex Media Server would switch to a different port
For example at 01:34:32 port 23873 was successfully mapped
Jul 20, 2018 01:34:32.826 [0x7f5d6efff700] DEBUG - NAT: UPnP, mapped port 23873 to 192.168.1.250:32400.
An hour later the attempt to refresh the mapping failed
Jul 20, 2018 02:34:25.857 [0x7f5d693fc700] DEBUG - NAT: UPnP, attempting port mapping.
Jul 20, 2018 02:34:28.869 [0x7f5d693fc700] DEBUG - NAT: UPnP, found device <http://192.168.1.253:49062/rootDesc.xml> with private address <192.168.1.250>
Jul 20, 2018 02:34:28.881 [0x7f5d693fc700] DEBUG - NAT: UPnP, usable device <http://192.168.1.253:49062/rootDesc.xml> with private address <192.168.1.250>.
Jul 20, 2018 02:34:33.888 [0x7f5d693fc700] WARN - NAT: UPnP, error mapping port 23873, error: Unknown Error, controlURL: http://192.168.1.253:49062/ctl/IPConn.
Jul 20, 2018 02:34:33.888 [0x7f5d693fc700] DEBUG - NAT: PMP, attempting mapping.
Jul 20, 2018 02:34:34.165 [0x7f5d62000700] DEBUG - NAT: UPnP, not an IGD: <http://192.168.1.253:49062/rootDesc.xml>.
Jul 20, 2018 02:34:34.165 [0x7f5d62000700] DEBUG - NAT: UPnP, getPublicIP didn't find usable IGD.
Jul 20, 2018 02:34:37.640 [0x7f5d693fc700] WARN - NAT: PMP, got an error: Network Error.
Jul 20, 2018 02:34:37.641 [0x7f5d693fc700] DEBUG - NAT: UPnP, attempting port mapping.
Jul 20, 2018 02:34:37.650 [0x7f5d693fc700] DEBUG - NAT: UPnP, usable device <http://192.168.1.253:49062/rootDesc.xml> with private address <192.168.1.250>.
Jul 20, 2018 02:34:37.918 [0x7f5d62000700] DEBUG - MyPlex: Last published value didn't change, we're done.
Jul 20, 2018 02:34:42.652 [0x7f5d693fc700] WARN - NAT: UPnP, error mapping port 23873, error: Unknown Error, controlURL: http://192.168.1.253:49062/ctl/IPConn.
Jul 20, 2018 02:34:42.652 [0x7f5d693fc700] DEBUG - PublicAddressManager: Mapping failed.
And the check an hour later - it succeeded using a different port
Jul 20, 2018 03:34:25.857 [0x7f5d68bfb700] DEBUG - NAT: UPnP, attempting port mapping.
Jul 20, 2018 03:34:33.888 [0x7f5d68bfb700] WARN - NAT: UPnP, error mapping port 14466, error: Unknown Error, controlURL: http://192.168.1.253:49062/ctl/IPConn.
Jul 20, 2018 03:34:33.888 [0x7f5d68bfb700] DEBUG - NAT: PMP, attempting mapping.
Jul 20, 2018 03:34:34.639 [0x7f5d68bfb700] DEBUG - NAT: UPnP, attempting port mapping.
Jul 20, 2018 03:34:35.076 [0x7f5d54bff700] DEBUG - MyPlex: Published Mapping State response was 201
Jul 20, 2018 03:34:38.709 [0x7f5d68bfb700] DEBUG - NAT: UPnP, mapped port 10668 to 192.168.1.250:32400.
Jul 20, 2018 03:34:38.709 [0x7f5d68bfb700] DEBUG - PublicAddressManager: Mapping succeeded for 192.168.1.250:10668.
It is more reliable to use a manually specified port and have a port forward in the router to your server local IP 192.168.1.250
You would need to make sure 192.168.1.250 is a DHCP reservation or outside dhcp range
Just to add a data point, my Plex installation has always had a manually specified port and a fixed IP address. I’ve only recently started having maintaining a connection.
What happens is that an out-of-house user gets a “limited connection” message. When I check the Server dashboard, it says that the server cannot connect. Generally, disconnecting and reconnecting does the trick.
FWIW, the problem appeared to start after the last ASUS firmware update. I’m wondering if the TrendMicro AIProtect is interpreting the connection tests as some sort of intrusion.
