We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tl;dr: Attempting to link Plex via the WebUI and ShokoDesktop fails.
Following the process documented in the docs, I'm getting the following errors in the logs and it doesn't give me the choice to select the server.
Attempting to perform the same action on Desktop results in the same error.
Server Version: 5.1.0.0 Web Version: 2.2.0 Desktop Version: 4.3.0.0
2025-02-02 17:40:23 Trace Requesting from plex: GET https://plex.tv/users/account.json 2025-02-02 17:40:24 Trace Got response: UnprocessableEntity 2025-02-02 17:40:24 Trace Requesting from plex: GET https://plex.tv/users/account.json 2025-02-02 17:40:25 Trace Got response: UnprocessableEntity 2025-02-02 17:40:25 Trace Requesting from plex: GET https://plex.tv/users/account.json 2025-02-02 17:40:26 Trace Got response: UnprocessableEntity 2025-02-02 17:40:26 Trace Requesting from plex: GET https://plex.tv/users/account.json
The text was updated successfully, but these errors were encountered:
Do you happen to have 2FA on your Plex account? If so see if it works after disabling it or try appending the auth to the password. password2FA
password2FA
Nvm, I tested it with 2FA and it is fine what I said above is irrelevant.
Sorry, something went wrong.
How did you fix your issue? I'm having the same problem, with and without 2fa
No branches or pull requests
tl;dr: Attempting to link Plex via the WebUI and ShokoDesktop fails.
Following the process documented in the docs, I'm getting the following errors in the logs and it doesn't give me the choice to select the server.
Attempting to perform the same action on Desktop results in the same error.
Server Version: 5.1.0.0
Web Version: 2.2.0
Desktop Version: 4.3.0.0
The text was updated successfully, but these errors were encountered: