Login with Jellyfin not working after update to 2.0.1

[p-rintz]

Description

Trying to login to Jellyseerr with Jellyfin login fails after update to 2.0.1 with the following error message: Something went wrong while trying to sign in.

In the log it will give the following two lines in regards to the failure:

Oct 17 15:34:56 jellyseerr node[162701]: 2024-10-17T15:34:56.720Z [debug][Jellyfin API]: Failed to authenticate with headers: Failed to parse URL from http://undefined:undefinedundefined/Users/AuthenticateByName {"ip":"10.2.100.128"}
Oct 17 15:34:56 jellyseerr node[162701]: 2024-10-17T15:34:56.721Z [warn][Auth]: Failed login attempt from user with incorrect Jellyfin credentials {"account":{"ip":"::ffff:10.2.100.128","email":"my@email.example.com","password":"__REDACTED__"}}

Not sure why everything is now undefined after the upgrade in regards to the Jellyfin instance.

Version

2.0.1

Steps to Reproduce

1. Upgrade to 2.0.1
2. Go to login
3. Try to login
4. Fail

Screenshots

No response

Logs

No response

Platform

desktop

Device

Linux PC

Operating System

Ubuntu 22.04

Browser

Firefox

Additional Context

No response

Code of Conduct

• [X] I agree to follow Jellyseerr's Code of Conduct

[Fallenbagel]

http://undefined:undefinedundefined/

can you check your settings.json and see the jellyfin section. See if the ip and port is set correctly Because from that log it shows as its not

[p-rintz]

I looked through Discord to see if others had this issue and found somebody who had posted their settings.json. Their settings.json had some things which mine lacked.

Here is the diff from my backed-up settings.json and the settings.json that now works:

 "jellyfin": {                           "jellyfin": {
  "name": "Jellyfin",                         |   "name": "",
  "hostname": "http://10.2.100.100:8096",             |   "hostname": "http://10.2.100.100",
  "externalHostname": "https://domain.was.here.com",              "externalHostname": "https://domain.was.here.com",
  "jellyfinForgotPasswordUrl": "",                |   "libraries": [],
  "libraries": [                          |   "serverId": "0101010101010101010101001010101010101"
   {                                  <
    "id": "0202020202020202",             <
    "name": "Anime",                          <
    "enabled": true,                          <
    "type": "show"                        <
   },                                 <
   {                                  <
    "id": "030303030303030",              <
    "name": "Movies",                         <
    "enabled": true,                          <
    "type": "movie"                       <
   },                                 <
   {                                  <
    "id": "040404040404040",              <
    "name": "Shows",                          <
    "enabled": true,                          <
    "type": "show"                        <
   }                                  <
  ],                                  <
  "serverId": "0101010101010101010101001010101010101",        <
  "ip": "10.2.100.100",                       <
  "useSsl": false,                        <
  "urlBase": "",                          <
  "apiKey": "APIKEYWASHERE",              <
  "port": 8096                            <
 },                              },

It was completely missing the ip,usessl,urlbase,apikey and port part.

[p-rintz]

It worked before 2.0.1 (so in 1.x). Not sure if there is supposed to be some migration happening or something.

[Fallenbagel]

there is supposed to be migrations happening in 2.0.0 and 2.0.1. I guess the migrations failed on your instance for some reason. Could happen if perm issue where jellyseerr was unable to write to settings.json when migrating

[Fallenbagel]

Please close the issue if fixed c:

[p-rintz]

Alright. Didnt want to just close it in case you wanted logs or anything the like.

[Fallenbagel]

Alright. Didnt want to just close it in case you wanted logs or anything the like.

The migration wouldnt log anything. We are thinking of adding a check when migration fails to not start jellyseerr to avoid migration failures for people migrating from 1.9.2 -> 2.x.x in the future