Plex unable to get public ip address from plex.tv

Plex Media Server Remote Access
1

Server Version#: 1.28.2.6106-44a5bbd28
Player Version#:

After restart my plex server, I am unable to connect to it via internet.
Appears to be issue on http://plex.tv/pms/:/ip returning 400 status rather than ip address.

If I access http://plex.tv/pms/:/ip on my browser it does not work.
If I access via TLS on https://plex.tv/pms/:/ip it does return my ip address.

Some relevant logs:

Aug 29, 2022 23:37:33.683 [0x7f14ff504b00] Debug — [Req#37c] PublicAddressManager: Obtaining public address and mapping port.
Aug 29, 2022 23:37:33.683 [0x7f14ffc86b00] Debug — [Req#37c] PublicAddressManager: Obtaining public IP.
Aug 29, 2022 23:37:33.684 [0x7f14ffc86b00] Debug — [Req#37c/HCl#ab] HTTP requesting GET http://plex.tv/pms/:/ip
Aug 29, 2022 23:37:33.794 [0x7f1500108b00] Debug — [HttpClient/HCl#ab] HTTP/1.1 (0.1s) 400 response from GET http://plex.tv/pms/:/ip
Aug 29, 2022 23:37:33.794 [0x7f14ffc86b00] Error — [Req#37c] PublicAddressManager: Unable to get public IP adddress from myPlex (httpCode=400): 400 Bad Request
2

Hey @ChuckPa
Could you please verify if this is known issue or something on my side?

3

Same thing here, just installed 1.28.2.6106

4

If your container or host can’t perform a DNS lookup of plex.tv then you clearly have a network issue on your side.

From the Linux command line nslookup plex.tv

If you get error – You are broken :slight_smile:

5

Same here, just updated to 1.28.2.6106, server running on Unraid docker.

6 
root@lizum:~# nslookup plex.tv
Server:		127.0.0.53
Address:	127.0.0.53#53

Non-authoritative answer:
Name:	plex.tv
Address: 34.250.46.62
Name:	plex.tv
Address: 52.212.166.170
Name:	plex.tv
Address: 176.34.175.0
Name:	plex.tv
Address: 54.154.55.122
Name:	plex.tv
Address: 34.252.41.177

root@lizum:~#

If all else fails, get the logs please (manually by tar.tz or zip)

7

@ChuckPa
From container:

root@09d6bb71df0a:/# getent hosts plex.tv
54.154.55.122   plex.tv
176.34.175.0    plex.tv
52.212.166.170  plex.tv
34.250.46.62    plex.tv
34.252.41.177   plex.tv

From host:

~# nslookup plex.tv
Server:		212.59.8.18
Address:	212.59.8.18#53

Non-authoritative answer:
Name:	plex.tv
Address: 34.252.41.177
Name:	plex.tv
Address: 54.154.55.122
Name:	plex.tv
Address: 176.34.175.0
Name:	plex.tv
Address: 52.212.166.170
Name:	plex.tv
Address: 34.250.46.62

I was trying to point out, that HTTP and HTTPS endpoints are behaving differently (at least for me).
Where HTTPS works without issues and HTTP does not work; returns status 400

Note: Http endpoint is typically difficult to access as browser will simply redirect to https one if you have previously visited secure one. Incognito/private browsing session required.

Same can be reproduced with curl inside container:

root@09d6bb71df0a:/# curl http://plex.tv/pms/:/ip; echo
400 Bad Request


root@09d6bb71df0a:/# curl https://plex.tv/pms/:/ip; echo
78.56.xx.xx
8

I’m pretty sure that’s correct behavior because http is not encrypted

A http request would return plain text… Not cool.

9

Yeah… But plex requests http one :frowning:

10

Where, show me please ?

11

Please see first post logs.

12

I see it… going to dive into PMS code

13

FIY:

This issue appeared after restart, I did not do an upgrade (it was working fine for some weeks). So likely configuration change on your side broke it.
I did upgrade before submitting this issue to see if it fixes the problem.

14

There is no obvious http://plex.tv/pms:/ip in the code by grep. Still searching.

15

Same here. I have 2 plex servers on 2 different networks. Same issue on both after a restart.
Remote access is just spinning.

16

Everything appears to be inside the binary blob

root@09d6bb71df0a:/# grep -rin /pms/:/ip /usr

Binary file /usr/lib/plexmediaserver/Plex Media Server matches
/usr/lib/plexmediaserver/Resources/Plug-ins-44a5bbd28/PlexMovie.bundle/Contents/Code/__init__.py:123:    ip = HTTP.Request('https://plex.tv/pms/:/ip', cacheTime=CACHE_1DAY).content.strip()
17

Adding in that I am seeing the same thing across 2 plex servers (in docker) as well.

18

I’ve just poked in all the right places.

Now to wait for a reply

:slight_smile:

19

Folks,

This was just verified by an employee too.

Downgrade if you can and retest. Let’s see if we can figure out (before they do) if it’s Operations or PMS itself ?

:smiling_imp:

20

Same with 1.28.1.6092-87136b92b which was released 12 days ago. For sure it was working.