Remote Access worked for 9 months before breaking

Plex Media Server Remote Access
1

Server Version#: 1.43.3.10828-00f62d37d
Player Version#: 1.112.0.359-0d79a49f

I bought the lifetime Plex-Pass last fall and have had no issues with it until roughly two weeks ago. I’ve tried everything listed on the Remote Access Troubleshooting page, and still nothing. I can confirm it’s not a Double NAT, CGNAT, or port forwarding issue. One thing that may or may not be an indicator of my problem is my inability to ping the crucial IPs listed on the troubleshooting page.

2

That would indeed indicate some deeper networking problem…

To what specific outcome did you perform those tests?

3

Verify that Windows on the plex server machine has your network connection still classified as “private”. If it’s set to “public”, the windows firewall will not allow direct access.

I have triggered a refresh of your server’s security certificate. Please stop and restart your server, then let it sit for several minutes before trying anything else.

4
  • I traced the route of pinging Google and confirmed I don’t have a Double NAT since my IPs didn’t repeat. (One of my potential fixes did create a Double NAT, but that solution has already been reverted)
  • My router’s public-facing IP doesn’t fit within the CGNAT IP range, so I ruled that out.
  • I also went ahead and port-forwarded the device running the server

Nothing else on that page was really too helpful, besides the list of un-pingable IPs. That’s all I really have to go on at this moment.

5

Verified my network is still private and restarted the server, still nothing.

I’ve also tried pinging those IPs through another device on the same network, but it failed as well. So I’m fairly certain this is a router/modem issue. Besides verifying the firewall isn’t blocking anything & turning UpNp off and on again, are there any other router-specific common fixes for this?

6

Those are Amazon addresses. They block pings and traceroutes to such hosts.

8

If the items below were not working, then you would probably see other problems besides no remote access. However, never hurts to double check.

Verify connectivity to plex.tv. The address for v4.plex.tv may differ depending on your location.

c:\>nslookup v4.plex.tv
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
Name:    k8s-ingressn-plextvin-d337945c85-d6d8bc4ebb772eca.elb.us-east-1.amazonaws.com
Addresses:  34.238.225.186
          35.172.142.61
          44.210.41.33
Aliases:  v4.plex.tv
          plex-tv-migration.plex.bz


c:\>curl http://v4.plex.tv
<html>
<head><title>308 Permanent Redirect</title></head>
<body>
<center><h1>308 Permanent Redirect</h1></center>
<hr><center>nginx</center>
</body>
</html>

Verify Plex Media Server is correctly obtaining a public IP address from v4.plex.tv.

The address should match what you see from whatismyipaddress.com, canyouseeme.org, or similar sites.

From Plex Media Server.log. Repeats every hour.

Aug 03, 2026 15:48:27.473 [129255867460408] DEBUG - PublicAddressManager: Obtaining public address and mapping port.
Aug 03, 2026 15:48:27.473 [129255867460408] DEBUG - PublicAddressManager: Obtaining public IP.
Aug 03, 2026 15:48:27.473 [129255867460408] DEBUG - [HCl#1ae] HTTP requesting GET https://v4.plex.tv/pms/:/ip
Aug 03, 2026 15:48:27.620 [129256006839096] DEBUG - [HttpClient/HCl#1ae] HTTP/1.1 (0.1s) 200 response from GET https://v4.plex.tv/pms/:/ip
Aug 03, 2026 15:48:27.620 [129255867460408] DEBUG - PublicAddressManager: Got public IP from v4.plex.tv: <redacted>
9

Right before I ran those commands, I checked the server and saw it was working again. So I’m not sure what exactly fixed it, but I’ll be keeping a close eye on it. Still, thanks for providing more checks, and hopefully your post can help someone in the future.