Also getting wrong public IP of 172.17.0.1 on one of my two servers , both of which were updated to 1.13.8.5395 this evening.
Up until this time I had no issues.
Both servers are set up in port forwarding with no changes in several months.
First server is using external port of 32400 (this is the one getting wrong public IP all of a sudden) the other server (working correctly) uses 32401 as the external port).
Just for giggles, I am going to change the port forwarding config on the server getting the wrong public IP to 32402, just to be using something other 32400, which is of course the internal port for the server.
And BTW - I am logged in with my account on both servers.
Changed the router port forwarding as above, and the manually specified public port on the remote access page. restarted plex on both servers. Now the one that had the right public IP got a 172.17.01.1 address and the one that previously had the wrong public IP got the correct one. restarted both again, both got right public IP, BUT even though servers say remote access is enabled, remote access is not working. Also, cannot see server 2 from serve 1, but can see server 1 from server 2.
I think its Plex end is doing all this ■■■■ and not our end. They’ve been quiet about it. No developer responding to our question why it’s not working…theyre blaming our router not configure properly which I think it’s all bs since everyone’s network configuration has been working for ages and Plex suddenly come crashing for the past days without we even touching any configuration to our setting in our router. And it’s not even isolated issue…it’s happening to everyone who’s using the remote feature.
Now server #1 is back to the wrong Public IP, seems to switch without me doing anything…
Remote access to both servers does not work, and cannot access server 2 from server 1 even if both (momentarily it seems) have right public IP.
Oddly the PLEX client on my fire tv and Plex client on android mobile (while on WIFI, not Data network) can still see both servers. All my devices (servers and clients) are on same private network.
Remote access has always been one of the best selling points of PLEX. You broke it, now fix it.
Glad to see that I am not the only one having this issue. I thought that it might have something to do with my VPN, so I uninstalled it. Still no remote access on my cell phone. Public IP, local IP, and port forwarding all working as intended. I checked on http://canyouseeme.org/ to make sure that my port was indeed open, and it is. Streaming and library access available over LAN WiFi, but over Verizon’s network nothing. The strange thing is that my setup would always show not available for a fraction of a second before the latest update, then it would flip over to fully accessible. Since the update, it just stays red until I hit either the “Apply” button or the “Disable Remote Access” button and then enable the service again. Attached is a screenshot confirming that Plex thinks that remote access is enabled.
I have the same issues. I’ve been up for 3 hours trying to resolve this until I came here and see that it’s system wide. I’m on the latest version as well. I have 2 servers on completely different networks and the same issue on both with that 172.17.0.1 Public IP address.
I can confirm the issue here as well. Latest version on Linux, gives me an internal IP 172.x.x.x and is unreachable from any device on any network from Plex apps.
Same here, too. so Sad! I did not update to the current version. Luckily i can use vpn accessing my nas. It consumes much more battery but better than nothing.
In this thread a plex employee seemed to answer:
I think, they are not aware of the problem level.
I found another thread for this:
btw: notification for 1.13.8 update is gone. Looks like they removed the update. So i can not update to this version which is suggested as a fix.
Realised that the same thing is happening as above, when using a remote plex client to search for my server, the polling to plex returns my remote server address as my internal network address 192.168.x.x. No chance of connecting to this address over the internet! lol
It looks like the problem is a bug in the Plex Media Server at this point, but Plex support have been spending the last 24 hours telling people its their own network/firewall configs that are to blame. Im hoping now that this tidal wave of Plex Pass users having the same issue will make them look a little closer at the problem.
Same thing here. Just like everyone else I was going nuts trying to track down the problem before finally checking here. Running 1.13.8.5395 and intermittently seeing the 172.17.0.1 public IP address. Direct access works fine.
Pinging @SamFromPlex as he was helpful the last time I reported an issue and I haven’t seen any official response yet.
Yep - I have had problems since the previous version (5223) with clients on the local network deciding that they can’t get direct access and having to relay, even though the server is fully accessible internally.
Then with the 5395 update it got worse, I have clients failing to connect, whilst the same version clients on the same network at the same time connecting just fine.
And I don’t have DNS rebinding, I can get to apps.plex.tv just fine from the clients, and my local network has RFC1918 address space. For external access (bearing in mind, its local thats broken for me) I don’t UpnP, I port forward (and the server says 'fully accessible outside of the network).
not sure if its temporary but give it another try if you were having the problem.
