Issues with Remote Access / Incorrect Public IP Address

Plex Media Server Desktops & Laptops
1

Hi guys,

I’ve looked in the forum and tried to find an answer but I couldn’t really.

Since earlier today my Remote Access is not working anymore. I noticed that the PUBLIC IP within Plex is different to the one on whatismyipaddress.com and on my router. The router and whatismyipaddress.com both show the same (as does IPCONFIG within the CMD).

I’ve checked if port 32400 is open using whatsmyip.org/port-scanner/ and it’s definitely open.

Any idea what I could be doing wrong?

Many thanks in advance for your help.

Regards,

Server Version#: 1.18.2.2058
Player Version#: N/A
Plex Media Server Logs_2019-12-06_17-40-01.zip (3.9 MB)

2 Likes
2

Having the same problem here. It’s been driving me crazy for the past hour.

I downloaded your logs and my server is giving me the same public IP as you - 64.188.30.130

I run two servers on my network so I forward port 32400 & 32401 - both servers report the same incorrect public IP - 64.188.30.130. One server is running on a Synology, the other a Windows desktop.

Hopefully this can be fixed because I’m guessing we’re not the only ones affected!PlexWrongPublicIP

Server version#: 1.18.3.2129

3

Are you guys perhaps using the same ISP?

From the log:

Dec 06, 2019 17:29:08.921 [4088] ERROR - MyPlex: mapping failed due to potential double NAT configuration
4

I’m in Melbourne, Australia using Aussie Broadband as my ISP. Definitely not behind a double NAT. Aussie do employ CGNAT for their customers but I’ve opted out and have been using Plex remote access daily for over a year and I’ve had the same public IP for months…

My actual public IP is 202.142.XXX.XXX but Plex thinks it is 64.188.30.130 (same as sneakybastard from his logs). At first I thought someone had compromised my account but I’ve reset my password and it’s still happening…

5

Never mind, I’ve got mine working again. The problem was caused by my DNS provider - Getflix SmartDNS.

Doing an nslookup on plex.tv returned 64.188.30.172 when using Getflix’s Sydney and Melbourne DNS servers. Changing my DNS server to 1.1.1.1 gave the correct result for plex.tv - 99.80.231.223 / 99.80.242.242 / 99.81.213.165

Changing my DNS server to 1.1.1.1 and restarting remote access on Plex fixed the problem. :slight_smile:

2 Likes
6

Ah sh*t … grantfisher, you’re the man! I’m sure that will be my issue as well (because I also have a GETFLIX account). I will check this right now.

But the weird thing is that I’ve had my GETFLIX account for ages now and never ever have I had any problems with my Remote Access.

(And btw, I’m based in Amsterdam, NL so definitely not the same Aussie ISP as grantfisher)

7

No worries. I’m thinking maybe Getflix are trying to make region switching available for Plex’s new Movies and TV service so that their customers aren’t geoblocked for some titles.

9 hours later and the Getflix DNS is now resolving plex.tv properly so I’d say you should be able to restart your remote access now and have it working again…

8

It didn’t for me (as of now), just added an override to my unbound dns (opnsense) exceptions :slight_smile:

1 Like
9

Yeah mine went back to not working again last night so I’ve hardcoded the correct IP for plex.tv in my /etc/hosts file :slight_smile:

1 Like
10

I was having the same problem (I’m in NZ). Only started happening in the last couple of days. I thought it may have been down to the new version of Plex Server (1.18.3.2129) on my Synology.

I removed the Getflix DNS settings on the router and back to using the ISP one and all worked again.

So, following on from @grantfisher solution (thanks!), I changed the DNS server settings on my Synology Control Panel/Network to 1.1.1.1 & 1.0.0.1, and re-enabled the Getflix DNS on my router. Seems to work so far!

Thanks for the heads up.

11

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.