Seems like I am really facing another problem. My history proves that my sister was remotly watching on 28.9 and nothing changed beside the Lets Encrypt Root expiration. I allready recreated all my certs. My android app seems to connect properly but its not able to play any files. The same thing works flawlessly when using chrome on the same phone.
I use an up to date Pixel 4A. The thing that unsettles me is that the tautulli App complains about my Lets Encrypt certificate,
I removed all known devices and rejoined them but the android problem persists. My reverse proxy doesn’t show any problem either. Shall I open a new thread for my specific problem?
You probably need to sign tautulli out and back into the server so it can get fresh cert cached as well with the token.
TO ALL:
Please be advised –
There appears to be a global outage at FaceBook.
Any users who are using Federated Authentication through their FaceBook account will be impacted and may not be able to sign in.
1 Like
I did that but even after recreating my letsencrypt certs and resetting the app it told me that the cert is not trusted. I will open a new thread and share my PMS and Android Logs.
I have to admit that I don’t see SSL Errors anywhere but I actually I don’t see any exceptions at all which could (in my opinion) lead to this behaviour.
Thx for your support and have a good night
Doemer
can you help me? plz~~~ i don’t know why so many error log…my server account is MODERATOR REDACTED
Oct 06, 2021 02:58:37.317 [0x7f0ace08db38] 警告 — Caught exception trying to convert extra data attribute 'originallyAvailableAt' with type 1 and value '2021-08-31' ~ bad lexical cast: source type value could not be interpreted as target
Oct 06, 2021 02:58:55.637 [0x7f0ad18c7b38] 警告 — [CERT] TLS connection from 203.204.253.51:47750 came in with unrecognized plex.direct SNI name '111-249-254-220.cc67e579fc7542a8bf6a42f9cad529a8.plex.direct'; using installed plex.direct cert
Oct 06, 2021 02:58:57.989 [0x7f0acb952b38] 警告 — Caught exception trying to convert extra data attribute 'originallyAvailableAt' with type 1 and value '2021-08-31' ~ bad lexical cast: source type value could not be interpreted as target
Oct 06, 2021 02:59:17.971 [0x7f0ace08db38] 警告 — Caught exception trying to convert extra data attribute 'originallyAvailableAt' with type 1 and value '2021-08-31' ~ bad lexical cast: source type value could not be interpreted as target
Oct 06, 2021 02:59:24.640 [0x7f0acb952b38] 警告 — QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.641 [0x7f0acb952b38] 警告 — QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.679 [0x7f0acbf70b38] 警告 — QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.679 [0x7f0acbf70b38] 警告 — QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.707 [0x7f0acb873b38] 警告 — QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.707 [0x7f0acb873b38] 警告 — QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.721 [0x7f0acb873b38] 警告 — QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.721 [0x7f0acb873b38] 警告 — QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.779 [0x7f0acb850b38] 警告 — QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.779 [0x7f0acb850b38] 警告 — QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.783 [0x7f0acb850b38] 警告 — QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.783 [0x7f0acb850b38] 警告 — QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.809 [0x7f0acbf08b38] 警告 — QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.809 [0x7f0acbf08b38] 警告 — QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 06, 2021 03:00:12.187 [0x7f0ad18eab38] 警告 — [CERT] TLS connection from 114.32.20.139:34602 came in with unrecognized plex.direct SNI name '111-249-254-220.cc67e579fc7542a8bf6a42f9cad529a8.plex.direct'; using installed plex.direct cert1 and value '2021-08-31' ~ bad lexical cast: source type value could not be interpreted as target
can you help me plz~i don’t know why so many error log and my plex media server crash stop working 2-3 times every hours …i going to crazy…plz help me
Oct 06, 2021 02:58:37.317 [0x7f0ace08db38] 警告 — Caught exception trying to convert extra data attribute 'originallyAvailableAt' with type 1 and value '2021-08-31' ~ bad lexical cast: source type value could not be interpreted as target
Oct 06, 2021 02:58:55.637 [0x7f0ad18c7b38] 警告 — [CERT] TLS connection from 203.204.253.51:47750 came in with unrecognized plex.direct SNI name '111-249-254-220.cc67e579fc7542a8bf6a42f9cad529a8.plex.direct'; using installed plex.direct cert
Oct 06, 2021 02:58:57.989 [0x7f0acb952b38] 警告 — Caught exception trying to convert extra data attribute 'originallyAvailableAt' with type 1 and value '2021-08-31' ~ bad lexical cast: source type value could not be interpreted as target
Oct 06, 2021 02:59:17.971 [0x7f0ace08db38] 警告 — Caught exception trying to convert extra data attribute 'originallyAvailableAt' with type 1 and value '2021-08-31' ~ bad lexical cast: source type value could not be interpreted as target
Oct 06, 2021 02:59:24.640 [0x7f0acb952b38] 警告 — QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.641 [0x7f0acb952b38] 警告 — QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.679 [0x7f0acbf70b38] 警告 — QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.679 [0x7f0acbf70b38] 警告 — QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.707 [0x7f0acb873b38] 警告 — QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.707 [0x7f0acb873b38] 警告 — QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.721 [0x7f0acb873b38] 警告 — QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.721 [0x7f0acb873b38] 警告 — QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.779 [0x7f0acb850b38] 警告 — QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.779 [0x7f0acb850b38] 警告 — QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.783 [0x7f0acb850b38] 警告 — QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.783 [0x7f0acb850b38] 警告 — QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.809 [0x7f0acbf08b38] 警告 — QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 06, 2021 02:59:24.809 [0x7f0acbf08b38] 警告 — QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 06, 2021 03:00:12.187 [0x7f0ad18eab38] 警告 — [CERT] TLS connection from 114.32.20.139:34602 came in with unrecognized plex.direct SNI name '111-249-254-220.cc67e579fc7542a8bf6a42f9cad529a8.plex.direct'; using installed plex.direct cert
Oct 06, 2021 03:00:46.950 [0x7f0ad0dd3b38] 錯誤 — XML: Entity: line 1:
Oct 06, 2021 03:00:46.950 [0x7f0ad0dd3b38] 錯誤 — XML: parser
Oct 06, 2021 03:00:46.950 [0x7f0ad0dd3b38] 錯誤 — XML: error :
Oct 06, 2021 03:00:46.950 [0x7f0ad0dd3b38] 錯誤 — XML: Start tag expected, '<' not found
Oct 06, 2021 03:00:46.950 [0x7f0ad0dd3b38] 錯誤 — XML: status=ok
Oct 06, 2021 03:00:46.950 [0x7f0ad0dd3b38] 錯誤 — XML: ^
Oct 06, 2021 03:00:46.950 [0x7f0ad0dd3b38] 錯誤 — Error parsing content.
Oct 06, 2021 03:00:46.950 [0x7f0ad0dd3b38] 錯誤 — Error parsing XML: Error parsing file.
Oct 06, 2021 03:00:46.950 [0x7f0ad0dd3b38] 錯誤 — SSDP: Error parsing device schema for http://192.168.1.207:9080
Oct 06, 2021 03:00:55.781 [0x7f0ad18c7b38] 警告 — [CERT] TLS connection from 203.204.253.51:47752 came in with unrecognized plex.direct SNI name '111-249-254-220.cc67e579fc7542a8bf6a42f9cad529a8.plex.direct'; using installed plex.direct cert
Oct 06, 2021 03:01:17.038 [0x7f0ad0dd3b38] 錯誤 — XML: Entity: line 1:
Oct 06, 2021 03:01:17.038 [0x7f0ad0dd3b38] 錯誤 — XML: parser
Oct 06, 2021 03:01:17.038 [0x7f0ad0dd3b38] 錯誤 — XML: error :
Oct 06, 2021 03:01:17.038 [0x7f0ad0dd3b38] 錯誤 — XML: Start tag expected, '<' not found
Oct 06, 2021 03:01:17.038 [0x7f0ad0dd3b38] 錯誤 — XML: status=ok
Oct 06, 2021 03:01:17.038 [0x7f0ad0dd3b38] 錯誤 — XML: ^
Oct 06, 2021 03:01:17.038 [0x7f0ad0dd3b38] 錯誤 — Error parsing content.
Oct 06, 2021 03:01:17.039 [0x7f0ad0dd3b38] 錯誤 — Error parsing XML: Error parsing file.
Oct 06, 2021 03:01:17.039 [0x7f0ad0dd3b38] 錯誤 — SSDP: Error parsing device schema for http://192.168.1.207:9080
Oct 06, 2021 03:01:47.152 [0x7f0ad0dd3b38] 錯誤 — XML: Entity: line 1:
Oct 06, 2021 03:01:47.152 [0x7f0ad0dd3b38] 錯誤 — XML: parser
Oct 06, 2021 03:01:47.152 [0x7f0ad0dd3b38] 錯誤 — XML: error :
Oct 06, 2021 03:01:47.152 [0x7f0ad0dd3b38] 錯誤 — XML: Start tag expected, '<' not found
Oct 06, 2021 03:01:47.152 [0x7f0ad0dd3b38] 錯誤 — XML: status=ok
Oct 06, 2021 03:01:47.152 [0x7f0ad0dd3b38] 錯誤 — XML: ^
Oct 06, 2021 03:01:47.152 [0x7f0ad0dd3b38] 錯誤 — Error parsing content.
Oct 06, 2021 03:01:47.152 [0x7f0ad0dd3b38] 錯誤 — Error parsing XML: Error parsing file.
Oct 06, 2021 03:01:47.152 [0x7f0ad0dd3b38] 錯誤 — SSDP: Error parsing device schema for http://192.168.1.207:9080
Oct 06, 2021 03:02:12.371 [0x7f0ad18c7b38] 警告 — [CERT] TLS connection from 114.32.20.139:34606 came in with unrecognized plex.direct SNI name '111-249-254-220.cc67e579fc7542a8bf6a42f9cad529a8.plex.direct'; using installed plex.direct cert
Oct 06, 2021 03:02:55.917 [0x7f0ad18c7b38] 警告 — [CERT] TLS connection from 203.204.253.51:47770 came in with unrecognized plex.direct SNI name '111-249-254-220.cc67e579fc7542a8bf6a42f9cad529a8.plex.direct'; using installed plex.direct cert
Oct 06, 2021 03:03:19.070 [0x7f0ad18c7b38] 警告 — [CERT] TLS connection from 218.166.31.148:47080 came in with unrecognized plex.direct SNI name '111-249-254-220.cc67e579fc7542a8bf6a42f9cad529a8.plex.direct'; using installed plex.direct cert
here is my log~plz help me
Plex Media Server Logs_2021-10-05_23-31-16.zip (514.6 KB)
Plex Media Server Logs_2021-10-06_03-20-14.zip (637.9 KB)
MODERATOR EDIT: Formatting
I have removed your email address above. I can see your account details without it.
I have reformatted your post for readability
I have reset your certificate. It was not necessary to delete the server.
You might be able to recover by restarting it now.
thank you so much!!! thank you*100000000000
Seeing similar cert alerts in logs, unable to stream from some devices and don’t know how to check if my cert was pre sept 30th
2203 Oct 05, 2021 23:33:06.232 [0x7fecdc4e6b38] DEBUG - CERT: incomplete TLS handshake from [::ffff:2.216.194.35]:46254: sslv3 alert certificate expired
2204 Oct 05, 2021 23:33:36.217 [0x7fecdc4c3b38] DEBUG - CERT: incomplete TLS handshake from [::ffff:2.216.194.35]:46256: sslv3 alert certificate expired
@ChuckPa can you restart my cert too pls. Thank you…
I still have a problem with remote access.I have the router well set up
I have reset your certificates.
You may restart your servers.
Please forgive the delay — “One of those days”
Hey I thought I was going crazy. I’ve also started getting complaints from family and friends in the last week or so. From the logs I can see:
Oct 06, 2021 13:46:26.560 [0x7fa8ff326b38] DEBUG - CERT: incomplete TLS handshake from xxx.151.215.176:53226: sslv3 alert certificate expired
Is the problem on their end or on my servers end? Do I also need a cert reset?
Thanks
Seeing cert errors when trying to cast to ‘plex-mpv-shim’
Oct 06, 2021 10:53:32.086 [13648] Debug — CERT: incomplete TLS handshake from [::ffff:192.168.0.14]:58833: sslv3 alert certificate expired
Just wanted to let you know that I sorted out my Android Cert Trust problems. My reverse proxy was still using the old cross signed R3 Intermediate 
. I don’t understand completly, why my Plex App was able to let me browse my stuff at all but it doesn’t matter. Glad its working again.
Regards,
Dom
Your certificate has been reset. Restart your server
Your certificate was created on Wed, 06 Oct 2021 09:17:16 +0000
All the devices on your account appear newly created as of 06-Oct.
Are you using a proxy ?
@ChuckPa
No proxy, I removed all devices and re-added them after the issues.
I’m trying to cast to plex-mpv-shim from the same PC the server is installed on but I get the “Playback Error: An error occurred trying to play this item.” Message and when I checked the console, I got “CERT: incomplete TLS handshake from [::ffff:192.168.0.14]:62081: sslv3 alert certificate expired” and plex-mpv-shim is not adding itself to authorised devices like it did the first time after connection.
Since that’s third party GitHub - iwalton3/plex-mpv-shim: Cast media from Plex Mobile and Web apps to MPV. (Unofficial) I need to refer you to them to answer this.
I have no knowledge of this software
If they have a certificate in it, then they probably need to update their certificate in the client
Hi, could you please reset my certificate too? Thanks!
Your certificate is current.
Valid Wed, 06 Oct 2021 09:41:59 +0000 Wed, 06 Oct 2021 09:42:10 +0000
What is the issue?
Good evening, I’m getting the same issue! May I please have my cert reset? If it’s already reset, please find the log attached to this post.log.txt (3.6 KB)
If it helps, I’m using a WD My Cloud as the Plex server.
