this is it. oh my lord this is it. i dont mean to jinx it, but it is working for me.
If you have issues still = please post logs from the server and indication of what went wrong and when. If you have any wireshark captures that go with the logs - please zip and send to me by private message
I searched āupnpā on the forums and this is one of the top, most recent posts. Iām experiencing a similar or this same issue. Plexās upnp will forward the port on my Netgear R8000P and use it briefly after itās been toggled on, but then it will stop using the port that has been forwarded.
I can cause it to work again briefly by toggling it off and then on is server settings. It requests a different high port be forwarded and then will stop utilizing that port. Manually forwarding works fine, but Iād rather upnp work since I use it for my xbox anyway.
I am using the debian source and would be happy to provide logs if it would be helpful. It seems like this is a known issue. ? Bet me know how I can help with data if this issue is still under investigation. Thanks.
How do you determine itās not working? Is this based on Plexā remote access status indicator or your media not being accessible from outside your home network?
If thereās an issue with the automatic UPnP and your setup (router/server)ā¦ have you tried establishing a manual port forward instead?
@sa2000 thanks for sharing some insights into disconnect issues. Near identical issue as with @heapson above - except I am in US East Coast. Hopefully the timeout adjustments will be made for US servers as well. My current settings are
-
UPnP off (UPnP banned on my LAN)
-
Public Domain Name with A record pointing to my internally hosted static IP
-
Custom External Port (1xxx) routed to Internal Port 32400
Latency is minimal (under 75ms) and no firewalls / NAT issues. Definately a sporadic connect / disconnect. As with above, it will stay connected form a few seconds to a few minutes - random.
Hope this is resolved at some point - significant loss of utility in its current state.
Same problems here. It connect/disconnects after trying lots of things. Hope they can fix this properly and ASAP.
Regards.
Nvidia Shield PMS user here checking in with the same issue. Iāve walked through many of the steps in this thread to try to nail down the issue, but Iām running into a brick wall at this point. Iāve PMād my logs to you @sa2000, and any help is appreciated!
Any solution for this? still happening!
1 Like
Same exact issue just started happening a few days ago for me as well. The only change I had made IF ANY was an update to the Plex Media Server software that ran automatically overnight. I noticed that just yesterday morning there was a newer version 1.20.2.3370 so I installed that, then re-installed it (chose the āRepairā option) and no fix. Most the devices in my home on my network no longer communicate with my Plex server and they are on the same local network. This really sucks and I hope a fix is pushed soon.
2 Likes
Just wanted to chime in and say I started having this issue a week ago. Hope it can be resolved.
2 Likes
Please, help. I have exactly same problem. from browser my friends can use the remote, but in the tv not. I use the remote while a year, but now its dead. i check the port, its open, i try another router, i reinstall plex, nothing. here is the log: Plex Media Server Logs_2020-10-05_16-50-03.zip (6.1 MB)
A quick FYI:
I noticed that Plex remote access wanāt working today. No idea how long it could have been like that, anything from today to a week or two ago. After changing or refreshing the port in the web interface it worked for a few seconds and then suddenly stopped.
I tried everything and doublechecked everything. Nothing was changed as far as I could see and yet it didnāt work. I reentered the ports in my router, restarted the router, the plex jail (I use freenas) and even the whole Freenas server, made sure I wasnāt behind a double nat etc etc. Everything looked fine and yet it didnāt work.
Solution:
It started to work after updating plex to the latest version (1.20.2.3402) which is a bit odd since the changelog doesnāt mention anything about a fix for this. And I also know for sure that remote access did work earlier with my previous plex version (1.20.2.3252), which makes it even more strange.
I donāt know if it was the update it self that fixed it but whatever it was Iām not complaining. 
Edit: I also noticed today that I couldnāt access the web interface through https. I rarely visit the web interface so I canāt know for sure when that stopped working but I think it worked a week or two ago. Donāt know if that has any correlation or if itās just a coincidence. The update did not fix the issue with https though.
Not sure what you are referring here : āthe remoteā
from browser my friends can use āthe remoteā, but in the tv not. I use āthe remoteā while a year, but now its dead.
Can you please try again using latest beta which was released today and get me fresh logs if the problem persists plus screenshots and details of exactly what is not working
Latest beta is 1.20.3.3430-48c594b30
Thanks
One thing Iāve noticed with Plex and my NetGear x6 R8000 router is that whenever I run Plex in the browser and connect remotely, it somehow needs to also have the router admin dashboard logged in on a separate tab. The R8000 has a login timeout and when that occurs, Plex loses its remote connection. If I then re-login to the R8000 admin dashboard and attempt the āRetryā on the connection in Plex, it reconnects. But only if the R8000 dashboard is logged in and hasnāt timed out.
If I add a Chrome extension that reloads the Netgear tab, it seems to help a bit to keep the connection open longer. I just havenāt tested it for a long enough time to know if thatās a sufficient workaround. I ought to be able to just leave the Plex tab open and not have to deal with the Netgear tab.
Itās super annoying. I have to run upstairs and refresh everything on the Mac to reconnect the Plex app on my phone and see whatās in my library.
1 Like
The same started to happen to me about 2 weeks ago with the latest PMS version on a QNAP NAS. As a Plex Pass subscriber, I would like to get something for my money when the ā ā ā ā hits the fan! I expect a Plex engineer to look into the issue ASAP.
1 Like
Looks like for some reason the ports from 15000 and above donāt reach my router. Maybe my provider blocks them. I changed the external port to 500 and forwarded it on my router and all seems to be working fine now. My provider is Movistar in Spain.
Thanks for re-sending the logs after the aborted upload.
The logs show failure to get to the server to WAN Port 32400 - please check that the router has a port forward for public tcp port 32400 to forward to local IP 192.168.1.26 on local port 32400
No problem! I had my port forwarding set up correctly, but I didnāt have it set up as TCP. Making that change fixed everything. Thanks for the help!
@sa2000 I am having the same issues as above - I turned off UPnP, and set a manual port forward to 192.168.0.10:32400 (hopefully this was done correctly)
Windows 10 defender seems to be allowing it through
Remote access flashes green for 2 seconds and then goes red. I have a new modem and wireless router, both have UPnP turned off, the modem is the one with the port forwarding, and I think they are bridged.
I am assuming I am missing something I have PMed you the logs and screenshot(s)
FYI I see this error in the logs:
NAT: PMP, got an error: NATPMP_ERR_RECVFROM.
