Server Version#: 1.42.1.10060
Player Version#: 4.147.1
I’m running plex in kubernetes and have 100% working remote access, but the remote access checker seems to disagree:
I personally wouldn’t care but I pay for remote access and I’m being throttled because plex wants to route incoming external traffic through a relay.
I’ve already taken a look at the logs, and I see this error when attempting to connect directly:
[HttpClient/HCl#61] HTTP error requesting GET https://xxxx.plex.direct:443/identity (35, SSL connect error) (OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to xxxx.plex.direct:443 )
I have TLS terminating at my load balancer, so I’m curious if it’s causing a conflict with the xxxx.plex.direct fqdn, which does not match the FQDN on the cert that’s pinned to the 443 listener. In addition, I am curious if plex supports local network TLS encryption. Plex reports as “nearby” when accessing it via the IP of the internal LB as expected, but reports as “remote” when accessing it using its internal FQDN.
