SSL Cert Warning with wrong SNI name

Plex Media Server
,
22

The source of the SNI error is the Plex Tuner Service?

For a moment, I thought it was, but no, it’s still generating connections from the Plex Media Server

23

The connections are FROM pms or TO pms?

24

The connections are FROM pms or TO pms?

Yes!

Originated from the internal IP address and directed to the same IP address.

25

Can you show me ?

PMS should always use http://127.0.0.1

It should never use the LAN / WAN IP.

We need to find the task(s) launched just before it occurs so we can jump down into the task stack and see which thread is executing (the server has some 50 internal threads)

26

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 tautulli   13u  IPv4 5620396      0t0  TCP 192.168.1.9:49868->192.168.1.9:32400 (ESTABLISHED)
python3    6158 tautulli   16u  IPv4 5620430      0t0  TCP 192.168.1.9:49884->192.168.1.9:32400 (ESTABLISHED)
python3    6158 tautulli   17u  IPv4 5621744      0t0  TCP 192.168.1.9:49886->192.168.1.9:32400 (ESTABLISHED)

So, I went to tautulli, and noticed the credentials were no longer valid! I guess that happened after I did the cleanup of the Cache.

So, went to fix that and now SNI cert name errors no more.

Once again, thank you so much for your input and time. I owe you at least a few beers.
This is now resolved.

1 Like
27

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