Plex refuses to recognize local client as local; transcodes for clients that can play direct

Plex Media Server Desktops & Laptops
1

Plex server 1.16.6.1592 on CentOS 7.

Web client on desktop Chrome and Firefox.
Server and client are in the same local subnet, which is added as a “LAN network”.

When the client accesses the server through app.plex.tv, the connection is “indirect” and all content is transcoded. My connection is fast enough to do direct play over the internet.

When the client access by https://server-ip:32400, the connection shows as “Nearby” and direct play is available.

So, I have two questions:

  1. Why is the web client convinced the server is “indirect” when they’re in the same subnet?
  2. How do I avoid transcoding for clients that can play direct over the internet?
2
  1. What LAN IP addresses are involved? Are they RFC 1918 compliant?
  2. App.plex.tv will fail to “switch over” if DNS rebinding protection is active and blocks Private Domain plex.direct .

DEBUG logs (DEBUG on, VERBOSE off) captured immediate after recreating the problems (play a few seconds only is all that’s needed)

After stopping all playback,

Settings - Server - Troubleshooting - Download Logs.
Attach the ZIP

3

  1. The LAN subnet is 10.16.0.0/24; in the RFC1918 Class ‘A’ block.

  2. The output is too long to post, it exceeds the 40k char limit.

Plex Media Server Logs_2019-09-23_01-06-43.zip (1.6 MB)
[/details]

4

Thank you for attaching the log ZIP as I had requested. I know the forum would not accommodate what was needed.

From your logs:

Sep 22, 2019 19:56:39.048 [0x7f7aff7fe700] ERROR - getaddrinfo(10-16-0-69.abcdefghijklmnopqrstuvwxyz012345.plex.direct) failed: -2

DNS rebinding protection is blocking the detection

Sep 22, 2019 19:56:39.035 [0x7f7a77fff700] DEBUG - HTTP requesting GET https://67-176-122-120.9cbbd6209ae24d20a58fdf95abc68277.plex.direct:26495/security/token?type=delegation&scope=all&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Sep 22, 2019 19:56:39.047 [0x7f7aff7fe700] DEBUG - EventSource: Read HTTP reply header.
Sep 22, 2019 19:56:39.047 [0x7f7aff7fe700] DEBUG - MyPlex: We appear to have regained Internet connectivity.
Sep 22, 2019 19:56:39.048 [0x7f7aff7fe700] ERROR - getaddrinfo(10-16-0-69.abcdefghijklmnopqrstuvwxyz012345.plex.direct) failed: -2
Sep 22, 2019 19:56:39.048 [0x7f7aff7fe700] DEBUG - Network: 10-16-0-69.abcdefghijklmnopqrstuvwxyz012345.plex.direct failed to resolve to 10.16.0.69 but instead yielded ""

Your choices are:

  1. Turn off DNS Rebinding Protection (not ideal)
  2. Create an exception / Declare the Private Domain plex.direct in your DNS resolver.

Declaring a private domain exemption on pfSense is

server:
private-domain: "plex.direct"

Additionally, if the server computer is running any kind of firewall, verify the following ports are open as defined here:

https://support.plex.tv/articles/201543147-what-network-ports-do-i-need-to-allow-through-my-firewall/

5

There is a firewall rule to allow Plex traffic.
As it turns out, I am on pfSense, I’ll set that exemption and try again.

6

Add it to the DNS Resolver.

7

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