After PLEX team without announcement changed drastically security issues they intentionally concealed the fact that they switched from TLS1.0 to 1.2.
Finding out that even if you have installed “kb3140245” on your windows 7 system, you need to manually enable it in the registry. Here is the registry data
Just to be clear this fix is for using full security, you can re-enable security in plex server back.
Beside this if you cant get the video with this fix, there is the problem with plex certificates.
I will explain in other thread the way with DynDNS and ZeroSSL
You are re-enabling TLS v1.0 and then you are speaking about “full security”?!
TLS v1.0 is considered “hacked”/“compromised”.
This was the reason why it was disabled.
If you want security, you should never enable and/or use TLS v1.0.
Its quite opposite to what you said.
Just updating TLS1.1 and 1.2 is just to place 4 files on 64bit system. Webio.dll, Winhttp.dll, Webio.dll, Winhttp.dll
But TLS1.2 isn’t enabled in registry.
I gave registry keys to enable it.
For years mods and devs are literally in war with Plex users, lets bridge the gap. Please start to work for your users they are paying to you.
Enable TLS 1.1 and 1.2 on Windows 7 at the SChannel component level
Per the TLS-SSL Settings article, for TLS 1.1 and 1.2 to be enabled and negotiated on Windows 7, you MUST create the “DisabledByDefault” entry in the appropriate subkey (Client) and set it to “0”. These subkeys will not be created in the registry since these protocols are disabled by default.
Create the necessary subkeys for TLS 1.1 and 1.2; create the DisabledByDefault DWORD values and set it to 0 in the following locations:
Plex ended TLS 1.0 at may 26-27 2021 and not in year 2016!!!
For months people asked for help to know whats happening and neither one of you entered into the topics to tell us its just because of TLS.
You wanted that we don’t use older androids, older IOS, older systems like win7-win8. I just rooted Lollipop and added tls 1.2 and its working again.