Server Version#:1.42.2.10156
Recently I have been experiencing an issue with my plex server where remote access will report successfully connecting, but after a few seconds, it will update the status to “Not available outside your network”. I have UPnP disabled on my router, I have a manual port forwarding rule set up in the router to forward external port 32400 to my lan IP at port 32400. I’ve ensured that Plex Media Server is allowed in my firewall, and I have the port manually configured in my plex server as well.
I’ve been at this for a while now, and it only started acting up when I set up a Pi Hole on my network, or at least that’s when I started noticing it. Since then I’ve completely shut down the Pi Hole, and have made sure to use my router as the DHCP server, with my plex IP reserved. My WAN IP on my router is the same as the IP that appears on whatsmyip.com, so I don’t think its a CGNAT issue, and I even tried completely resetting windows and reinstalling the plex server. Any help would be appreciated, I fell I’m out of my depth a bit here.
The status briefly showing as green before switching to red just means it’s not working at all. This is due to Plex‘s „optimistic approach“ to show the status as green while it’s testing the connection (this will usually take a few seconds; there’s situations where it can take up to 2-3 minutes).
Have you confirmed your port forward is still accessible from outside your home network? If it’s not, you could try switching to a different port. It might be worth to test some random ports ranging from 20000 to 50000, or a standard port like 80 or 8080 — this way you could test if your ISP might be blocking that particular port.
Well, I switched the port forwarding rule from 32400 > 32400, over to 28124 > 32400, and it works like a charm. That’s what the port was before I consulted chatgpt on how to fix it, and it recommended I switch the external port to 32400. I guess that’s a lesson learned about AI. In any case remote access seems to be doing just find now.
Well I guess I spoke too soon, because this morning it was broken again. Still exposing port 28124, and I disabled SIP ALG on my router last night, as well as disabling port triggering. I’m stumped.
I am having this exact same issue. It says it is working, then a few seconds later it isn’t. I had my ISP put in the forward a few months ago and it did the same thing so I figured it was an ISP issue. I had them put their device in bridge mode and installed my own router so I could see everything and have more control, and it is doing the same thing. My router is an ASUS RT-BE58U. I have Upnp turned off and a port forward put in manually.
Check your router’s firewall settings. My solution turned out to be the router I was using was blocking the port in its firewall, and didn’t allow me any ability to control the firewall settings. Switching to a router that allowed that control made it work right. It’s been working right for a couple weeks now, so I’m confident that this was the issue.
I am also having the same issue. I was in the middle of a remote stream and it cut out and now I mysteriously have no remote access. Been remote streaming for years never had this problem
Hi guys, I have a similar issue. Whereby remote access is not working but my issue can’t seem to be fixed. My private ip address sub net is 192.168.x.x however when i log in to remote access, the ip is showing as 172.16.x.x. I do believe there is not CGNAT or Double NAT as just a few days ago remote access was working. Also to confirm, there is no VPN activated at the time of installing and setting up plex media server on my TrueNAS. I believe a relay connection is being used instead.
Does this mean I can log in anywhere and still view my media even if I’m away from home and not connected on my network by any means?
You’re saying that your home network’s IP subnet is 192.168.x.x but Plex identifies your private address to be 172.16.x.x?
If this is about the private IP, it indicates there’s a misconfiguration within your home network. Could be you accidentally created a new subnet using a separate IP band — this could happen by adding a new active network component with its own DHCP server, e.g. a WLAN Access Point.
In that case, you might be able to fix this by either connecting the PMS to your regular/main network or configuring the new component in bridge mode (so it won’t create its own subnet but extends the existing network).
To be honest I didn’t really do anything. I had an issue where I had to reinstall Truenas. The only hardware change I made was added a gigabit pci card to the old computer. The gigabit card has a static ip of 192.168.0.119 and checking my router settings nothing has changed except for my port forward of 32400 as TCP rule.
Your plex server is running in bridge mode on your TrueNAS. During the Plex setup process on TrueNAS, there’s a checkbox to run it in host. Check that box and restart the plex server.
Oh perfect thank you. Most tutorials I seen was showing as not to tick the box. I guess because the web Ui button also disappears in Truenas so thought it was wrong. But thank you.
edit
Spoke too soon. Now that Plex is showing the correct IP, I’m have the issue where after a few seconds the Remote Access stops running after a few moments. Double checked network settings and all seem fine.
You need to double check your port forwarding on your router. Check if the port you entered on the Remote Access page and that you forwarded on your router is open: https://canyouseeme.org
Every 2 days in the morning the remote access stops working. And I have to reboot my Router Modem to temporarily fix it. But my router modem is set to exposed host. No Firewall, no NAT, nothing. ALL traffic is forwarded to my actual home network router. And my public IP is fixed. So it makes no sense to me.
External access worked for the last 2 years without issues and this just started. There was no update on any device in the few weeks before it started.
For me it seems that my ports are not being exposed right now so probably will have to get in touch with Sky as Map-T share ratio is showing 1:1 as per other research
In any case remote access seems to be doing just find now.