Server Version#: 1.24.5.5173-8dcc73a59 Player Version#: app.plex.tv 4.68.0 on Firefox After doing cleanup (removed cache from agents and ended up also removing Preferences.xml) I have a lot of logs stating that I’ have thw wrong SNI name as follows: Oct 27, 2021 13:28:54.146 [0x7ff0255deb38] WARN…

Wait. This gave me another clue! LOOK WHO I FOUND DOING THE NASTY: lsof -ni TCP:32400 | grep -v "Plex" COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python3 6158 tautulli 7u IPv4 5617496 0t0 TCP 192.168.1.9:49890->192.168.1.9:32400 (ESTABLISHED) python3 6158 taut…

Thank you @ChuckPa but that didn’t work neither. I have the new cert on the Cache but the error persists. I guess at this point I will nuke the server completely, remove all traces of previous installations, logs and re-install everything from scratch so I can rebuild all the libraries from 0 over …

@mave007 I’m afraid that’s all you can do at this point unless you want to start swapping in the com.plexapp.plugins.library.db backups in hopes of getting one not damaged. If you want to keep “Preferences.xml” then switch it back in after you’ve restarted, you can preserve the server’s identity…

Hi @ChuckPa an update here. I removed the whole plexmediaserver installation in my Ubuntu 18 this way: cp '/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Preferences.xml' /opt apt remove plexmediaserver apt clean rm -rf /var/lib/plexmediaserver/* rm -rf /usr/lib/plexmediase…

You MUST have DNS rebinding protection blocking in your modem/router. That’s the only explanation. Can you create an exception rule (most modem/routers allow it) to allow *.plex.direct On pfSense, I allow private-network: *.plex.direct

When you say router, you mean the DNS resolver on my network, right? I use unbound, on the same server, so I just added the following: cat /etc/unbound/unbound.conf.d/dns-rebinding.conf server: private-domain: "plex.direct" service unbound restart So if I do the following: dig 192-168-1-9.d7…

Is this the expected response? curl -k -v https://192-168-1-9.d7ede18c3ab140f1964a21e4966c632c.plex.direct:32400/identity * Trying 192.168.1.9... * TCP_NODELAY set * Connected to 192-168-1-9.d7ede18c3ab140f1964a21e4966c632c.plex.direct (192.168.1.9) port 32400 (#0) * ALPN, offering h2 * ALPN, off…

I think that’s right. I’ve honestly not done the deep dive into DNS rebinding mitigation. My pfSense, which also uses unbound, is set as follows: [Screenshot from 2021-10-29 13-25-19]

I did the same curl command with the outside ip address and it worked! this is so weird :-S Why my server is locally having issues with the cert (from connections source generated from the same machine) and not from the outside?

default adapter? you KNOW it’s going to be something stupid

Changed the Interface from ANY to the specific eth0. After some deep lsof and tcpdump I think I found the source of the system creating the query for this thing: /usr/lib/plexmediaserver/Plex Tuner Service Can I turn off that?

SSL Cert Warning with wrong SNI name

Plex Media Server

mave007 October 29, 2021, 6:14pm 18

argh, no way to disable that cleanly. I think i’m going this way:

Topic		Replies	Views
Secure connection not working after moving server to new, and reverted back Plex Media Server server-linux , server-freebsd	40	576	April 6, 2021
Documentation around the WARN CERT TLS errors, plex.direct SNI, DNS overlay, etc...? Plex Media Server server-synology	5	353	October 24, 2022
CERT: incomplete TLS handshake from 192.168.xx.xx:25738: sslv3 alert certificate expired Remote Access server-linux	20	615	September 3, 2022
SSL Certificate Errors Plex Media Server server-linux , networking	1398	23830	October 20, 2023
Cert does not match - DNS error Plex Media Server server-synology	21	139	November 2, 2022

SSL Cert Warning with wrong SNI name

Related topics