PMS Logs Error requesting .plex.direct - Couldn't connect to server

Seeing this in the logs on both servers. Servers are on Proxmox VMs and cabled.
Any way to resolve this?

Server 1:

Aug 17, 2023 09:56:51.731 [140211898301240] DEBUG - PublicAddressManager: Got public IP from v4.plex.tv: WAN-IP
Aug 17, 2023 09:57:06.556 [140211898301240] DEBUG - NAT: UPnP, found device <http://10.0.1.140:80/dms/device.xml> with private address <10.0.1.10>
Aug 17, 2023 09:57:06.556 [140211898301240] DEBUG - NAT: UPnP, not an IGD: <http://10.0.1.140:80/dms/device.xml>.
Aug 17, 2023 09:57:06.569 [140211898301240] DEBUG - NAT: UPnP, found device <http://10.0.1.155:8008/ssdp/device-desc.xml> with private address <10.0.1.10>
Aug 17, 2023 09:57:06.569 [140211898301240] DEBUG - NAT: UPnP, not an IGD: <http://10.0.1.155:8008/ssdp/device-desc.xml>.
Aug 17, 2023 09:57:06.575 [140211898301240] DEBUG - NAT: UPnP, found device <http://10.0.1.30:8008/ssdp/device-desc.xml> with private address <10.0.1.10>
Aug 17, 2023 09:57:06.575 [140211898301240] DEBUG - NAT: UPnP, not an IGD: <http://10.0.1.30:8008/ssdp/device-desc.xml>.
Aug 17, 2023 09:57:06.578 [140211898301240] DEBUG - NAT: UPnP, found device <http://10.0.1.150:5000/ssdp/desc-DSM-eth0.xml> with private address <10.0.1.10>
Aug 17, 2023 09:57:06.578 [140211898301240] DEBUG - NAT: UPnP, not an IGD: <http://10.0.1.150:5000/ssdp/desc-DSM-eth0.xml>.
Aug 17, 2023 09:57:06.578 [140211898301240] DEBUG - NAT: UPnP, getPublicIP didn't find usable IGD.
Aug 17, 2023 09:57:16.583 [140211898301240] WARN - NAT: PMP, timed out waiting for response.
Aug 17, 2023 09:57:16.585 [140211898301240] DEBUG - [HCl#121f2] HTTP requesting GET https://WAN-IP.1c668654f8bf44ab8522cafd97b76185.plex.direct:32402/identity
Aug 17, 2023 09:57:16.586 [140212341455672] WARN - [HttpClient/HCl#121f2] HTTP error requesting GET https://WAN-IP.1c668654f8bf44ab8522cafd97b76185.plex.direct:32402/identity (7, Couldn't connect to server) (Failed to connect to WAN-IP.1c668654f8bf44ab8522cafd97b76185.plex.direct port 32402 after 0 ms: Couldn't connect to server)
Aug 17, 2023 09:57:16.586 [140211898301240] DEBUG - MyPlex: mapping state set to 'Mapped - Not Published'.
Aug 17, 2023 09:57:16.587 [140211898301240] DEBUG - MyPlex: Last published value didn't change, we're done.

Server 2:

Aug 17, 2023 09:54:38.856 [140337288670008] DEBUG - [HCl#2237] HTTP requesting GET https://(WAN-IP).plex.direct:32401/identity
Aug 17, 2023 09:54:38.857 [140337679027000] WARN - [HttpClient/HCl#2237] HTTP error requesting GET https://(WAN-IP).plex.direct:32401/identity (7, Couldn't connect to server) (Failed to connect to (WAN-IP).plex.direct port 32401 after 0 ms: Couldn't connect to server)
Aug 17, 2023 09:54:38.857 [140337288670008] DEBUG - MyPlex: mapping state set to 'Mapped - Not Published'.

Unsure if this is related from the system logs:

2023-08-17 08:56:45,033 (7f8e509feb30) :  DEBUG (networking:144) - Requesting 'http://resources-cdn.plexapp.com/hashes.json'
2023-08-17 08:56:45,118 (7f8e509feb30) :  ERROR (networking:197) - Error opening URL 'http://resources-cdn.plexapp.com/hashes.json'
2023-08-17 08:56:45,123 (7f8e509feb30) :  CRITICAL (runtime:1299) - Exception getting hosted resource hashes (most recent call last):
  File "/usr/lib/plexmediaserver/Resources/Plug-ins-b6a09ad81/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/components/runtime.py", line 1291, in get_resource_hashes
    json = self._core.networking.http_request("http://resources-cdn.plexapp.com/hashes.json", timeout=5).content
  File "/usr/lib/plexmediaserver/Resources/Plug-ins-b6a09ad81/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/components/networking.py", line 243, in content
    return self.__str__()
  File "/usr/lib/plexmediaserver/Resources/Plug-ins-b6a09ad81/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/components/networking.py", line 221, in __str__
    self.load()
  File "/usr/lib/plexmediaserver/Resources/Plug-ins-b6a09ad81/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/components/networking.py", line 159, in load
    f = self._opener.open(req, timeout=self._timeout)
  File "/usr/lib/plexmediaserver/Resources/Python/python27.zip/urllib2.py", line 435, in open
    response = meth(req, response)
  File "/usr/lib/plexmediaserver/Resources/Python/python27.zip/urllib2.py", line 548, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib/plexmediaserver/Resources/Python/python27.zip/urllib2.py", line 473, in error
    return self._call_chain(*args)
  File "/usr/lib/plexmediaserver/Resources/Python/python27.zip/urllib2.py", line 407, in _call_chain
    result = func(*args)
  File "/usr/lib/plexmediaserver/Resources/Python/python27.zip/urllib2.py", line 556, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
HTTPError: HTTP Error 404: Not Found

Server Version#: Plex Media Server v1.32.6.7371-b6a09ad81 - Debian GNU/Linux PC x86_64 - build: linux-x86_64 debian / Linux version: 12 (bookworm), language: en-US
Player Version#: 4.113.2

It can’t find a gateway by probing.

Have you tried setting the default gateway address manually in the VM ?

had a look on both Plex server VMs, the Hypervisor and Router - all seems to be fine - perhaps I missed something?

Non standard items are 1. router DNS (manually set in VMs as per /etc/resolv.conf) and 2. both Plex severs have non default ports to accomodate 2 servers.

**ROUTER**

Subnet: 255.255.255.0
Gateway: 000.233.1.44
DNS1: 58.96.9.5
DNS2: 220.233.0.4
MRU: 1492
MTU: 1492

**PROXMOX**

$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq master vmbr0 state UP group default qlen 1000
    link/ether 6c:3b:e5:87:b3:8c brd ff:ff:ff:ff:ff:ff
    altname enp1s0
3: wlo1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether de:25:7c:2b:c9:1c brd ff:ff:ff:ff:ff:ff permaddr c8:f7:33:c1:aa:16
    altname wlp2s0
4: fake0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 72:31:ad:c8:e2:a3 brd ff:ff:ff:ff:ff:ff
    inet 1.2.3.4/24 brd 1.2.3.255 scope global noprefixroute fake0
       valid_lft forever preferred_lft forever
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 6c:3b:e5:87:b3:8c brd ff:ff:ff:ff:ff:ff
    inet 10.0.1.9/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::6e3b:e5ff:fe87:b38c/64 scope link 
       valid_lft forever preferred_lft forever
6: veth101i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP group default qlen 1000
    link/ether fe:31:58:ba:a7:0c brd ff:ff:ff:ff:ff:ff link-netnsid 0
7: veth102i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr102i0 state UP group default qlen 1000
    link/ether fe:7c:01:15:70:13 brd ff:ff:ff:ff:ff:ff link-netnsid 1
8: fwbr102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 52:b6:fe:43:75:7d brd ff:ff:ff:ff:ff:ff
9: fwbr101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 5a:c5:4a:9b:95:84 brd ff:ff:ff:ff:ff:ff
10: fwpr102p0@fwln102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether e6:59:83:4a:8a:d7 brd ff:ff:ff:ff:ff:ff
11: fwln102i0@fwpr102p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr102i0 state UP group default qlen 1000
    link/ether fe:b8:79:2e:a7:61 brd ff:ff:ff:ff:ff:ff
12: fwpr101p0@fwln101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 9a:25:dc:c1:b3:3e brd ff:ff:ff:ff:ff:ff
13: fwln101i0@fwpr101p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP group default qlen 1000
    link/ether 5a:81:52:76:64:8a brd ff:ff:ff:ff:ff:ff
14: veth100i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
    link/ether fe:fb:08:d5:17:14 brd ff:ff:ff:ff:ff:ff link-netnsid 2
15: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 46:3c:fc:a9:90:91 brd ff:ff:ff:ff:ff:ff
16: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 86:4f:46:6a:6c:c6 brd ff:ff:ff:ff:ff:ff
17: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
    link/ether c2:0e:54:8b:56:45 brd ff:ff:ff:ff:ff:ff
18: tap103i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq master fwbr103i0 state UNKNOWN group default qlen 1000
    link/ether 06:aa:09:b6:8a:53 brd ff:ff:ff:ff:ff:ff
19: fwbr103i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether da:59:24:4c:c7:47 brd ff:ff:ff:ff:ff:ff
20: fwpr103p0@fwln103i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 66:a4:6a:28:a6:3e brd ff:ff:ff:ff:ff:ff
21: fwln103i0@fwpr103p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr103i0 state UP group default qlen 1000
    link/ether 3a:97:cc:86:18:a8 brd ff:ff:ff:ff:ff:ff

$ ip route
default via 10.0.1.1 dev vmbr0 proto kernel onlink 
default via 1.2.3.1 dev fake0 proto static metric 550 
1.2.3.0/24 dev fake0 proto kernel scope link src 1.2.3.4 metric 550 
10.0.1.0/24 dev vmbr0 proto kernel scope link src 10.0.1.9 

**PLEX SERVER 1 (10.0.1.10)**

@lxc-plex:~# cat /etc/resolv.conf
# --- BEGIN PVE ---
search google.com
nameserver 1.1.1.1
nameserver 8.8.8.8
# --- END PVE ---

@lxc-plex:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: eth0@if14: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 26:b0:01:50:03:a5 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 10.0.1.10/24 brd 10.0.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::24b0:1ff:fe50:3a5/64 scope link 
       valid_lft forever preferred_lft forever

@lxc-plex:~# ip route
default via 10.0.1.1 dev eth0 onlink 
10.0.1.0/24 dev eth0 proto kernel scope link src 10.0.1.10 
root@lxc-plex:~# 

@lxc-plex:~# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.0.1.1        0.0.0.0         UG    0      0        0 eth0
10.0.1.0        0.0.0.0         255.255.255.0   U     0      0        0 eth0



@lxc-plex:~# ping 10.0.1.1
PING 10.0.1.1 (10.0.1.1) 56(84) bytes of data.
64 bytes from 10.0.1.1: icmp_seq=1 ttl=64 time=0.880 ms
64 bytes from 10.0.1.1: icmp_seq=2 ttl=64 time=0.423 ms
64 bytes from 10.0.1.1: icmp_seq=3 ttl=64 time=0.512 ms
64 bytes from 10.0.1.1: icmp_seq=4 ttl=64 time=0.414 ms
64 bytes from 10.0.1.1: icmp_seq=5 ttl=64 time=0.488 ms
64 bytes from 10.0.1.1: icmp_seq=6 ttl=64 time=0.638 ms

@lxc-plex:~# ping 000.233.1.44 (WAN Gateway)
PING 000.233.1.44 (000.233.1.44) 56(84) bytes of data.
64 bytes from 000.233.1.44: icmp_seq=1 ttl=255 time=4.91 ms
64 bytes from 000.233.1.44: icmp_seq=2 ttl=255 time=4.77 ms
64 bytes from 000.233.1.44: icmp_seq=3 ttl=255 time=6.71 ms
64 bytes from 000.233.1.44: icmp_seq=4 ttl=255 time=5.57 ms
64 bytes from 000.233.1.44: icmp_seq=5 ttl=255 time=5.11 ms
64 bytes from 000.233.1.44: icmp_seq=6 ttl=255 time=4.95 ms

**PLEX SERVER 2 (10.0.1.12)**

@lxc-plex2:~# cat /etc/resolv.conf
# --- BEGIN PVE ---
search google.com
nameserver 1.1.1.1
nameserver 8.8.8.8
# --- END PVE ---

@lxc-plex2:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: eth0@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether c2:91:9e:a4:31:9c brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 10.0.1.12/24 brd 10.0.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::c091:9eff:fea4:319c/64 scope link 
       valid_lft forever preferred_lft forever

@lxc-plex2:~# ip route
default via 10.0.1.1 dev eth0 onlink 
10.0.1.0/24 dev eth0 proto kernel scope link src 10.0.1.12 

@lxc-plex2:~# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.0.1.1        0.0.0.0         UG    0      0        0 eth0
10.0.1.0        0.0.0.0         255.255.255.0   U     0      0        0 eth0

@lxc-plex2:~# ping 10.0.1.1
PING 10.0.1.1 (10.0.1.1) 56(84) bytes of data.
64 bytes from 10.0.1.1: icmp_seq=1 ttl=64 time=0.554 ms
64 bytes from 10.0.1.1: icmp_seq=2 ttl=64 time=0.490 ms
64 bytes from 10.0.1.1: icmp_seq=3 ttl=64 time=0.494 ms
64 bytes from 10.0.1.1: icmp_seq=4 ttl=64 time=0.524 ms
64 bytes from 10.0.1.1: icmp_seq=5 ttl=64 time=0.473 ms
64 bytes from 10.0.1.1: icmp_seq=6 ttl=64 time=0.471 ms


HUH?

You have two VMs, each with their own LAN IP?

Why is PMS on a “non-standard” port on the host (or guest)?

If each VM GUEST has a separate LAN IP then they can be at the default ports.

I have multiple LXCs on the same host at different IP addresses on my LAN.
That’s all that matters.

Everything works perfectly.

Plex was having issues with remote access so ended up setting it up based on this support article…

https://support.plex.tv/articles/200931138-troubleshooting-remote-access/#:~:text=Manual%20Port%20Forwards%20for%20Multiple%20Servers&text=Choose%20a%20different%20unique%20port,ports%2032401%2C%2032402%2C%20etc.

Manual Port Forwards for Multiple Servers

If you have more than one Plex Media Server to connect on your local network, you can set up Remote Access for all of them. Things work basically exactly as outlined above, except that you will need to choose a unique external port number for each server. To do this:

  • Choose a different unique port number for each of your Plex Media Servers
  • Remember, you must use a different WAN/external port for each server connection you want to have here. For instance, you could use ports 32401, 32402, etc.
  • Forward that unique external port number to LAN/internal port 32400 for the local IP address of the corresponding computer running that Plex Media Server – follow the previous instructions

For example, imagine you have two computers running Plex Media Servers and their internal IP addresses are “192.168.1.11” and “192.168.1.22”. In that situation, you might set up forwards such as:

Server 1
IP Address: 192.168.1.11
WAN/External Port: 32401
LAN/Internal Port: 32400

Server 2
IP Address: 192.168.1.22
WAN/External Port: 32402
LAN/Internal Port: 32400

@triks_melb

Gateway: 000.233.1.44

???

Not a valid IP address

LAN IP addresses are 100% safe to post as they are not routed across the internet (per RFC)

masked it - its my public gateway address (ISP) just to be on the safe side but fair point.

Future reference:

Non-routed (RFC-1918 compliant) LAN addresses are:

10.x.x.x
192.168.x.x
172.16.x.x → 172.31.x.x

I can safely tell you I have servers at 192.168.0.13, 192.168.0.20, 192.168.0.21, 192.168.0.70, and 192.168.0.71 (in addition to any other temporaries I spin up)

There’s no router anywhere on the internet which will forward these addresses
— outside my network
— to my network.

That’s what RFC-1918 “Private Network” gives us.

thats good info for the newbs but as mentioned earlier I de-identified a public IP not LAN. I think we are getting a bit of topic though, I was hoping there might be some explanation for the initial errors in the logs especially the Critical entry?

If the logs don’t reveal anything obvious to you, I guess we just call it some sort of temporary network issue and keep monitoring logs?

@triks_melb

check your PM please

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.