Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Jellyseer will log into the wrong account after a first login with plex is done #1227

Closed
1 task done
Simoneu01 opened this issue Jan 5, 2025 · 7 comments · Fixed by #1242
Closed
1 task done

Jellyseer will log into the wrong account after a first login with plex is done #1227

Simoneu01 opened this issue Jan 5, 2025 · 7 comments · Fixed by #1242
Assignees
@gauthier-th @fallenbagel
Labels
bug Something isn't working confirmed This bug has been reproduced released

Comments

@Simoneu01
Copy link
Contributor

Simoneu01 commented Jan 5, 2025 •
edited
Loading

Description

You get logged into the wrong account using Plex accounts

Version

2.2.3

Steps to Reproduce

Log into another account:

  1. Container started
  2. Log into an account with Plex
  3. Log with another account → Result = Logged with admin account

Access Denied Error:

  1. Set up jellyseer
  2. Import the 2nd user
  3. Stop the container
  4. Start the container
  5. Try to log in with the 2nd account → Result = Access Denied

Screenshots

image

Logs

https://discord.com/channels/952656177924300932/952656177924300935/1325586287146831922
https://discord.com/channels/952656177924300932/952656177924300935/1325511600286990367
https://discord.com/channels/952656177924300932/952656177924300935/1325498349742456842
https://discord.com/channels/952656177924300932/952656177924300935/1325497521203843082
https://discord.com/channels/952656177924300932/952656177924300935/1325496852467945504

Platform

desktop

Database

SQLite (default)

Device

PC & Android

Operating System

W11 & andorid

Browser

Edge & Chrome

Additional Context

No response

Code of Conduct

  • I agree to follow Jellyseerr's Code of Conduct
@Simoneu01 Simoneu01 added awaiting triage This issue needs to be reviewed bug Something isn't working labels Jan 5, 2025
@fallenbagel
Copy link
Owner

Could you post the logs when you see when you login as the second user that gets logged in as the previous/wrong user

@Simoneu01
Copy link
Contributor Author

Simoneu01 commented Jan 5, 2025 •
edited
Loading

Logs 1.9.4:
overseerr.log

Logs 2.2.3:
overseerr.log

@Simoneu01
Copy link
Contributor Author

Updated logs when I got the error "Access denied."
overseerr.log

@svenEsven
Copy link

same Issues here. also unable to connect to my plex anymore? about to rebuild just to see if it will work fresh.

@svenEsven
Copy link

rebuilt it, new config, same issue

@fallenbagel
Copy link
Owner

fallenbagel commented Jan 9, 2025 •
edited
Loading

@svenEsven this is a confirmed issue. You'll either have to use 1.9.2 or wait for the fix. Or use overseerr

@fallenbagel fallenbagel added confirmed This bug has been reproduced and removed awaiting triage This issue needs to be reviewed labels Jan 9, 2025
fallenbagel added a commit that referenced this issue Jan 11, 2025
@fallenbagel
fix: resolve plex user mismatch due to caching issues
a6e4390 
This commit addresses an issue where cached responses for PlexTV API
requests could return incorrect user data when multiple users were logged in.
This was caused by a shared cache key that did not account for differences
in auth tokens, i.e `X-Plex-Token`. The `serializeCacheKey` method should
now include headers in the cache key generation to ensure unique cache keys.
This should fix the plex user mismatch that occurred due to the same
cache key being used without accounting for the difference in auth
token.

fix #1227
@fallenbagel fallenbagel mentioned this issue Jan 11, 2025
Merged
3 tasks
fallenbagel added a commit that referenced this issue Jan 12, 2025
@fallenbagel
fix: resolve plex user mismatch due to caching issues (#1242)
131a5a2 
* fix: resolve plex user mismatch due to caching issues

This commit addresses an issue where cached responses for PlexTV API
requests could return incorrect user data when multiple users were logged in.
This was caused by a shared cache key that did not account for differences
in auth tokens, i.e `X-Plex-Token`. The `serializeCacheKey` method should
now include headers in the cache key generation to ensure unique cache keys.
This should fix the plex user mismatch that occurred due to the same
cache key being used without accounting for the difference in auth
token.

fix #1227

* fix: adds the default params and optional params, add the headers in all methods

* refactor: apply review commits and rename params to options in cachekey
@fallenbagel
Copy link
Owner

🎉 This issue has been resolved in version 2.3.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gauthier-th gauthier-th

@fallenbagel fallenbagel

Labels
bug Something isn't working confirmed This bug has been reproduced released
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: resolve plex user mismatch due to caching issues fallenbagel/jellyseerr
4 participants
@gauthier-th @Simoneu01 @svenEsven @fallenbagel