-
Notifications
You must be signed in to change notification settings - Fork 154
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.
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
Jellyseer authentication to jellyfin fails #95
Comments
Forgot to add I can curl to http://jellyfin:8096/jellyfin from within jellyseerr docker |
related issue here: Fallenbagel/jellyseerr#1023 |
I was having similar issues. In the
|
The approach above might work if you already had a working jellyseerr installation, but it's preventing me from going through the initial setup now. I can't just plug those values into settings.json because it will just ignore them during installation. Why doesn't the jellyseerr page ask for an API token during setup? As far as I can tell it's required, and when using an api token I can authenticate using curl with the provided settings. |
This is my problem, I'm trying to do an initial setup have never used the app before. |
Late to the party, but was anything fixed on Jellyseer's end? Do we need to update our configurations or the readme to make it work for new users? |
Hi great script thanks for posting.
I have everything working fine as it should except I can't get Jellyseerr to login to Jellyfin, just get incorrect username and password error.
Error in Jellyseerr logs is:
[debug][Jellyfin API]: Failed to authenticate with headers: fetch failed {"ip":"172.22.0.2"}
[warn][Auth]: Failed login attempt from user with incorrect Jellyfin credentials {"account":{"ip":"::ffff:172.22.0.2","email":"jl","password":"REDACTED"}}
I'm using http://jellyfin:8096/jellyfin as the server url and correct username and password.
Don't even see the attempt in the Jellyfin logs as doesn't seem to get past Traefik.
Not sure if it's an issue with the rewrite middleware or not.
The text was updated successfully, but these errors were encountered: