Server Version#:1.2.3.3483-211702a9f
Windows 10 1909
Tried opening plex in the browser using localhost and I got this error “We were unable to complete this request.”
Did a little troubleshooting, tried deleting the registry keys for my username and rebooting, tried reinstalling the app from scratch but it seemed to retain some data
right now my server is still showing my libraries but it’s “unclaimed” and when I try to claim it I get that error which appears to be signin/credentials related
I get the same error when I click in the upper right and click “sign in”
I also tried doing it in private mode and trying other browsers
is it possible to get your server logs. ( you can message them to me). There is another user having a similar issue right now and want to see if I see the same sort of errors in logs.
some curl errors, and a time out like this below (filter on myPlex) if you want to look yourself
Oct 28, 2020 15:26:48.676 [11840] DEBUG - Request: [127.0.0.1:52224 (Loopback)] POST /myplex/claim?token=xxxxxxxxxxxxxxxxxxxxxxx (4 live) GZIP
Oct 28, 2020 15:27:01.813 [11840] DEBUG - MyPlex: Did token exchange for claim (returnCode: 408)
Oct 28, 2020 15:27:01.813 [11840] DEBUG - MyPlex: Got a token poked, let's act on it.```
I did more troubleshooting. I figured I would try to start from scratch and rebuild my library.
I signed in on the public website and under settings and made sure I deleted all my sessions and devices.
I removed the program in control panel, deleted the whole registry key for plex, deleted the plex folder in appdata, in programfiles and programfiles x86 and anywhere else I could find anything that said plex
rebooted and reinstalled, getting the same error, now it is coming up upon launching the program (can’t get as far as an interface anymore)
Unfortunately there is another issue with sign in to local that popped up right now that is probably exacerbating the one you came to report. waiting on our devops guys who are working on it right now to fix that
I had to set my library and settings back up from scratch, likely due to my aggressive removal. Seemed fine, started scanning, I see it’s chugging along. I try to go to the library and get this error
@BigWheel Just wanted to hop in and say I was experiencing similar issues as this user at the time of issue creation. Everything has been resolved for me as well. Thanks, too!