My media server remote access keeps failing. It will be on and active for a few minutes then turn off saying “Not available outside of your network” If I disable remote access and then reenable it, it will be available to outside network for a few minutes and then fail again.
What I have tried so far to resolve issue–
Disable all Firewall and anti-virus software.
assign server a static IP.
Port Forwarding to 32400.
enabled UPNP on router.
My home bandwidth is 200 mbps down and 20 mbps up.
This just started happening after the last server update. I have had this media server up and running for over 2 years without any issues.
Any feedback on this issue would be great. Is anyone else having this problem?
I’m a newbie, setting up a new server (V1.26.0.5715 - the latest) running on an M1 Mac (macOS 12.2.1) with Frontier gigabit up/down service. The router is an eero Pro 6 with the latest software.
I got it working last Wednesday. Yesterday, it failed in the same way as described above and has been able to connect only for a few minutes after retrying…
I have the following network settings:
LAN is DHCP with a reserved address for the computer.
Port 32400 is forwarded from the reserved address. Tried Port 40000, which connected, then failed almost immediately.
WAN is DHCP. IP address has not changed.
TCP and UDP are on.
IPv6 is on, but no address has been assigned to the computer. Turning it off doesn’t change the behavior.
No firewall.
I have the same issue. I have done the same and more as original poster:
Disable all Firewall and anti-virus software.
assign server a static IP.
Port Forwarding to 32400.
enabled UPNP on router.
Disabled (has been disabled) Xfinity Security
Rolled back to 3 previous versions of plex.
I have had some positive and mostly negative results. Either the external access will just gets disabled on it’s own or if I do have access, it always plays “indirect”. I have seen this issue in past once a year or twice sometimes and it goes away on it’s own. I don’t make any changes to my home network but the issue creeps up every now n then with new updates. This time, it’s not going away on it’s own. Is there any actual plex support or do we all just rely on each other to figure out what could be the cause? I have lifetime plex membership pass as well.
First thing to check is there anything else on the network that could be using that port? As in a weird piece of software or some equipment? (My friend was using is torrent program on the same port which caused the remote access to fail of course)
Resolving Networking issues is hard as everyones is different, but from what you have posted it sounds like everything is correct.
I would enable the Firewall however, as this can turn off rules that Plex requires to port forward and route the application out to the big bad world, I’d also turn on UPNP to see if you can get it talking just by old fashioned port forwarding.
Same here, I’ve been running PMS 1.21.1.3830 in a FreeNAS jail for several years and a few months ago my remote users started having this same issue. I setup a new server on Ubuntu running PMS 1.25.9.5673 assuming it was an issue with the other server and it’s having the exact same issue. It doesn’t happen to them at the same time. Sometimes both are online or just one or sometime neither. Very frustrating and not sure how to get help to fix it.
I’ve found that if I go into the settings, remote access it will show green but after a few moments it will turn red. If I click the retry button next to “Manually specify public port” it will turn green again and my users can access the server.
Hello, good, I have a problem, I am not able to connect remote plex, it only lasts a few minutes and it cuts off, I am out of cgnat, I do not know what the problem is, I opened the ports and it still does not connect…
Hello - I had issues as well due to a specific configuration in my DD-wrt router firmware that did not allow NAT/port forwarding besides standard 443,22,23 TCP ports. As a work-around, I enabled/am using the Settings–>Network → Enable Relay and then access my Plex Media Server via https://app.plex.tv. Keep in mind - this is not recommended for watching livestreams (video/tv/movies) but does the job for streaming music when not on LAN. Relay bandwidth/service is a proxy-based so bandwidth is obviously limited by what Plex offers to users.
Long term fix - get a dedicated/capable home router (Firewalla box etc.) that is powerful enough to handle 1 Gbps up/down vs. 400 Mbps max that my router (Netgear R7000 is not capable of wuthout software shortcuts (CTF/SFE)). NOTE: For reference, the issue with my custom firmware (dd-wrt) R7000) is using Cut-Through-Forwarding which enables full duplex 1Gbps WAN/LAN but breaks non-standard NAT/Port forwarding. If I disable CTF/SFE, NAT and Remote Access to my PMS works. Hope this helps!
PMS 1.26.0.5715
Synology DS920+ on DSM 6.2.4-25556 Update 5,
I tried the following mentioned in the first message
Plus
Manually Port forwarding to 32400, and letting PMS choose which port automatically
Mapping the port in the router
Enabling/Disabling NAT on router
Activating/Deactivating ipv4
Placing NAS inside a DMZ on router
Nothing changes the core problem that is when enabling remote control it says “successful”, but then alternate with “Not available outside of your network”
Ubiquiti Amplifi router connected directly to Optical Network Terminal (ONT) for fibre internet, 300 mbit down 60 up.
Amplifi is gateway/DHCP server for home network
Amplifi in Mesh Wifi config with two APs
UPnP enabled.
Static IP on server, Plex Server listening on 32400
TCP traffic on 32400 forwarded to server’s static IP
PlexServer running on Windows Server 2019 running one other app that uses another port. Have turned other app off to test just in case, no effect.
no virtual adapters of any other sort, such as VPN or Hyper-V.
IPv4 and IPv6 both enabled all the way through
Firewall disabled on server
Amplifi has no NAT or similar capability other than manual port forwarding that I can see
Only way remote works is with the relay enabled which seems to limit me to 328p, not really watchable unless you like seeing the world through smeared glasses.
Any suggestions from anyone for the above config? Can’t disable DHCP server on the router for some reason. Can only change the scope…
Hey! I am running 4.81.1 and 1.26.1.5798 and had the same issue. Everything was working fine and then I updated to the latest version (see above) then suddenly I couldn’t reach the server. For some reason during the update my IP’s got all screwey. What I mean is the static IP on the machine for some reason wasn’t matching the plex. Plex was saying it was connected to the internet even though that IP didn’t have an exception and even though I blocked it on the router. The static IP of the machine was correct but for some odd reason plex was saying it had another. After restarting plex it showed the correct IP but still couldn’t be reached. Another restart and it went back to the other wrong IP (the machine still had the correct static). I fixed it by unistalling and reinstalling plex then everything was working fine again. I don’t know if that helps but that is what worked for me.
Joining the discussion with the exact same problem. I tried EVERYTHING. This all the sudden started happening 2-3 weeks ago out of the blue without any change. Before that my PLEX server was running straight without problems for 3 years. I also took all the same steps that the others outline. But after 1 minute or so it still turns red and is not available outside my network anymore. I also rolled back to the last 3 server versions. Given how many people seem to be experiencing the same problem it would be great for PLEX Developers to acknowledge and maybe look into this?
Something that I encountered on my end (and was fixed only by the ISP):
If you make a traceroute to google, and one of your hops is in the 100.xx.xx.xx IP range (on IPV4 connectivity), you are a victim of CG_NAT deployment by your ISP, and all your efforts for remote access are futile until your ISP gives you a real public IP.
Another way is to look at your Router’s administration page, and find the Internet or WAN address. If that’s 100.x.x.x, or if it’s different from your reported IP at https://www.canyouseeme.org/, something like CGNAT is active.
Much like everyone else, I have the exact same problem. Ran perfectly fine for years until 2-3 weeks ago and now remote access fails. I’ve done all the noted troubleshooting steps but nothing works. Seems to have coincided with an update that came down from Plex (could be mistaken but it’s awfully coincidental). Will Plex ever acknowledge there’s a problem here?
FIXED - I did manage to FIX this on my server. Turns out, xFinity did some type of update to my X1 router and the firewall on there was blocking it. I changed the firewall settings on my X1 router and Plex began working again. Still tweaking it a bit to ensure I have a decent level of security but this seems to be the root cause.
Assuming, of course, that Plex did not change the way my server registers to plex.tv. Such a change could have caused a pre-existing rule on my X1 router to take effect.
