Server Version#:1.18.3.2156-349e9837e_amd64
I recently upgraded to Ubuntu 18.04 and I’m having difficulty claiming plex. The server remains available on my home network. I did a little googling and tried to remove the Preferences file and re-claim, but that did not work. Unfortunately I do not have any older .deb files, so I haven’t tried backing down to an older version of Plex.
My logs are attached.
Logs.zip (4.7 MB)
You have network issues, since PMS keeps detecting Network Interface Change
Also, you have timeouts when reaching the internet (plex.tv), and that could indicate a bad gateway, or a faulty DNS.
If gateway is okay, I suggest for a short test you switch your DNS to Google (8.8.8.8 and 8.8.4.4)
I’m not sure I totally understand. The laptop running the server otherwise has fine internet connectivity.
The only other thing I can think is my firewall. I’m using UFW to manage my firewall and am currently allowing connections to PlexMediaServer from Anywhere and vice versa, and this hasn’t changed.
Regardless, do try and switch to Google DNS for a short test
Plex is failing in configuring NAT on your router:
Plex Media Server.4.log:Dec 24, 2019 13:44:27.405 [0x7f03dd7fa700] WARN - NAT: UPnP, error mapping port 16995, error: The port mapping entry specified conflicts with a mapping assigned previously to another client, controlURL: http://192.168.1.1:56688/ctl/IPConn.
Plex Media Server.4.log:Dec 24, 2019 14:44:32.135 [0x7f03f7fff700] WARN - NAT: UPnP, error mapping port 17384, error: The port mapping entry specified conflicts with a mapping assigned previously to another client, controlURL: http://192.168.1.1:56688/ctl/IPConn.
Plex Media Server.4.log:Dec 24, 2019 14:44:32.411 [0x7f03f7fff700] WARN - NAT: UPnP, error mapping port 20310, error: The port mapping entry specified conflicts with a mapping assigned previously to another client, controlURL: http://192.168.1.1:56688/ctl/IPConn.
Plex Media Server.5.log:Dec 21, 2019 18:37:31.727 [0x7f03cd7fa700] WARN - NAT: UPnP, error mapping port 13263, error: The port mapping entry specified conflicts with a mapping assigned previously to another client, controlURL: http://192.168.1.1:56688/ctl/IPConn.
Plex Media Server.5.log:Dec 21, 2019 18:37:32.012 [0x7f03cd7fa700] WARN - NAT: UPnP, error mapping port 13470, error: The port mapping entry specified conflicts with a mapping assigned previously to another client, controlURL: http://192.168.1.1:56688/ctl/IPConn.
Without changing anything in your server, can you share the results of the commands below?
arp -a
netstat -nr
ifconfig
ping plex.tv
ping meta.plex.tv
cat /etc/resolv.conf
thanks all. here are the results to the commands CostaHT suggested. the ping to plex.tv failed but meta.plex.tv worked. I will try the DNS now.
cav@serverUbuntu:~$ arp -a
? (192.168.1.8) at 84:3a:4b:0a:4b:3c [ether] on enp0s25
www.routerlogin.com (192.168.1.1) at 08:02:8e:e8:16:3c [ether] on enp0s25
? (192.168.1.16) at 80:0c:67:3e:9e:1a [ether] on enp0s25
? (192.168.1.6) at 40:4e:36:20:46:ad [ether] on enp0s25
? (192.168.1.3) at 44:09:b8:01:15:8c [ether] on enp0s25
? (192.168.1.9) at 00:05:cd:90:4e:21 [ether] on enp0s25
? (192.168.1.15) at f0:6e:0b:e4:16:8a [ether] on enp0s25
cav@serverUbuntu:~$ netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 enp0s25
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 enp0s25
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s25
cav@serverUbuntu:~$ ifconfig
enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.4 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::21f:16ff:fe34:533 prefixlen 64 scopeid 0x20<link>
ether 00:1f:16:34:05:33 txqueuelen 1000 (Ethernet)
RX packets 46227210 bytes 53102243336 (53.1 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 19846954 bytes 12023567437 (12.0 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf2600000-f2620000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 5775486 bytes 1580713105 (1.5 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5775486 bytes 1580713105 (1.5 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wls1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:26:c6:82:78:e2 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
cav@serverUbuntu:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
cav@serverUbuntu:~$ ping plex.tv
PING plex.tv (99.80.242.242) 56(84) bytes of data.
^C
--- plex.tv ping statistics ---
166 packets transmitted, 0 received, 100% packet loss, time 168935ms
cav@serverUbuntu:~$ ping meta.plex.tv
PING meta.plex.tv.cdn.cloudflare.net (104.18.157.41) 56(84) bytes of data.
64 bytes from 104.18.157.41 (104.18.157.41): icmp_seq=1 ttl=57 time=17.3 ms
--- meta.plex.tv.cdn.cloudflare.net ping statistics ---
64 packets transmitted, 64 received, 0% packet loss, time 63087ms
rtt min/avg/max/mdev = 10.682/15.219/28.308/3.132 ms
After fiddling the the DNS and refreshing Preferences (by stopping Plex, deleting the file, and restarting), Plex seems to be working.
I don’t know much about networking but tried to follow the instructions on these sites. Using dnsmasq I added the severs dane22 suggested as per hte below. add the addresses that dane22 suggested.
cav@serverUbuntu:/$ sudo nano /etc/dnsmasq.conf
# Add other name servers here, with domain specs if they are for
# non-public domains
#server = /localnet/192.168.0.01
server=8.8.4.4
server=8.8.8.8
Sorry, posted that by accident.
I meant to include - I’m not sure if this is a sustainable solution. Does this seem like a reasonable configuration to leave in place, or is there more you would do?
Having Google as DNS is fine
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
