Server Version#: 1.18.0.1944
Player Version#:
I have Plex installed on a fresh Ubuntu 19.10 install.
Plex player will work on the machine, but I cannot be “local” on any other device on the same network.
I did install Plex on another Windows machine - it works fine as local.
On the Ubuntu machine I CAN access Plex from the windows server 192.168.1.118:32400
On the Windows machine I cannot access Plex on the Ubuntu machine 192.168.1.30:32400
Both machines are on the same Asus router.
I can ping both machines from each other (I can also share files between the 2)
I have Roku and Amazon fire device - Windows Plex shows as Local and Ubuntu Plex shows as Relay
I have completely powered down the network and both machines and re-started them.
Relay occurs when there is no direct connection (ports blocked) in most cases.
Check here first and advise?
I have the Ubuntu firewall completely disabled.
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 9414/smbd
tcp 0 0 0.0.0.0:8989 0.0.0.0:* LISTEN 1678/mono
tcp 0 0 127.0.0.1:20030 0.0.0.0:* LISTEN 1677/nxserver.bin
tcp 0 0 127.0.0.1:20000 0.0.0.0:* LISTEN 12131/nxserver.bin
tcp 0 0 127.0.0.1:17600 0.0.0.0:* LISTEN 2534/dropbox
tcp 0 0 0.0.0.0:4000 0.0.0.0:* LISTEN 2213/nxd
tcp 0 0 127.0.0.1:12001 0.0.0.0:* LISTEN 3348/nxnode.bin
tcp 0 0 127.0.0.1:12002 0.0.0.0:* LISTEN 12159/nxnode.bin
tcp 0 0 127.0.0.1:17603 0.0.0.0:* LISTEN 2534/dropbox
tcp 0 0 127.0.0.1:25001 0.0.0.0:* LISTEN 3368/nxclient.bin
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 1756/mysqld
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 9414/smbd
tcp 0 0 127.0.0.1:41707 0.0.0.0:* LISTEN 2955/Plex Plug-in [
tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN 3154/perl
tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN 2443/python2
tcp 0 0 127.0.0.1:26001 0.0.0.0:* LISTEN 3348/nxnode.bin
tcp 0 0 127.0.0.1:32401 0.0.0.0:* LISTEN 2902/Plex Media Ser
tcp 0 0 127.0.0.1:26002 0.0.0.0:* LISTEN 12159/nxnode.bin
tcp 0 0 0.0.0.0:8084 0.0.0.0:* LISTEN 1593/mono
tcp 0 0 0.0.0.0:32469 0.0.0.0:* LISTEN 3251/Plex DLNA Serv
tcp 0 0 0.0.0.0:1749 0.0.0.0:* LISTEN 3251/Plex DLNA Serv
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 1309/systemd-resolv
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 1511/cupsd
tcp 0 0 127.0.0.1:32600 0.0.0.0:* LISTEN 3248/Plex Tuner Ser
tcp 0 0 127.0.0.1:7001 0.0.0.0:* LISTEN 3348/nxnode.bin
tcp6 0 0 :::5500 :::* LISTEN 2433/clementine
tcp6 0 0 :::445 :::* LISTEN 9414/smbd
tcp6 0 0 :::4000 :::* LISTEN 2213/nxd
tcp6 0 0 :::33060 :::* LISTEN 1756/mysqld
tcp6 0 0 :::139 :::* LISTEN 9414/smbd
tcp6 0 0 :::32400 :::* LISTEN 2902/Plex Media Ser
tcp6 0 0 :::80 :::* LISTEN 1795/apache2
tcp6 0 0 ::1:631 :::* LISTEN 1511/cupsd
tcp6 0 0 ::1:7001 :::* LISTEN 3348/nxnode.bin
It’s binding to IPv6, not IPv4
Please try netstat -an | grep 32400 and see where we’re at.
I had another report of PMS binding on IPv6
If you have IPv6 enabled on your host, please disable it. PMS doesn’t use V6
This failing, we will manually add a hidden preference to force it off
The Preference to add to the XML in Preferences.xml:
EnableIPV6="0" to force it to remain off.
Should this NOT work, please let me know immediately
netstat -an | grep 32400
tcp 0 0 192.168.1.20:46468 73.247.6.8:32400 ESTABLISHED
tcp 0 1 192.168.1.20:33662 192.168.0.5:32400 SYN_SENT
tcp 0 1 192.168.1.20:58476 192.168.1.118:32400 SYN_SENT
tcp 0 0 127.0.0.1:35966 127.0.0.1:32400 ESTABLISHED
tcp 0 0 127.0.0.1:35978 127.0.0.1:32400 ESTABLISHED
tcp 0 0 192.168.1.20:34604 192.168.1.20:32400 ESTABLISHED
tcp 0 0 127.0.0.1:35954 127.0.0.1:32400 ESTABLISHED
tcp 0 1 192.168.1.20:55336 192.168.1.4:32400 SYN_SENT
tcp 0 0 127.0.0.1:35972 127.0.0.1:32400 ESTABLISHED
tcp 0 1 192.168.1.20:33668 192.168.0.5:32400 SYN_SENT
tcp 0 1 192.168.1.20:58470 192.168.1.118:32400 SYN_SENT
tcp 0 1 192.168.1.20:55342 192.168.1.4:32400 SYN_SENT
tcp 0 1 192.168.1.20:42624 192.168.2.1:32400 SYN_SENT
tcp 0 1 192.168.1.20:42618 192.168.2.1:32400 SYN_SENT
tcp 0 0 127.0.0.1:35952 127.0.0.1:32400 TIME_WAIT
tcp 0 0 192.168.1.20:46484 73.247.6.8:32400 ESTABLISHED
tcp6 0 0 :::32400 :::* LISTEN
tcp6 0 0 127.0.0.1:32400 127.0.0.1:35944 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:35946 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:35948 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:35972 ESTABLISHED
tcp6 0 0 127.0.0.1:32400 127.0.0.1:35954 ESTABLISHED
tcp6 0 0 127.0.0.1:32400 127.0.0.1:35958 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:35966 ESTABLISHED
tcp6 0 0 192.168.1.20:32400 192.168.1.20:34604 ESTABLISHED
tcp6 0 0 127.0.0.1:32400 127.0.0.1:35950 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:35964 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:35978 ESTABLISHED
And I have no clue how to disable IPv6 on Ubuntu…
I modifed the XML file.
netstat -an | grep 32400
tcp 0 0 127.0.0.1:33900 127.0.0.1:32400 TIME_WAIT
tcp 0 0 127.0.0.1:33912 127.0.0.1:32400 TIME_WAIT
tcp 0 1 192.168.1.20:38922 192.168.1.118:32400 SYN_SENT
tcp 0 0 127.0.0.1:33936 127.0.0.1:32400 ESTABLISHED
tcp 0 0 127.0.0.1:33934 127.0.0.1:32400 TIME_WAIT
tcp 0 0 192.168.1.20:49026 192.168.1.20:32400 TIME_WAIT
tcp 0 0 127.0.0.1:34076 127.0.0.1:32400 FIN_WAIT2
tcp 0 1 192.168.1.20:38924 192.168.1.118:32400 SYN_SENT
tcp 0 0 192.168.1.20:55630 73.247.6.8:32400 ESTABLISHED
tcp 0 0 127.0.0.1:33958 127.0.0.1:32400 TIME_WAIT
tcp 0 0 127.0.0.1:33940 127.0.0.1:32400 ESTABLISHED
tcp6 0 0 :::32400 :::* LISTEN
tcp6 0 0 127.0.0.1:32400 127.0.0.1:34076 CLOSE_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33754 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33716 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33782 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33936 ESTABLISHED
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33794 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33750 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33948 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33906 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33746 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33760 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33776 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33764 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33806 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33752 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33940 ESTABLISHED
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33910 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33718 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33762 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33748 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33798 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33680 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33682 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33744 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33934 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33928 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33920 TIME_WAIT
tcp6 0 0 127.0.0.1:32400 127.0.0.1:33914 TIME_WAIT
I disabled IPV6 in Ubuntu using GRUB
netstat -an | grep 32400
tcp 0 0 0.0.0.0:32400 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:32400 127.0.0.1:53378 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53172 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53188 TIME_WAIT
tcp 0 0 127.0.0.1:53816 127.0.0.1:32400 FIN_WAIT2
tcp 0 0 127.0.0.1:32400 127.0.0.1:53358 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53152 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53264 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53220 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53196 TIME_WAIT
tcp 0 0 192.168.1.20:49704 73.247.6.8:32400 ESTABLISHED
tcp 0 0 127.0.0.1:32400 127.0.0.1:53676 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53672 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53816 CLOSE_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53098 TIME_WAIT
tcp 0 0 127.0.0.1:53702 127.0.0.1:32400 FIN_WAIT2
tcp 0 0 127.0.0.1:32400 127.0.0.1:53268 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53702 CLOSE_WAIT
tcp 0 0 127.0.0.1:53696 127.0.0.1:32400 ESTABLISHED
tcp 0 0 127.0.0.1:32400 127.0.0.1:53386 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53150 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53398 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53206 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53174 TIME_WAIT
tcp 0 0 127.0.0.1:53716 127.0.0.1:32400 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53100 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53684 TIME_WAIT
tcp 0 0 127.0.0.1:53398 127.0.0.1:32400 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53404 TIME_WAIT
tcp 0 0 127.0.0.1:53354 127.0.0.1:32400 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53354 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53680 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53674 TIME_WAIT
tcp 0 0 127.0.0.1:53356 127.0.0.1:32400 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53686 ESTABLISHED
tcp 0 0 127.0.0.1:32400 127.0.0.1:53272 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53166 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53388 TIME_WAIT
tcp 0 0 192.168.1.20:41722 192.168.1.20:32400 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53612 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53410 TIME_WAIT
tcp 0 0 127.0.0.1:53686 127.0.0.1:32400 ESTABLISHED
tcp 0 0 127.0.0.1:32400 127.0.0.1:53168 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53688 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53484 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53696 ESTABLISHED
tcp 0 0 127.0.0.1:32400 127.0.0.1:53208 TIME_WAIT
tcp 0 0 127.0.0.1:32400 127.0.0.1:53170 TIME_WAIT
unix 3 [ ] STREAM CONNECTED 32400 /run/dbus/system_bus_socket
ChuckPa
October 23, 2019, 7:56pm
11
Now it looks good.
The rest of the reasons you’re not able to see it locally is firewall / subnet / something local.
I can see Plex/web reaching out to another machine.
May I have the ZIP logs, collected 3 minutes after restarting PMS ?
One thing you can add to Preferences.xml is EnableIPv6="0", save and restart.
This will change most of the bindings.
ChuckPa
October 23, 2019, 9:57pm
12
Adding:
I just reproduced the TCP v6 problem.
I have flagged it Critical and submitted to Engineering, complete with all the data.
ChuckPa
October 24, 2019, 12:52am
13
I had a nice chat with one of the Engineers.
It is starting to look like a problem with the bundled app in 1.18.0 (Plex/web).
The server appears ok and explains why we see it continue to run when inaccessible via the browser.
I will see if there’s a way to decouple the bundled web app from a previous version so we can get you working at least temporarily .
The primary issue is at setup time.
system
Closed
January 22, 2020, 12:52am
14
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.