Description
During the Plex auth popup process, Seerr is not including the stored clientId from the config files. This causes every browser to generate its own unique clientId. This clientId is not expected by Plex, which makes Plex return a blank auth response, which locks the users out. This can be seen here:
root@Plex:/mnt/cache/appdata/swag/nginx/proxy-confs# curl -s http://localhost:5056/api/v1/settings/public | python3 -m json.tool | grep -i "client\|plex"
"applicationUrl": "https://request.myplex.com/",
"newPlexLogin": false,```
If the auth process passed in the stored clientId, this would allow Plex to see a previously authenticated client ID and complete the OAuth process.
Version
2.7.3
Steps to Reproduce
- Go to Seerr
- Click Authenticate with Plex
- Approve the authentication in the Plex popup
- Look at the empty response from the POST in Network dev tools
- Not be logged into Seerr or get past the login page
I have tried nightly, your own container and hotio's container. All behave the same way.
Screenshots
response - See "authToken:null"
{"id":1589111464,"code":"u4fsabbj9zomh3j6i2nimg2a3","product":"Jellyseerr","trusted":false,"qr":"https://plex.tv/api/v2/pins/qr/u4fsabbj9zomh3j6i2nimg2a3","clientIdentifier":"8cfe391f-b8d8-40ab-b453-734967d5b36d","location":{"code":"US","european_union_member":false,"continent_code":"NA","country":"United States","city":"none","time_zone":"Etc/UTC","postal_code":"none","in_privacy_restricted_country":false,"in_privacy_restricted_region":false,"subdivisions":"New York","coordinates":"redacted3, redacted"},"expiresIn":1800,"createdAt":"2026-03-20T19:19:34Z","expiresAt":"2026-03-20T19:49:34Z","authToken":null,"newRegistration":null}
Logs
Seerr is not logging the response because it's not getting a successful response.
Platform
desktop
Database
SQLite (default)
Device
Unraid 7.2.4
Operating System
Unraid 7.2.4
Browser
Firefox
Additional Context
I did try to work through this issue 2 weeks ago with the Seerr team in discord, but we couldn't figure it out. I have since discovered more information to help troubleshoot, and narrowed it down to this null response issue.
Search Existing Issues
Code of Conduct
Description
During the Plex auth popup process, Seerr is not including the stored clientId from the config files. This causes every browser to generate its own unique clientId. This clientId is not expected by Plex, which makes Plex return a blank auth response, which locks the users out. This can be seen here:
If the auth process passed in the stored clientId, this would allow Plex to see a previously authenticated client ID and complete the OAuth process.
Version
2.7.3
Steps to Reproduce
I have tried nightly, your own container and hotio's container. All behave the same way.
Screenshots
response - See "authToken:null"
{"id":1589111464,"code":"u4fsabbj9zomh3j6i2nimg2a3","product":"Jellyseerr","trusted":false,"qr":"https://plex.tv/api/v2/pins/qr/u4fsabbj9zomh3j6i2nimg2a3","clientIdentifier":"8cfe391f-b8d8-40ab-b453-734967d5b36d","location":{"code":"US","european_union_member":false,"continent_code":"NA","country":"United States","city":"none","time_zone":"Etc/UTC","postal_code":"none","in_privacy_restricted_country":false,"in_privacy_restricted_region":false,"subdivisions":"New York","coordinates":"redacted3, redacted"},"expiresIn":1800,"createdAt":"2026-03-20T19:19:34Z","expiresAt":"2026-03-20T19:49:34Z","authToken":null,"newRegistration":null}
Logs
Seerr is not logging the response because it's not getting a successful response.Platform
desktop
Database
SQLite (default)
Device
Unraid 7.2.4
Operating System
Unraid 7.2.4
Browser
Firefox
Additional Context
I did try to work through this issue 2 weeks ago with the Seerr team in discord, but we couldn't figure it out. I have since discovered more information to help troubleshoot, and narrowed it down to this null response issue.
Search Existing Issues
Code of Conduct