Sorry, yeah it’s a static WAN IP on a remote dedicated server with port 32400 forwarded in the Windows firewall. No UPnP in use, and no router firewall (DMZ). I did not disable remote access at all. All I did last night was update from the previous 1.13 release to the latest 1.14. Hope that helps, and thanks for looking into this. If I could get the link to 1.15, I would be very happy to see if that works. Been down for almost a day now 
Ok i will send you a link for windows binary to try
Could you export the registry settings for PMS to text file and send me by private message
HKEY_CURRENT_USER\Software\Plex, Inc.\Plex Media Server
and send me unedited log file by PM
having the same issues. May I try the Dev build please?
I am sorry i need to see the issue first rather than just give out a dev build
So please logs of the problem and what the problem is. Is your server with just a WAN IP and no local IP? If that is so, i would need to see the settings as well (sent by private message)
I just downgraded to 1.13 and it’s working again. I’ll pass on being a guinea pig from now on. No more beta builds for me until you guys do a better job of QA.
3 Likes
The logs did show a glitch whilst setting the manual port - which is the timing issue i mentioned
I just went through sequence of switching to uPnP automatic port mapping and it worked ok. So will need to get some diagnostics if it is not working for you and ideally should try and see if you can use wireshark to capture the network traffic and send me that (zipped) by private message to go with the logs
Wireshark is available here Wireshark for Windows - Download it from Uptodown for free
- Ensure uPnP is enabled in the router
- Check the router uPnP forwarded Ports list to see how many there are - some routers have a limit on that
- Restart the server to get fresh logs created
- wait 5 minutes
- Start wireshark capture of all packets on the network interface
- On Plex Media Server Remote Access settings with show advanced ticked, untick
manually specify portand then clickretry - When you see remote access disabled, wait a few seconds and then Enable Remote Access
- wait 30 seconds after the action completes and see if it has successfully mapped a port to 192.168.1.129
- if not, do an F5 browser refresh and see what happens
If it is not successful, stop the wireshark capture and save all to the default pcap file type
collect the server logs
send me the zipped pcap file by private message and i will have a look together with the logs
If there is an issue with 1.14.0 then without the evidence,the issue will not get investigated until someone hits it and provides diagnostics.
I am running on 1.14.0 and i do not have an issue. So issues that users encounter are not necessarily seen by everyone and specific investigations are needed. The development build fix is for a bug that was introduced before 1.13.8.
I see that you have downgraded to 1.13.8.5385 - i am not aware of any new issues in this area between that and 1.14.0.5465
1 Like
1.15 did not solve the issue, unfortunately.
Here as well no remote connection working after updating to 1.14. Downgrading to latest public version restores the remote connection.
Running Ubuntu 16.04.
1 Like
I am also back in business after reverting back to 1.13.9.5456.
2 Likes
Also went back to 1.1.395456 and all is working again!!!
1 Like
Yep the UPNP is broken in 1.14. No problem I can rollback freenas plex easy enough but I don’t know how to rollbaack a Nvidia Shield.
Same here on Windows. Currently switched to manual assigning the port and using port forwarding on the router.
My home network is simple - it’s all on the same “LAN” or subnet as the router.
I did not break it out into different networks or subnets.
No, LOL - my Tablo has the exact same IP address it has had since I installed it.
First thing I do with “important devices” or devices I need to always find in the same place is set up an IP reservation in cases where I can’t assign a static IP.
The only way my Tablo address could change would be if the Tablo was replaced and thus had a different MAC address, or I changed my router in which case the IP reservation table would be gone and I’d have to rebuild it in the new router.
First thing I did when my Tablo arrived was grab the MAC address and put it into my router and assign an IP address so when Tablo came online I’d know exactly from the very first second what its address would be.
(For onlookers - Tablo has no place for a STATIC IP. You can NOT assign static IP to Tablo since Tablo has no place internally to do so.
You must assign a reserved IP address in your DHCP server, or if the router assigns addresses and acts as your DHCP server, in your router.
Static is where you assign it in the device itself,
reserved is for devices like Tablo where it can ONLY do DHCP - you set your DHCP server up so that the device with MAC address whatever always pulls the same IP address.
The result is the same - but if you know DHCP, you can see the differences in the DNS server. People always use the word static interchangeably with reserved but they are in fact NOT the same. Static is assigned inside the device - you turn off DHCP client and type in the address the device is to use as soon as it starts up, they make no DHCP request if assigned a static address. Reserved is configured within the DHCP server. This way the device also pulls the DNS, WINS and other special DHCP information. With static you must set that in the device itself - you can’t with tablo. )
My Tablo has been 192.168.0.100 since day one and there’s a reservation for it in the DHCP server which is currently my router acting as DHCP server.
My notebook, Tablo, Chromecast, and one other device always get the same IP address. That has never changed.
I do happen to know the ins and outs of IP addressing and am in fact responsible for DNS, DHCP, VPN and several other functions at work as a network administrator and network security administrator. I manage over 40 routers at work, a Juniper chassis/core switches/routers, Cisco ASAs, 100 VPN clients and an NCP secure VPN gateway with fail-over.
So in that regard we can skip to chapter 2, and go to networks 110 instead of 101 
However, these little home devices are, well, lacking in real control. They simplify them to the point they are complex and there’s no real logging to be of much use.
I’d find it 100 times easier if this were some Cisco ASA or a Juniper enterprise class router! Those are SIMPLE!
This netgear is admittedly difficult and the terminology is not enterprise, it’s changed for the homeowner making me feel like a pure novice.
I admit I could build a complex WAN from step 1 using enterprise-class equipment but am lost as a kid in a department store in this Netgear thing.
I’ve tried for a year to make the remote access work. I used every hint or tip that Tablo support had as well as some of the best Tablo users such as snowcat, theuser86 and other long-time Tablo users who have cut their teeth on these devices.
I’ve even set my home router NAT to unsecured to see if I could force it to work, no joy.
I have almost zero choice on Internet devices due to the fact that our area, like a lot of the states, has no broadband service. We have to use cell data services.
There’s no cable, no DSL, etc
People get comfy in their 100 gig broadband (yeah, an exaggeration, but making a point) their ability to stream a dozen movies a night with no limits and no stuttering and assume the rest of the country also has such access which couldn’t be farther from the truth. We have a cap and speed isn’t stellar but is actually pretty good most of the time since the router firmware update and US Cellular did some more tower work making 4G better here.
So, I have a single device- modem/router, all in one.
It’s a Netgear LG2200D
It has 300 Mb Wi-Fi abilities (Wireless N up to 300 Mbps), routing, 4 built-in 10/100 Ethernet ports, handles up to 30 Wi-Fi devices, 2x2 MIMO,
Firewall support includes Stateful packet inspection (SPI), intrusion logging and reporting, denial service (DoS) and DDoS protection
NAT traversal (VPN pass-through) for IPSec, PPTP and L2TP VPNs
Mode of operation: Port and Network Address Translation (PAT/NAT), static routing
IP Address Assignment: Static IP address assignment,
internal DHCP server on LAN (where I set the IP reservation for my Tablo so it ALWAYS has the exact same IP address on my LAN)
DHCP client on WAN,
Domain Filtering & Parental Control,
Port range forwarding,
Exposed host (DMZ), DNS proxy, URL content filtering
DOS protect & DDOS detect
Static and dynamic routing with TCP/IP, SIP & VPN pass-through (IPSec, L2TP, PPTP)
RIP V1 & V2
DMZ
DNS
DNS Proxy
Dynamic DNS
DHCP (client, relay & server)
RFC 1483 static IP
Classic IP
Port forwarding and Wireless Distribution System (WDS)
QoS
TFTP Client
I also had to rollback to 1.13.9.5456, UPnP and port forwarding does not work in 1.14.0.5465.
2 Likes
Same issue here with Version 1.14.0.5465. Remote access is really intermittent, it seems to work for a few hours then stop. It’s breaking integration with Sonos and Alexa too since they both check for remote access. It was rock solid previously.
Logs attached.
1 Like
I had the same issue…went into router settings, toggled UPnP off and on 2 or 3 times, restarted PMS and now it works again. (On MacOS Mojave 10.14.1, PMS 1.14)
Standard stuff to disable UPnP, tried that a few times and tried manually setting port. Just not working.
Thanks for the logs
could you have a look into the router uPnP port forwarding view and see what port forwards are set in the router. There is a possibility that may be Plex Media Server attempted to do the port mapping to different ports too many times and reached a router limit
could you get screenshots of all the uPnP mapped ports
Thanks
I went ahead and rolled back to version 1.13.9.5456 and everything works fine.
UPnP now works.
