🐛 [jellyseerr] New 2.1.0 version is not working

[AnshulJ999]

Description

There is something wrong with the new 2.1.0 Jellyseerr version and it doesn't work for me.

Add-on logs are attached. I'm not sure what's wrong and whether I did something wrong or if there's an issue with the update.

I rolled back to 2.0.1 for now and it's working again. Any help is appreciated. Thanks.

Reproduction steps

1. Update the Jellyseerr addon to 2.1.0 from 2.0.1. 

Everything else is latest version as of now.

Addon Logs

/etc/cont-init.d/00-banner.sh: executing
-----------------------------------------------------------
 Add-on: Jellyseerr
 Fork of overseerr for jellyfin support
-----------------------------------------------------------
 Add-on version: 2.1.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.2  (amd64 / qemux86-64)
 Home Assistant Core: 2024.11.3
 Home Assistant Supervisor: 2024.11.4
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums
-----------------------------------------------------------
 Provided by: https://github.com/alexbelgium/hassio-addons 
-----------------------------------------------------------
/etc/cont-init.d/00-global_var.sh: executing
TYPE='emby'
TZ='Europe/Paris'
/etc/cont-init.d/00-local_mounts.sh: executing
/etc/cont-init.d/00-smb_mounts.sh: executing
/etc/cont-init.d/01-config_yaml.sh: executing
Setting permissions for the config.yaml directory
Load environment variables from /config/addons_config/jellyseerr/config.yaml if existing
If accessing the file with filebrowser it should be mapped to /homeassistant/addons_config/jellyseerr/config.yaml
---------------------------------------------------------
Wiki here on how to use : github.com/alexbelgium/hassio-addons/wiki/Add‐ons-feature-:-add-env-variables
... no env variables found, exiting
/etc/cont-init.d/01-custom_script.sh: executing
Execute /homeassistant/addons_autoscripts/jellyseerr.sh if existing
Wiki here : github.com/alexbelgium/hassio-addons/wiki/Add-ons-feature-:-customisation
/etc/cont-init.d/90-run.sh: executing
[21:59:20] INFO: Config stored in /config/addons_config/jellyseerr
yarn run v1.22.22
warning [email protected]: The engine "pnpm" appears to be invalid.
$ NODE_ENV=production node dist/index.js
2024-11-25T20:59:22.195Z [info]: Commit Tag: $GIT_SHA 
2024-11-25T20:59:22.855Z [info]: Starting Overseerr version 2.1.0 
2024-11-25T20:59:23.510Z [debug][Settings Migrator]: Checking migration '0001_migrate_hostname.js'... 
2024-11-25T20:59:23.513Z [debug][Settings Migrator]: Checking migration '0002_migrate_apitokens.js'... 
2024-11-25T20:59:23.557Z [error][Jellyfin API]: Something went wrong while creating an API key from the Jellyfin server {"error":"Unauthorized"}
2024-11-25T20:59:23.558Z [error][Settings Migrator]: Error while running migration '0002_migrate_apitokens.js': Failed to create Jellyfin API token from admin account. Please check your network configuration or edit your settings.json by adding an 'apiKey' field inside of the 'jellyfin' section to fix this issue. 
2024-11-25T20:59:23.559Z [error][Settings Migrator]: A common cause for this error is a permission issue with your configuration folder, a network issue or a corrupted database. 
Done in 3.13s.
Starting the upstream container

Architecture

No response

OS

HAos

[alexbelgium]

Hi, looks like this : same error observed upstream. There was no clear solution beyond redoing the config : Fallenbagel/jellyseerr#1009

[AnshulJ999]

Hi, looks like this : same error observed upstream. There was no clear solution beyond redoing the config : Fallenbagel/jellyseerr#1009

Hi, If I understood correctly, you mean I have to delete the config folder and redo the whole setup? :(

I'll lose all the saved settings and all in that case?

I guess I have to stick to 2.0.1 in that case. Until there's some solution.

[alexbelgium]

Well that's what jelyseer devs seem to say... I'll revert the add-on and hopefully next version will avoid this

[AnshulJ999]

Fallenbagel/jellyseerr#1095 (comment)

This may be a possible solution to the same problem I faced. I will try to test later once I get time.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.