I updated Plex Media Server on my Synology DS716+II this morning and remote access it not working except if I manually setup the public port.
This was not needed before and UPnP is enabled on my router.
Does anyone else have this issue?
What I’ve seen is that it can work for a few seconds and then the port moves back to 0.
Moi aussi je me déconnecte même avec la version 1.19.3.2764
je viens de repasser a la version 1.19.1.2645 je vous tiens au courant
Je suis en France
Non cela ne fonctionne toujours pas !!!
I have the same issue version 1.19.3.2764
Just downloaded the new Plex Media Server 1.19.2.2737 update and yes I get the green light and it has stayed on for over two hours. Lets hope it continues…
The New Plex media server is 1.19.3.2764
Hi Sa2000 - I am having also having this issue and based in NZ. Can I provide you with any info so we can find a solution? I was running the latest 1.19, now I’ve rolled back to PMS 1.16.6.1592 and the issue is still occurring. Remote access connects for up to 10 seconds, then turns red, and no remote access is available. I can play media on my local network fine. Let me know if I can help please, I need to find a solution. Thanks
I have passed details to our plex.tv team for servers in Australia, New Zealand and Singapore / Malaysia being affected.
As far as I can see it is only the test connections that go wrong and the availability indicator - so no real impact to Remote Access if you leave it alone and not disable / re-enable.
I suggest disabling the Tautulli every minute test
Thanks heaps for getting back to me. I have several accounts access my remote server, and none of them have been able to connect over the past 2 or so weeks, however today I tried deleting a single user, then re-sharing libraries and boom boom pow it worked (they had to accept request again).
Server is still RED saying unavailable, but this single user has a connection. All other users screens still say connection unavailable.
I will now delete and re-share them as well. Let me know if I can send any data through. Cheers
At the moment your server is only shared with 2 users
If you do encountered remote access dropping out then would need server debug and verbose logs covering time when server settings is on the screen and it is unavailable. Based on what is in the log - may then ask you for tracert output to the Plex back end systems
I also have been running Plex for a long time and just recently began having remote connection issues. I have one server on Windows and one on Synology. Both are having the same problem. Immediate disconnects in the GUI and they are randomly reachable externally. I am PMing logs from before and after 1.19.3.2793.
Thanks for the logs from the windows PMS.
Could you send me screenshots from the router please
I would like to see port forward screen for public port 32401 being forwarded to 10.20.100.50 on port 32400
and a port forward for 32402 forwarded to local port 32400 on 10.20.100.20
The logs do not any aborted connectivity test requests - the logs just show nothing coming in
What security software in use?
Does canyouseeme.org reach to your public IP 173.164.xxx.xxx and port 32401 - similarly for 32402
Canyouseeme gives inconsistent results, but I don’t know if they have always been inconsistent because I never had a call to check it before… I have sent a screen shot of config.
This has worked for a long time but I am open to suggestions about my environment if you see something, but I am skeptical it is something on my end.
Do I need open inbound traffic to this from outside the US? I don’t remember seeing this before, but I have a couple logs from AWS in Europe.
I’ve had the same issue for a year worked once upon a time but since then never managed to get it working, best case it goes green then red again. Running Plex Media Server on nvidia shield
Not sure if logs will benefit or if it’s a know cause that’s under investigation.
The only known issue is timeouts/aborts for some Plex Media Servers located in Australia / New Zealand / Malaysia / Singapore for requests coming in from Plex Amazon Cloud servers in Ireland.
Logs sent (edit sorry saw that i was not supposed to send logs) , at the moment default settings no manual port specified tried with that before and that didn’t work. Sweden, latest plex media server for nvidia shield , the shield is not rooted so running stock no strange things .
Not available outside your network
Your server is signed in to Plex, but is not reachable from outside your network.
Private 192.168.1.66 : 32400 Public XX.XX.XX.XX : 24643 Internet
Did a retry and it worked shortly and now it says not available outside your network.
I have portforwardng according to above (though public is ip is *)
DLNA is now off, Upnp i guess it’s Upnp that has created the rule
If you’re using a VPN… This may help.
Logs show that we are successfully mapping a public uPnP port to route to 192.168.1.66 on 32400 and every hour we refresh this mapping without getting an error and the mapping is appearing in your router uPnP IGD screenshot above
But …… something is blocking the requests reaching 192.168.1.66 on port 32400.
We can forget about what Plex Web says or does and simply test that the port forward is working by trying your public IP and port 24643 to see if we reach the server. At the moment we are not as I tried it
Is the public IP visible to plex and starting with 78.71.xx.xx the WAN IP address showing on your router internet status page ? Also is it the IP that http://canyouseeme.org detects?
http://78.71.xx.xx:24643/web from outside your network
Is their a firewall in your router ? Could it be blocking requests coming in?
You could as a test, setup a test server on a windows PC and then you can run wireshark on that computer and see if the requests from outside reach the PC - it would be a different port than 24643 but using similar mechanism
1 Like
Was a firewall hidden , seems to work for now, plex has set it to “Private Unknown IP Public Unknown IP Internet” though. If it stops working I will check through the rest of your reply,
ty very much
That does not seem right. So there are still probably some errors being returned
