SSL Certificate Errors

ChuckPa · July 21, 2023, 5:23pm

Plex.tv is telling your host to BE QUIET (sound familiar? lol)

Jul 21, 2023 18:42:50.238 [22728981162808] DEBUG - [HCl#26] HTTP requesting POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx
Jul 21, 2023 18:42:50.312 [22728996285240] DEBUG - [HttpClient/HCl#26] HTTP/2.0 (0.1s) 422 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx (reused)
Jul 21, 2023 18:42:50.312 [22728981162808] DEBUG - MyPlex: Published Mapping State response was 422
Jul 21, 2023 18:42:50.312 [22728981162808] DEBUG - MyPlex: Got response for 1c04f21c6dcda803a5377a935bbdbf0bbbcb1aae ~ registered :0
Jul 21, 2023 18:42:50.312 [22728981162808] DEBUG - MyPlex: updating mapped state - current state: 'Mapped - Not Published'
Jul 21, 2023 18:42:50.312 [22728981162808] DEBUG - MyPlex: mapping state set to 'Mapped - Publishing'.

If you did a lot of stop/start/stop/start then that can happen.
Also. creating new hosts will do it as well (even when you clean up after yourself)

I can reset the certificate but, in actuality, I’m resetting the whole server.

To do this,

Please stop the server
Let me know which one and I’ll do the full reset (You have two listed)
You can then start it.

TomArne · July 21, 2023, 5:31pm

haha Yes I have done e few restarts today…
Does this mean I have to add all the media all over again?

If you have the possibility, you can delete the old “Arnes Plex”

I am only using the one named “Arne’s “nye :(” Plex”
This has happened before, and then I started a new server

ChuckPa · July 21, 2023, 5:38pm

@TomArne

The servers I see are:

Arne’s “nye :(” Plex
-and-
Tower

Does this make sense?

NO – you will not have to add media again UNLESS you completely erased the APPLICATION_SUPPORT_DIR (DB storage)

TomArne · July 21, 2023, 5:42pm

Ahh…

Tower is my Unraid Server.
Then I guess it’s the Arne’s “nye :(” Plex you have to reset.

Nope. I did nothing but try to reinstall the binhex plex docker when the update wouldn’t let me in.

ChuckPa · July 21, 2023, 5:54pm

Please shutdown the PMS server.
I will remove ‘Tower’ if you want – However, that might be an indicator to what’s going wrong.

Let me know when you want me to reset “Nye”

TomArne · July 21, 2023, 5:58pm

The PMS docker is stopped.
Yes, please remove the Tower. I probably messed with things I don’t know how to, the last time this happened

You can now do the reset of “Nye”

ChuckPa · July 21, 2023, 8:11pm

@TomArne

Sorry for delay.

Host NYE has been reset.

You may start it.

Give it a minute to generate and grab the new cert BEFORE opening it.

TomArne · July 22, 2023, 9:32am

Thank you so much for your help. But it didn’t work
The server always installs as Tower…
I had to upload the library databases to a new install.
Renamed the new one, and deleted previous servers.
It’s now up and running again

ChuckPa · July 22, 2023, 3:45pm

@TomArne

Problem existed between keyboard and chair?

gripfly · July 22, 2023, 8:26pm

Hi, I also have issues with the certificate, mind to help me with it?

Jul 22, 2023 20:25:21.441 [139691405191992] Warning — [CERT] TLS connection from 192.168.1.1:57284 came in with unrecognized plex.direct SNI name 'IP.0d350e47459f4759bac2575fee923149.plex.direct'; using installed plex.direct cert
Jul 22, 2023 20:25:25.976 [139691403082552] Warning — [CERT] TLS connection from 192.168.1.1:57292 came in with unrecognized plex.direct SNI name 'IP.0d350e47459f4759bac2575fee923149.plex.direct'; using installed plex.direct cert
Jul 22, 2023 20:25:26.009 [139691403082552] Warning — [CERT] TLS connection from 192.168.1.1:57294 came in with unrecognized plex.direct SNI name 'IP.0d350e47459f4759bac2575fee923149.plex.direct'; using installed plex.direct cert
Jul 22, 2023 20:25:26.012 [139691405191992] Debug — CERT: incomplete TLS handshake from 192.168.1.1:57294: sslv3 alert bad certificate (SSL routines)
Jul 22, 2023 20:25:31.444 [139691403082552] Warning — [CERT] TLS connection from 192.168.1.1:40080 came in with unrecognized plex.direct SNI name 'IP.0d350e47459f4759bac2575fee923149.plex.direct'; using installed plex.direct cert

ChuckPa · July 22, 2023, 9:07pm

This is the Certificate ID from the old server before you recreated it yesterday.

Did you completely terminate and restart the player ?
PMS is reporting that it’s getting a certificate it’s not expecting (which we now know is the old server – pre recreation)

gripfly · July 22, 2023, 9:34pm

There was actually no player running at that moment (at least not visible on the dashboard) when I posted the logs.

Not sure if the recreating is a problem. I had issues that I could not mount /dev/shm in the snap version, so I stopped the snap and installed the package through apt (on the same vm)

I’m also seeing the following which rather confuses me, as it’s an AP and on my home network no device is currently playing:

Jul 22, 2023 21:33:16.627 [139691323542328] Debug — [NSB/SSDP] Parsing SSDP schema for http://192.168.1.250:8200/rootDesc.xml
Jul 22, 2023 21:33:16.633 [139691372350264] Warning — [HttpClient/HCl#13e] HTTP error requesting GET http://192.168.1.250:8200/rootDesc.xml (56, Failure when receiving data from the peer) (Recv failure: Connection reset by peer)

ChuckPa · July 22, 2023, 9:53pm

I’m sorry, I need more than 2 line snippets.

NSB / SSDP — Network Service Browser / Simple Service Discovery Protocol.
It’s looking and finding things.

You’re not giving me enough to know what’s happening.

(Looking at a toothache through a microscope isn’t productive … lol)

gripfly · July 22, 2023, 10:02pm

Don’t worry, I’m grateful that you respond quite quick

So this here repeats itself currently (just a couple minutes after my first comment here someone actually started watching something remotely):

Jul 22, 2023 21:53:34.383 [139691403082552] Warning — [CERT] TLS connection from 192.168.1.1:45676 came in with unrecognized plex.direct SNI name 'IP.0d350e47459f4759bac2575fee923149.plex.direct'; using installed plex.direct cert
Jul 22, 2023 21:53:38.633 [139691405191992] Warning — [CERT] TLS connection from 192.168.1.1:55922 came in with unrecognized plex.direct SNI name 'IP.0d350e47459f4759bac2575fee923149.plex.direct'; using installed plex.direct cert
Jul 22, 2023 21:53:38.667 [139691403082552] Warning — [CERT] TLS connection from 192.168.1.1:55932 came in with unrecognized plex.direct SNI name 'IP.0d350e47459f4759bac2575fee923149.plex.direct'; using installed plex.direct cert
Jul 22, 2023 21:53:38.670 [139691405191992] Debug — CERT: incomplete TLS handshake from 192.168.1.1:55932: sslv3 alert bad certificate (SSL routines)
Jul 22, 2023 21:53:44.381 [139691403082552] Warning — [CERT] TLS connection from 192.168.1.1:55934 came in with unrecognized plex.direct SNI name 'IP.0d350e47459f4759bac2575fee923149.plex.direct'; using installed plex.direct cert
Jul 22, 2023 21:53:46.733 [139691323542328] Debug — [NSB/SSDP] Parsing SSDP schema for http://192.168.1.250:8200/rootDesc.xml
Jul 22, 2023 21:53:46.739 [139691372350264] Warning — [HttpClient/HCl#16f] HTTP error requesting GET http://192.168.1.250:8200/rootDesc.xml (56, Failure when receiving data from the peer) (Recv failure: Connection reset by peer)
Jul 22, 2023 21:53:54.386 [139691403082552] Warning — [CERT] TLS connection from 192.168.1.1:44806 came in with unrecognized plex.direct SNI name 'IP.0d350e47459f4759bac2575fee923149.plex.direct'; using installed plex.direct cert
Jul 22, 2023 21:54:04.387 [139691405191992] Warning — [CERT] TLS connection from 192.168.1.1:36848 came in with unrecognized plex.direct SNI name 'IP.0d350e47459f4759bac2575fee923149.plex.direct'; using installed plex.direct cert
Jul 22, 2023 21:54:08.704 [139691405191992] Warning — [CERT] TLS connection from 192.168.1.1:47270 came in with unrecognized plex.direct SNI name 'IP.0d350e47459f4759bac2575fee923149.plex.direct'; using installed plex.direct cert
Jul 22, 2023 21:54:08.734 [139691403082552] Warning — [CERT] TLS connection from 192.168.1.1:47278 came in with unrecognized plex.direct SNI name 'IP.0d350e47459f4759bac2575fee923149.plex.direct'; using installed plex.direct cert
Jul 22, 2023 21:54:08.736 [139691405191992] Debug — CERT: incomplete TLS handshake from 192.168.1.1:47278: sslv3 alert bad certificate (SSL routines)
Jul 22, 2023 21:54:14.386 [139691405191992] Warning — [CERT] TLS connection from 192.168.1.1:47284 came in with unrecognized plex.direct SNI name 'IIP.0d350e47459f4759bac2575fee923149.plex.direct'; using installed plex.direct cert
Jul 22, 2023 21:54:16.736 [139691323542328] Debug — [NSB/SSDP] Parsing SSDP schema for http://192.168.1.250:8200/rootDesc.xml
Jul 22, 2023 21:54:16.742 [139691372350264] Warning — [HttpClient/HCl#170] HTTP error requesting GET http://192.168.1.250:8200/rootDesc.xml (56, Failure when receiving data from the peer) (Recv failure: Connection reset by peer)

ChuckPa · July 22, 2023, 10:11pm

Would you do the following please ?

Settings - Server - Troubleshooting (lower left corner) - Download Logs

It will give you a ZIP file

Attach the ZIP here.

(( My concern here is that we might need manual intervention to undo a stuck certificate file ))

gripfly · July 22, 2023, 10:30pm

Had to split it in 2 as iit was just slightly over 8MB

Removed Logs

ChuckPa · July 22, 2023, 11:03pm

thank you.

Your logs confirm:

Plex.tv has

UUID CDB1F210EBC247D280FBEA77A16B

Your server has

Jul 22, 2023 20:11:04.213 [139691412540048] DEBUG - [CERT] Subject name is /CN=*.cdb1f210ebc247d280fbea77a16b.plex.direct

This device is acting like a PMS server but isn’t.

Jul 22, 2023 20:11:19.750 [139691372350264] WARN - [HttpClient/HCl#31] HTTP error requesting GET https://172-17-0-10.0638b75dd51a4ea4bf090887d4d303f5.plex.direct:32400 (7, Couldn't connect to server) (Failed to connect to 172-17-0-10.0638b75dd51a4ea4bf090887d4d303f5.plex.direct port 32400 after 3079 ms: Couldn't connect to server)

It continues to try and use the old server certificate

This device is acting like a network gateway – and failing

Jul 22, 2023 20:14:16.238 [139691372350264] WARN - [HttpClient/HCl#45] HTTP error requesting GET http://192.168.1.250:8200/rootDesc.xml (56, Failure when receiving data from the peer) (Recv failure: Connection reset by peer)

gripfly · July 22, 2023, 11:20pm

Tautulli was actually the issue, oh man… I guess that explains why I could not see a player running in the dashboard.

This device is acting like a network gateway – and failing

Interesting. Will see what I can find out.

Thanks for your support, was very helpful!

system · October 20, 2023, 11:21pm

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

Topic		Replies	Views
Plex Certificate "404" -- Unable to obtain Certificate from cloud Plex Media Server	485	2243	April 22, 2021
Secure connection not working after last update Remote Access server-linux	149	3640	June 7, 2021
Plex Employee to Reset Server Certificate? "API rate limit exceeded" error Desktops & Laptops server-windows	521	8396	November 1, 2023
Some remote access stopped working Remote Access server-linux	392	3701	March 5, 2021
I cannot access my server with a browser but i can with the Plex app Remote Access server-mac , plex-web	278	8192	May 31, 2022

SSL Certificate Errors

Related topics