Can no longer browse to my PMS from local desktop? Must go through Plex.TV

Plex Players Desktop Players
,
1

Server Version#: 1.20.1.3252
Player Version#: 4.43.1

Was forced to upgrade server OS from Ubuntu 16.0.4 to 18.0.4 after the last major PMS update.

Server is a ESXi 6.7 VM, client is a Ubuntu 16.0.4 desktop running Firefox 81.0 (64-bit)

I was previously able to just browse to my local server on 192.168.40.150/24 from my desktop 192.168.10.153/24 to watch movies. I can no longer do that. I have two ROKU’s and a PlayStation 4 on the .10.0/24 network which have no issues. The only way I can access my server is via Plex.tv, and then it works fine. Due to the reduced bandwidth using the relay, I would prefer to access my server locally without traffic leaving my network.

I tried the trick using a private browser and I got a browser time out?

Do Rokus and PS4 go out to the relay for their normal operation or do they try to connect locally initially?

Thanks for your help.

Rob

2

I need the log files please (downloaded ZIP or manual tar.gz of the Logs directory) to help with this.

From what you’re showing me of your networking, you’re trying to cross subnets as if they aren’t there.

Might I suggest a bit of network subnet renumbering -OR- increasing the width of the netmask to make it be one subnet with different numbers for grouping purposes.

If I’m not understanding, would you please let me know and help me understand?

3

Plex Media Server Logs_2020-09-28_23-42-02.zip (7.3 MB)

The subnets are part of a larger network, and traffic between them is not restricted. Renumbering them or changing the mask to make them one large flat network is not possible.

Both networks are identified in the PMS configuration.

4

Do you have port 32400 open & forwarded (or route table entries) to provide a clear path to the server IP?

Relay will only engage if the server isn’t accessible.

The sequence is:

  1. Player wishes to make a play request
  2. Looks to see if on same subnet
  3. If not on same subnet, query Plex.tv for address
  4. Attempt to open that address:port directly.
  5. If not, request relay
  6. Relay starts
  7. Plex.tv handles data brokering

What this implies is:

  1. No clear access (TCP) where the players / other clients can reach the server
  2. Route tables don’t direct traffic ?
  3. Firewall ports not open on server machine?

Did the Ubuntu firewall engage without you knowing it? (it wouldn’t surprise me)

5

Yes, port 32400 is open and forwarded on my firewall. It is wide open between the subnets. The Ubunutu firewall is not installed.

When I used to connect directly to the server, I used the server’s internal address:32400 and had no issues.

6

Local desktop:
enp0s25 Link encap:Ethernet HWaddr 64:31:50:8e:be:ab
inet addr:192.168.10.153 Bcast:192.168.10.255 Mask:255.255.255.0

Ping to PMS:
root@ajaxjones:~$ ping 192.168.40.150
PING 192.168.40.150 (192.168.40.150) 56(84) bytes of data.
64 bytes from 192.168.40.150: icmp_seq=1 ttl=63 time=0.466 ms
64 bytes from 192.168.40.150: icmp_seq=2 ttl=63 time=0.444 ms
64 bytes from 192.168.40.150: icmp_seq=3 ttl=63 time=0.622 ms
64 bytes from 192.168.40.150: icmp_seq=4 ttl=63 time=0.534 ms
64 bytes from 192.168.40.150: icmp_seq=5 ttl=63 time=0.473 ms
64 bytes from 192.168.40.150: icmp_seq=6 ttl=63 time=0.390 ms
^C
— 192.168.40.150 ping statistics —
6 packets transmitted, 6 received, 0% packet loss, time 5096ms
rtt min/avg/max/mdev = 0.390/0.488/0.622/0.074 ms

7

Resolved the problem. It was a misconfiguration on the local desktop. The wrong default route was selected. There are two on this network. Thanks for your help.

8

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