PMS Version#: 1.25.4.5426 Samsung client: 5.29.1 (platform 4) Last September, I switched my PMS certificate from Let’sEncrypt to ZeroSSL to workaound DST ROOT CA X3 expiration on broken clients. Since then, old TVs were back on track except my Samsung TVs (>2016) when transcoding was required. S…

@ChuckPa I see you are involved in fixing certificate issue in other threads. Do you have an idea of why this certificate issue only happen when transcoding is required?

First. your server certificate (which includes your Plex.direct) is valid. Valid Tue, 28 Dec 2021 08:20:56 +0000 Tue, 28 Dec 2021 08:21:05 +0000 What are you doing with the Custom Server Access URLs? Plex.tv has a very broken entry for you. (Privacy redacted below) PUBLISHED YES (82.XX.XXX.XX…

What are you doing with the Custom Server Access URLs? <?xml version="1.0" encoding="utf-8"?> <Preferences MachineIdentifier="****" ProcessedMachineIdentifier="*****" TranscoderTempDirectory="/var/tmp/plexmediaserver/" OldestPreviousVersion="legacy" AnonymousMachineIdentifier="*****" MetricsEpoch…

@seblu I looked directly at the record Plex.tv has for your server. It listed your URLs and then has ,HTTPS on the end as if you were trying to do something else but did not complete it.

I don’t know the format of the record you have for my server at Plex.tv, so I have no idea where this , HTTPS comes from. I sent you my server Preferences.xml where the network configuration of the Plex Media Server is. Do you see something wrong in it which can lead to this , HTTPS in your record? …

@seblu Where did you send it? I’m looking at my PMs and do not see anything.

In my previous answer from 4:41pm. [image] TLS, unknown player error and *.plex.direct Plex Media Server What are you doing with the Custom Server Access URLs? <?xml version="1.0" encoding="utf-8"?> <Preferences MachineIdentifier="****" ProcessedMachineIdentifier="*****…

@seblu I figured it out You have a FULL URL for the Domain name. You only want domain.tld . This is why Plex.tv is seeing HTTPS. It thinks https://name.domain.tld:32400 is the domain name and parsing it incorrectly. The Custom Access URL is different :wink: I was looking right at it and d…

Oh, I see. I misinterpreted the using your mapped port in the help text. It’s fixed and after server restart the main issue remain. Reminder: Transcoding fail on 2018 Samsung TVs and my current guess is it’s related to the certificate authority provided by plex.direct (i.e https://192-168-242-****.…

[image] seblu: Reminder: Transcoding fail on 2018 Samsung TVs and my current guess is it’s related to the certificate authority provided by plex.direct (i.e https://192-168-242-****.plex.direct:3240) which is expired. LOGs please so I may see the player error ? There are MANY televisions imp…

TLS, unknown player error and *.plex.direct

Plex Media Server

ChuckPa February 16, 2022, 3:49pm 11

LOGs please so I may see the player error ?

There are MANY televisions impacted by the 30-Sept-2021 LE certificate expiration

Topic		Replies	Views
Another Samsung TV Support **Issue! Plex Players smart-tv , samsung-tizen	12	287	July 4, 2022
Absolutely frustrated since ~2 years Plex Media Server server-linux	26	697	August 18, 2021
PMS suddenly shows issues with remote access 9/30/2021 10AM EST Plex Media Server server-linux	188	9167	March 23, 2022
About to Give Up on Plex Plex Media Server server-linux	41	1135	January 30, 2022
SSL Certificate Errors Plex Media Server server-linux , networking	1398	23380	October 20, 2023

TLS, unknown player error and *.plex.direct

Related topics