Can't claim server - ipv6 issue?

Server Version#:1.19.3.2740

Seems Plex is listening with IPv6 on port 32400. If I connect to port 32401 I get the plex app - but doesn’t have any place to ‘claim’ the server. And trying to load http://localhost:32400/ (using.a browser on the server) results in a timeout .

pax@ithaki:~$ sudo netstat -ntulp | grep -i plex
tcp 0 0 127.0.0.1:40335 0.0.0.0:* LISTEN 2292/Plex Plug-in [
tcp 0 0 127.0.0.1:32401 0.0.0.0:* LISTEN 2091/Plex Media Ser
tcp 0 0 0.0.0.0:2004 0.0.0.0:* LISTEN 2489/Plex DLNA Serv
tcp 0 0 0.0.0.0:32469 0.0.0.0:* LISTEN 2489/Plex DLNA Serv
tcp 0 0 127.0.0.1:32600 0.0.0.0:* LISTEN 2493/Plex Tuner Ser
tcp6 0 0 :::32400 :::* LISTEN 2091/Plex Media Ser
udp 0 0 0.0.0.0:59148 0.0.0.0:* 2489/Plex DLNA Serv
udp 0 0 0.0.0.0:32410 0.0.0.0:* 2091/Plex Media Ser
udp 0 0 0.0.0.0:32412 0.0.0.0:* 2091/Plex Media Ser
udp 0 0 0.0.0.0:32413 0.0.0.0:* 2091/Plex Media Ser
udp 0 0 0.0.0.0:32414 0.0.0.0:* 2091/Plex Media Ser
udp 0 0 0.0.0.0:1900 0.0.0.0:* 2489/Plex DLNA Serv
udp 0 0 0.0.0.0:1901 0.0.0.0:* 2091/Plex Media Ser
udp 0 0 127.0.0.1:35844 0.0.0.0:* 2091/Plex Media Ser
udp 0 0 127.0.0.1:40887 0.0.0.0:* 2091/Plex Media Ser
udp 0 0 192.168.5.185:41166 0.0.0.0:* 2091/Plex Media Ser
udp 0 0 192.168.5.143:41993 0.0.0.0:* 2091/Plex Media Ser
udp 0 0 0.0.0.0:9781 0.0.0.0:* 2489/Plex DLNA Serv
udp 0 0 192.168.5.143:42609 0.0.0.0:* 2091/Plex Media Ser
udp 0 0 0.0.0.0:44540 0.0.0.0:* 2489/Plex DLNA Serv
udp 0 0 192.168.5.143:44915 0.0.0.0:* 2091/Plex Media Ser
udp 0 0 192.168.5.185:55136 0.0.0.0:* 2091/Plex Media Ser
udp 0 0 192.168.5.185:55931 0.0.0.0:* 2091/Plex Media Ser

PMS Logs in a zip please

can’t access through the portal - no other plex servers… so which files from Linux would you like?

Zip the entire PMS log directory

https://support.plex.tv/articles/202915258-where-is-the-plex-media-server-data-directory-located/

The server was working for awhile. It stopped working. I updated the installation - that didn’t help. So I deleted and reloaded. Still didn’t work. And that’s when I noticed it was listening on the IPv6 address…

pms.zip (762.2 KB)

Are you running it in a docker?

And puzzled here…

The 5 PMS logs shows, that all from today, shows different interfaces every time?

Latest:

May 02, 2020 15:38:19.941 [0x7f3fc6a32f40] DEBUG - Detected primary interface: 192.168.5.143
May 02, 2020 15:38:19.941 [0x7f3fc6a32f40] DEBUG - Network interfaces:
May 02, 2020 15:38:19.941 [0x7f3fc6a32f40] DEBUG -  * 1 lo (127.0.0.1) (loopback: 1)
May 02, 2020 15:38:19.941 [0x7f3fc6a32f40] DEBUG -  * 3 wlo1 (192.168.5.143) (loopback: 0)
May 02, 2020 15:38:19.941 [0x7f3fc6a32f40] DEBUG -  * 4 docker0 (172.17.0.1) (loopback: 0)
May 02, 2020 15:38:19.941 [0x7f3fc6a32f40] DEBUG -  * 1 lo (::1) (loopback: 1)
May 02, 2020 15:38:19.941 [0x7f3fc6a32f40] DEBUG -  * 3 wlo1 (2601:589:4901:2930:4183:8403:4565:2250) (loopback: 0)
May 02, 2020 15:38:19.941 [0x7f3fc6a32f40] DEBUG -  * 3 wlo1 (2601:589:4901:2930:4aa4:72ff:fe42:2895) (loopback: 0)
May 02, 2020 15:38:19.941 [0x7f3fc6a32f40] DEBUG -  * 3 wlo1 (fe80::4aa4:72ff:fe42:2895%wlo1) (loopback: 0)
May 02, 2020 15:38:19.941 [0x7f3fc6a32f40] DEBUG -  * 4 docker0 (fe80::42:d6ff:fe91:1ae5%docker0) (loopback: 0)
May 02, 2020 15:38:19.941 [0x7f3fc6a32f40] DEBUG -  * 6 vethd5e14a0 (fe80::705c:a9ff:fe6f:8134%vethd5e14a0) (loopback: 0)

Above has the primary interface set to a wireless card?

May 02, 2020 15:18:24.864 [0x7f202200af40] DEBUG - Detected primary interface: 0.0.0.0
May 02, 2020 15:18:24.864 [0x7f202200af40] DEBUG - Network interfaces:
May 02, 2020 15:18:24.864 [0x7f202200af40] DEBUG -  * 1 lo (127.0.0.1) (loopback: 1)
May 02, 2020 15:18:24.864 [0x7f202200af40] DEBUG -  * 1 lo (::1) (loopback: 1)

Above has no access to the world?

May 02, 2020 15:14:52.556 [0x7f0e7fd30f40] DEBUG - Detected primary interface: 192.168.5.185
May 02, 2020 15:14:52.556 [0x7f0e7fd30f40] DEBUG - Network interfaces:
May 02, 2020 15:14:52.556 [0x7f0e7fd30f40] DEBUG -  * 1 lo (127.0.0.1) (loopback: 1)
May 02, 2020 15:14:52.556 [0x7f0e7fd30f40] DEBUG -  * 2 eno2 (192.168.5.185) (loopback: 0)
May 02, 2020 15:14:52.556 [0x7f0e7fd30f40] DEBUG -  * 4 docker0 (172.17.0.1) (loopback: 0)
May 02, 2020 15:14:52.556 [0x7f0e7fd30f40] DEBUG -  * 1 lo (::1) (loopback: 1)
May 02, 2020 15:14:52.556 [0x7f0e7fd30f40] DEBUG -  * 4 docker0 (fe80::42:bdff:fe13:18b7%docker0) (loopback: 0)
May 02, 2020 15:14:52.556 [0x7f0e7fd30f40] DEBUG -  * 6 vethf283861 (fe80::d035:4dff:febd:b80d%vethf283861) (loopback: 0)

Above looks good, with the primary set to the onboard nic, but you went away from that?

I’ve been trying various permutations without success. Which permutation do you suggest I stick with?

This is what I have right now - with the wifi link.

With this configuration:

http://localhost:32400/web - timeout
http://localhost:32401/web - plex app without local server or ability to ‘claim’


pax@ithaki:~$ netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.5.1     0.0.0.0         UG        0 0          0 wlo1
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 docker0
172.17.0.0      0.0.0.0         255.255.0.0     U         0 0          0 docker0
192.168.5.0     0.0.0.0         255.255.255.0   U         0 0          0 wlo1
pax@ithaki:~$ sudo netstat -ntulp | grep -i plex
[sudo] password for pax: 
tcp        0      0 127.0.0.1:32401         0.0.0.0:*               LISTEN      25014/Plex Media Se 
tcp        0      0 0.0.0.0:32469           0.0.0.0:*               LISTEN      25345/Plex DLNA Ser 
tcp        0      0 127.0.0.1:32600         0.0.0.0:*               LISTEN      25349/Plex Tuner Se 
tcp        0      0 0.0.0.0:1082            0.0.0.0:*               LISTEN      25345/Plex DLNA Ser 
tcp        0      0 127.0.0.1:41181         0.0.0.0:*               LISTEN      25065/Plex Plug-in  
tcp6       0      0 :::32400                :::*                    LISTEN      25014/Plex Media Se 
udp        0      0 192.168.5.143:40615     0.0.0.0:*                           25014/Plex Media Se 
udp        0      0 0.0.0.0:41647           0.0.0.0:*                           25345/Plex DLNA Ser 
udp        0      0 192.168.5.143:42630     0.0.0.0:*                           25014/Plex Media Se 
udp        0      0 0.0.0.0:10205           0.0.0.0:*                           25345/Plex DLNA Ser 
udp        0      0 127.0.0.1:54324         0.0.0.0:*                           25014/Plex Media Se 
udp        0      0 127.0.0.1:54838         0.0.0.0:*                           25014/Plex Media Se 
udp        0      0 0.0.0.0:58145           0.0.0.0:*                           25345/Plex DLNA Ser 
udp        0      0 0.0.0.0:32410           0.0.0.0:*                           25014/Plex Media Se 
udp        0      0 0.0.0.0:32412           0.0.0.0:*                           25014/Plex Media Se 
udp        0      0 0.0.0.0:32413           0.0.0.0:*                           25014/Plex Media Se 
udp        0      0 0.0.0.0:32414           0.0.0.0:*                           25014/Plex Media Se 
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           25345/Plex DLNA Ser 
udp        0      0 0.0.0.0:1901            0.0.0.0:*                           25014/Plex Media Se 
udp        0      0 192.168.5.143:35125     0.0.0.0:*                           25014/Plex Media Se 
udp        0      0 0.0.0.0:6843            0.0.0.0:*                           25345/Plex DLNA Ser 
pax@ithaki:~$

Don’t use Wifi link for the server, stick with the one I mentioned above

Ok, I turned of the WiFi Chip… purely on ethernet.

I then restarted plex and still have the same problem (using a browser on the server) -

http://localhost:32400/web - timeout
http://localhost:32401/web - plex app without local server or ability to ‘claim’
root@ithaki:/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs# service plexmediaserver restart
root@ithaki:/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs# netstat -rn | fgrep -v cali
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.5.1     0.0.0.0         UG        0 0          0 eno2
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 docker0
172.16.18.0     172.16.82.1     255.255.255.0   UG        0 0          0 tun0
172.16.80.0     172.16.82.1     255.255.255.0   UG        0 0          0 tun0
172.16.81.0     172.16.82.1     255.255.255.0   UG        0 0          0 tun0
172.16.82.0     0.0.0.0         255.255.255.0   U         0 0          0 tun0
172.16.105.0    172.16.82.1     255.255.255.0   UG        0 0          0 tun0
172.16.108.0    172.16.82.1     255.255.255.0   UG        0 0          0 tun0
172.16.111.0    172.16.82.1     255.255.255.0   UG        0 0          0 tun0
172.17.0.0      0.0.0.0         255.255.0.0     U         0 0          0 docker0
172.17.0.0      172.16.82.1     255.255.0.0     UG        0 0          0 tun0
192.168.5.0     0.0.0.0         255.255.255.0   U         0 0          0 eno2
192.168.5.1     0.0.0.0         255.255.255.255 UH        0 0          0 eno2
199.193.189.11  192.168.5.1     255.255.255.255 UGH       0 0          0 eno2
root@ithaki:/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs# netstat -ntulp | grep -i plex
tcp        0      0 127.0.0.1:41307         0.0.0.0:*               LISTEN      19649/Plex Tuner Se 
tcp        0      0 0.0.0.0:1996            0.0.0.0:*               LISTEN      19642/Plex DLNA Ser 
tcp        0      0 127.0.0.1:32401         0.0.0.0:*               LISTEN      19306/Plex Media Se 
tcp        0      0 0.0.0.0:32469           0.0.0.0:*               LISTEN      19642/Plex DLNA Ser 
tcp        0      0 127.0.0.1:40311         0.0.0.0:*               LISTEN      19358/Plex Plug-in  
tcp        0      0 127.0.0.1:32600         0.0.0.0:*               LISTEN      19649/Plex Tuner Se 
tcp6       0      0 :::32400                :::*                    LISTEN      19306/Plex Media Se 
udp        0      0 0.0.0.0:38158           0.0.0.0:*                           19642/Plex DLNA Ser 
udp        0      0 0.0.0.0:5835            0.0.0.0:*                           19642/Plex DLNA Ser 
udp        0      0 10.42.0.0:39235         0.0.0.0:*                           19306/Plex Media Se 
udp        0      0 10.42.0.0:39573         0.0.0.0:*                           19306/Plex Media Se 
udp        0      0 0.0.0.0:7461            0.0.0.0:*                           19642/Plex DLNA Ser 
udp        0      0 0.0.0.0:40950           0.0.0.0:*                           19642/Plex DLNA Ser 
udp        0      0 127.0.0.1:42046         0.0.0.0:*                           19306/Plex Media Se 
udp        0      0 0.0.0.0:10840           0.0.0.0:*                           19642/Plex DLNA Ser 
udp        0      0 10.42.0.0:44431         0.0.0.0:*                           19306/Plex Media Se 
udp        0      0 127.0.0.1:45193         0.0.0.0:*                           19306/Plex Media Se 
udp        0      0 192.168.5.185:46662     0.0.0.0:*                           19306/Plex Media Se 
udp        0      0 192.168.5.185:58548     0.0.0.0:*                           19306/Plex Media Se 
udp        0      0 192.168.5.185:59562     0.0.0.0:*                           19306/Plex Media Se 
udp        0      0 0.0.0.0:32410           0.0.0.0:*                           19306/Plex Media Se 
udp        0      0 0.0.0.0:32412           0.0.0.0:*                           19306/Plex Media Se 
udp        0      0 0.0.0.0:32413           0.0.0.0:*                           19306/Plex Media Se 
udp        0      0 0.0.0.0:32414           0.0.0.0:*                           19306/Plex Media Se 
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           19642/Plex DLNA Ser 
udp        0      0 0.0.0.0:1901            0.0.0.0:*                           19306/Plex Media Se 
root@ithaki:/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs#

Logs please, again :wink:

sure thing…
pms.zip (860.0 KB)

Seems good, now two Q’s for you:

  • When browsing towards http://192.168.5.185:32400/identity does the xml that shows in your browser has an entry named claimed and if so, is it 0 or 1?

  • are you browsing towards PMS directly on the server, or from a workstation, and if so, what’s the IP address of that workstation?

I am running Firefox on the server.

I get a timeout when going to that url.

Huh…

It’s an IP loaded on that same box?

What happens, if you try http://127.0.0.1:32400/identity ?

And timeout might be firewall related!

And this Q still needs to be answered!

Plex is not running inside docker.

No firewall.

Obviously docker has a bunch of iptables. I’ll slog through it again but I didn’t see anything obvious. Btw, this problem happens even when docker wasn’t running so iptables would have been empty. I’ve rebooted the machine multiple times this afternoon. With and without docker starting.

Remember, the timeout is part of my original post. Hasn’t changed.

The same machine is running Kubernetes and I’ve been working on KubeFlow in between working on this issue

Hmm. It would be interesting to get Plex in docker. But that would be after getting it running again. I can setup multus-cni which should make running plex in kubernetes pretty easy - just give the container it’s own LAN IP address

Yes. Timeout when going to localhost as well.

And 192.168.5.185 is the machine’s address on its Ethernet.

I get a response from port 32401. But it’s obviously not the right server.

The only thing I’ve noticed is 32400 is running on tcp6. Unfortunately I haven’t played around much with IPv6 to know what difference that makes.

Btw, fwiw, I’m running on Ubuntu 18.04

Hmmm…

According to the logs, PMS is running, and is listening to 192.168.1.185 which is the servers own interface, and yet it’s not possible to browse it?

It’s NOT IPV6 related, but IPV4 related !

If your PMS server is running, and reports it’s bound and listning to port 32400 on both loopback as well as the IPV4 address, and you can’t reach it, it’s something else!

Can you, just to make sure it’s not a browser issue, try and install Chrome on the box?

I think there is a difference between what you are seeing in the logs and what I’m seeing in netstat ?

See the results below using curl

I live in Linux network. Especially recently. This has me stumped.


Welcome to Ubuntu 18.04.4 LTS (GNU/Linux 5.3.0-51-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

 * Ubuntu 20.04 LTS is out, raising the bar on performance, security,
   and optimisation for Intel, AMD, Nvidia, ARM64 and Z15 as well as
   AWS, Azure and Google Cloud.

     https://ubuntu.com/blog/ubuntu-20-04-lts-arrives


 * Canonical Livepatch is available for installation.
   - Reduce system reboots and improve kernel security. Activate at:
     https://ubuntu.com/livepatch
Last login: Sat May  2 19:42:48 2020 from 192.168.5.128
pax@ithaki:~$ sudo bash
[sudo] password for pax: 
root@ithaki:~# iptables -L -n | grep 3240
root@ithaki:~# netstat -ntulp | grep 3240
tcp        0      0 127.0.0.1:32401         0.0.0.0:*               LISTEN      19306/Plex Media Se 
tcp6       0      0 :::32400                :::*                    LISTEN      19306/Plex Media Se 
root@ithaki:~# curl http://localhost:32400
curl: (7) Failed to connect to localhost port 32400: Connection refused
root@ithaki:~# curl http://localhost:32401
<html><head><script>window.location = window.location.href.match(/(^.+\/)[^\/]*$/)[1] + 'web/index.html';</script><title>Unauthorized</title></head><body><h1>401 Unauthorized</h1></body></html>root@ithaki:~# curl http://192.168.5.185:32400
curl: (7) Failed to connect to 192.168.5.185 port 32400: Connection refused
root@ithaki:~# curl http://192.168.5.185:32401
curl: (7) Failed to connect to 192.168.5.185 port 32401: Connection refused
root@ithaki:~#