Server Version#: 1.42.1.10060
While I’ve done my best to investigate the issue on my own, I’ve run up to a brick wall now. I am unable to claim my Plex server through the web app, while running on a local machine. The machine running PMS is running Ubuntu Server, if that matters.
When I attempt to press the “Claim Server” button, it simply spins for a second and returns to saying “Claim Server”. The logs seem to indicate some kind of connection issue regarding connections through port 443. I have allowed that port through Ubuntu’s UFW firewall, but that didn’t seem to change anything.
Logs.zip (154.5 KB)
Plex Media Server cannot communicate with hosts at plex.tv.
- Verify the network settings are correct: ip address, default gateway, network mask.
- Configure the server to use a public DNS such as 1.1.1.1 (Cloudflare), 8.8.8.8 (Google), or 9.9.9.9 (Quad9).
- Drop the firewall, at least temporarily, for testing purposes.
You can also try the User Credential Reset Utility.
Firewall disabled, DNS is already set to 1.1.1.1, No change. I did make sure to restart the server after disabling the firewall.
As for my network settings, I’m not entirely sure I understand which set you’re referring to. Server? Client? Router?
The server. It cannot talk to systems at plex.tv. That is why claiming fails.
If the settings are incorrect, then the server would have trouble accessing any site on the Internet, but it never hurts to double check them.
Examples from my Ubuntu server:
This shows the IP address and netmask.
$ ifconfig
enp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.46 netmask 255.255.255.0 broadcast 192.168.1.255
This shows the gateway. It is usually the IP address of your router (unless you’ve multiple networks, routers, etc.).
$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.254 0.0.0.0 UG 100 0 0 enp1s0
192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 enp1s0
$
Went over this again and had someone else take a look as well.
It is not a DNS problem. Otherwise there would be DNS lookup failures in the log file.
Something is blocking the Plex server communicating on port 443 to hosts at plex.tv.
Port 443 is the https port, so it is not normally blocked by firewalls.
You mentioned the Ubuntu firewall was disabled. Maybe double check it is still down or re-issue sudo ufw disable to make sure?
Anything else in your network that could block the traffic?
This is a bog standard home wifi network, there shouldn’t be anything in the way, and I wouldn’t even begin to know where to look.
I disabled the firewall, ran a clean install. Nothing seems to have changed. Is it possible I have to forward the https port? Should I try pinging something over https first?
Looking at your forum account, I see an IPv6 address without IPv4
The forums are IPv4 and IPv6
Try this, You should get this response:
[chuck@lizum ~.2005]$ curl http://plex.tv
<html>
<head><title>308 Permanent Redirect</title></head>
<body>
<center><h1>308 Permanent Redirect</h1></center>
<hr><center>nginx</center>
</body>
</html>
[chuck@lizum ~.2006]$
When you look at the WAN IP of your modem router, do you see both IPv4 and IPv6 ?
I suspect you’ll only see IPv6
When I run that curl command from my server, this is the response I get.
curl: (7) Failed to connect to plex.tv port 80 after 24 ms: Couldn’t connect to server
I’m not sure what the IP address tied to my forum account has to do with it. However, as far as I’m able to tell, I have both an IPv4 and IPv6 address on the router.
Edit: Just because I was curious, I ran that same command with http://google.com and https://google.com and was able to get a response both times.
I’m convinced there is a firewall / block somewhere between your server and plex.tv or your provider no longer supports IPv4.
- plex.tv – bare domain is its own site (the services in the cloud
- forums.plex.tv – this site
- www.plex.tv – Account management and streaming video gateway
** Plex.tv
[chuck@lizum Downloads.2018]$ nslookup plex.tv
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: plex.tv
Address: 52.17.59.150
Name: plex.tv
Address: 52.209.82.108
[chuck@lizum Downloads.2019]$
** www.plex.tv
[chuck@lizum Downloads.2019]$ nslookup www.plex.tv
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: www.plex.tv
Address: 104.18.36.51
Name: www.plex.tv
Address: 172.64.151.205
Name: www.plex.tv
Address: 2606:4700:4400::ac40:97cd
Name: www.plex.tv
Address: 2606:4700:4400::6812:2433
[chuck@lizum Downloads.2020]$
** forums.plex.tv
[chuck@lizum Downloads.2020]$ nslookup forums.plex.tv
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
forums.plex.tv canonical name = plex.hosted-by-discourse.com.
Name: plex.hosted-by-discourse.com
Address: 184.105.99.43
Name: plex.hosted-by-discourse.com
Address: 2602:fd3f:3:ff01::2b
[chuck@lizum Downloads.2021]$
At this point, the best next step is to contact your ISP and confirm plex.tv (the IPv4 addresses above) are not blocked.
I can rule that out rather quickly. Spectrum internet supports both IPv4 and IPv6.
Performing nslookup just now has returned the following.
Plex.tv
stationmaster@stationmainframe:~$ nslookup plex.tv
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: plex.tv
Address: 52.209.82.108
Name: plex.tv
Address: 52.17.59.150
www.plex.tv
stationmaster@stationmainframe:~$ nslookup www.plex.tv
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: www.plex.tv
Address: 172.64.151.205
Name: www.plex.tv
Address: 104.18.36.51
Name: www.plex.tv
Address: 2606:4700:4400::6812:2433
Name: www.plex.tv
Address: 2606:4700:4400::ac40:97cd
forums.plex.tv
stationmaster@stationmainframe:~$ nslookup forums.plex.tv
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
forums.plex.tv canonical name = plex.hosted-by-discourse.com.
Name: plex.hosted-by-discourse.com
Address: 184.105.99.43
Name: plex.hosted-by-discourse.com
Address: 2602:fd3f:3:ff01::2b
Performing the curl command still returns the same results. (Which is to say, that it cannot communicate.)
I have checked my router settings, and as far as I can tell, there is no indication of any kind of firewall.
What other equipment is running on your LAN between your computer (PMS server) and the ISP’s modem/router ? (Make & Model please if anything other than a simple switch)
You overestimate me, my good man. (Though I understand the need to account for every variable.)
The only thing between my router and the PMS server is an ethernet cable.
Now for me to understand your ISP. (rolling eyes LOL)
When you look at the bottom of their modem/router, what model is it please ?
This is a strange one. I had Spectrum for years and never had trouble with them.
Try the nslookup & curl commands from another system and see if you have the same results. If on a Mac, use the terminal. On a PC, use the c:\ prompt.
nslookup and curl both work as advertised on other machines, those are connected to the same network via 5ghz wifi.
I don’t know. To me, it seems the problem is with the Ubuntu installation, since nslookup & curl work on a different system. But troubleshooting such problems is beyond my Linux knowledge.
It’s possible. The Poweredge that it’s running on still has some bios level stuff floating around that I, admittedly, do not have the knowledge to interact with. The only thing I could think of would be the network controller having some dedicated filter, since it’s a former business machine, but that feels absurd.
This may not have any effect, but if you want to attempt a reversion back to an earlier PMS version, here is a link to 1.41.6.9685. Just to rule out some issue with a recent version.
Well, time to finally put this to bed. The ultimate issue ended up being that my default gateway in my netplan file started at 192.168.0.1 when my new carriers IP range starts at 192.168.1.1. This explains why I could connect to it, but not receive any HTTP traffic.
