Plex not working via custom domain

[Chroniclefonzie]

Server Version#: 1.40.2.8395
Player Version#:
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
I am attempting to access Plex using my domain and Kemp load balancer as the load balancer. However, when I try to access it via my SSL-enabled domain, Plex gets stuck on the login screen. Can you help me with this issue?

[ChuckPa]

Do you have the server’s DEBUG logs ZIP file which captures this?

[Chroniclefonzie]

Plex Media Server Logs_2024-04-22_03-48-51.zip (446.7 KB)

Let me know if you need something else.

[ChuckPa]

Thanks for the logs.

I found it .

Your certificate was not accepted by PMS (which loads when PMS starts)

Cerficates cannot be self-signed certificates.
P12 files must contain the your CRT and KEY, plus the CA (from the issuer)

Apr 22, 2024 01:46:34.113 [139996737366840] ERROR - [CERT] Found a user-provided certificate, but couldn't install it.
Apr 22, 2024 01:46:34.113 [139996737366840] WARN - [CERT] MyPlex: Invalid connection URL 'plex.chroniclefonzie.com'.

While you’re making changes, Given your LAN is IPv4, you can turn off IPv6 support in Settings - Server - Network. Mixing modes complicates TLS use.

[Chroniclefonzie]

Could you walk me thought how to setup it properly? I have a wildcard certs from CloudFlare? I’m using via Kemp LoadMaster and loadBalencing it to my local servers.

[ChuckPa]

First, Your Loadmaster / balancer are for you to resolve manage.

Using certs an advanced topic and should already be known to you.

This is how I generate my P12. The ACME cert is managed by my pfSense.

#!/bin/sh

# Get current cert & key

scp admin@pfsense:/conf/acme/MYDOMAIN.TLD-production.key  ./MYDOMAIN.TLD-production.key

scp admin@pfsense:/conf/acme/MYDOMAIN.TLD-production.crt  ./MYDOMAIN.TLD-production.crt

openssl pkcs12 -export -out MYDOMAIN.TLD.p12 -inkey MYDOMAIN.TLD-production.key -in MYDOMAIN.TLD-production.crt -certfile "Acmecert_+O=Let's+Encrypt,+CN=R3,+C=US.crt"