Problem getting authentication token

[pfzlsk]

[pfzlsk]

Both my PMS and mt web interface are on the same PC. Any suggestions?

[ukdtom]

What OS and version?

[pfzlsk]

[pfzlsk]

My Plex installation was previously working and stable, but then in early December I started to lose connectivity with the server frequently. I noticed the failed install message and tried to reinstall but then the Claim Server button appeared. I have totally removed PMS using Revo uninstaller to purge all registry entries and delete all remaining files, but with no success. I even dropped back to a previous PMS release 1.23.6.4881

[ukdtom]

It's a Windows issue, where it can't connect to plex.tv using the newer encryption req. by Plex

Make sure, that you are running the latest .Net4 version avail for a start https://dotnet.microsoft.com/en-us/download/dotnet-framework/thank-you/net48-web-installer

And if not working, then you need to troubleshot your windows OS, which is out of scope for ClaimIT

[pfzlsk]

I looked at the registry entry and I am running the .net 4.8 framework I have also tried running the repair tool from Microsoft but that didn't work, and I've kind of exhausted my knowledge set at this point. I appreciate your help and just knowing the general location of the problem is a tremendous help. I know it's beyond the scope of ClaimIT but do you have any suggestions on where I should look next to fix this in the OS? Do you think that a brute force approach of upgrading top Win 11 might work?

[ukdtom]

Sadly no idea, since I'm a Linux dude, so sadly can't help here....

But when said...

Can you using a browser on the box reach https://plex.tv ?

[pfzlsk]

Pops open immediately

[ukdtom]

Darn, then it actually might be my problem ;)

ClaimIt was compiled with .Net4.5

Above .Net version did support TLS1.2, but at that time, it was not yet the standard, and as such, TLS1.1 was used as the default.

Plex no longer supports TLS 1.1 ;)

Stand by here

[ukdtom]

ClaimIt.zip

Does above work?

[pfzlsk]

When I ran it, it flashed some gray text with Password OK in green, then cleared the message box, then after a few seconds went to Not Responding. I did not get an error message.

[pfzlsk]

It did generate a log request to Plex however, as I received a new device login email from them

[ukdtom]

Hmm, and okay....Will look more into this, but sadly 3.20 at night here, so ;)

[pfzlsk]

I may not have let it run long enough. I tried again and got the following, which looks like progress....

[ukdtom]

That is much better, and look here:

https://github.com/ukdtom/ClaimIt/wiki/Errors-and-Troubleshooting#500

And regarding prefs.xml mentioned, it's in the registry for windows

https://support.plex.tv/articles/204281528-why-am-i-locked-out-of-server-settings-and-how-do-i-get-in/

[pfzlsk]

So I checked the wiki and I did not edit preferences as this is a clean install, and the ping test worked. My DNS is provided by my Ubiquiti gateway, so I will attempt a re-install.

[ukdtom]

Updated my comment above !

[pfzlsk]

I followed the "Why am I locked out" directions with the same results. I only had one of the reg entries of the 4 it said to look for. I also ran ClaimIT after getting the unclaimed message and again got the 500 error.

Earlier, I tried using the installer's repair function and curiously it stopped to ask for the pms.exe file which did not exist in the location (at least outside of the installer file), but at the point it stopped the installer window referenced the C++ Redistributable (2015-2019), which I confirmed is installed. So this may point to deeper problems with the OS. So I'm back at Square 1.

I really appreciate all of your effort

[ukdtom]

Then sadly out of scope here ;)

[stevehurcombe]

@ukdtom the version in the zip file worked perfectly for me.