Skip to content

Jellyseerr Failed Updateย #4355

Description

@oOStroudyOo

โœ… Have you read and understood the above guidelines?

Yes

๐Ÿ“œ What is the name of the script you are using?

Jellyseerr

๐Ÿ“‚ What was the exact command used to execute the script?

update

โš™๏ธ What settings are you using?

  • Default Settings
  • Advanced Settings

๐Ÿ–ฅ๏ธ Which Linux distribution are you using?

Debian 12

๐Ÿ“ Provide a clear and concise description of the issue.

Jellyseerr fails to update, I have used the update script previously with no problem so unsure if it's a script problem, or a Jellyseerr problem.

Same error as #4233 except I'm trying to update, rather than install, and using the correct script as seen instead my /bin/update file (bash -c "$(curl -qLO - https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyseerr.sh)")

I've also tried it with bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyseerr.sh)"

If I try and run npm install --frozen-lockfile manually, you get:
ERR_PNPM_NO_PKG_MANIFESTโ€‰ No package.json found in /root

๐Ÿ”„ Steps to reproduce the issue.

Update Jellyseerr using update script.

โŒ Paste the full error output (if available).

remote: Enumerating objects: 961, done.
remote: Counting objects: 100% (556/556), done.
remote: Compressing objects: 100% (20/20), done.
remote: Total 961 (delta 534), reused 547 (delta 530), pack-reused 405 (from 1)
Receiving objects: 100% (961/961), 352.78 KiB | 11.76 MiB/s, done.
Resolving deltas: 100% (673/673), completed with 178 local objects.
From https://github.com/Fallenbagel/jellyseerr
   5663ac1a..fac45387  main                -> origin/main
   e5ab8475..70a28dd1  develop             -> origin/develop
 + 21654614...a3feaba2 feat-dns-caching-manager -> origin/feat-dns-caching-manager  (forced update)
 * [new branch]        fix-pending-media   -> origin/fix-pending-media
 * [new branch]        fix-pgsql-timezone  -> origin/fix-pgsql-timezone
 * [new branch]        fix-typeorm-update  -> origin/fix-typeorm-update
 * [new tag]           preview-typeorm-fix -> preview-typeorm-fix
 * [new tag]           v2.5.2              -> v2.5.2
  โœ–๏ธ   Updating pnpm from version 10.6.4 to ^9.0.0...

changed 1 package in 1s

1 package is looking for funding
  run `npm fund` for details
npm notice
npm notice New major version of npm available! 10.9.2 -> 11.3.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.3.0
npm notice To update run: npm install -g npm@11.3.0
npm notice
โ ‹ Updating Jellyseerrโ€‰ERR_PNPM_UNSUPPORTED_ENGINEโ€‰ Unsupported environment (bad pnpm and/or Node.js version)

Your pnpm version is incompatible with "/opt/jellyseerr".

Expected version: ^9.0.0
Got: 10.6.4

This is happening because the package's manifest has an engines.pnpm field specified.
To fix this issue, install the required pnpm version globally.

To install the latest version of pnpm, run "pnpm i -g pnpm".
To check your pnpm version, run "pnpm -v".
โ ™ Updating Jellyseerr
[ERROR] in line 73: exit code 0: while executing command $STD pnpm install --frozen-lockfile

๐Ÿ–ผ๏ธ Additional context (optional).

Image

Image

Activity

  1. MickLesk commented on May 9, 2025

    @MickLesk
    Member

    Pnpm 9.0 what an sleeper Repo...

  2. MickLesk commented on May 9, 2025

    @MickLesk
    Member

    can you check again if #4365 merged?

  3. oOStroudyOo commented on May 10, 2025

    @oOStroudyOo
    ContributorAuthor

    Hi @MickLesk

    Same error occurs, just looks a little different this time:

    remote: Enumerating objects: 959, done.
    remote: Counting objects: 100% (552/552), done.
    remote: Compressing objects: 100% (25/25), done.
    remote: Total 959 (delta 527), reused 538 (delta 521), pack-reused 407 (from 1)
    Receiving objects: 100% (959/959), 351.81 KiB | 12.56 MiB/s, done.
    Resolving deltas: 100% (667/667), completed with 179 local objects.
    From https://github.com/Fallenbagel/jellyseerr
       5663ac1a..fac45387  main                -> origin/main
       e5ab8475..8da1c929  develop             -> origin/develop
     + 21654614...a3feaba2 feat-dns-caching-manager -> origin/feat-dns-caching-manager  (forced update)
     * [new branch]        fix-pending-media   -> origin/fix-pending-media
     * [new branch]        fix-typeorm-update  -> origin/fix-typeorm-update
     * [new tag]           preview-typeorm-fix -> preview-typeorm-fix
     * [new tag]           v2.5.2              -> v2.5.2
      โœ–๏ธ   Updating pnpm from version 10.6.4 to ^9.0.0...
      โœ”๏ธ   Node.js 22 already installed
    
    changed 1 package in 862ms
    
    1 package is looking for funding
      run `npm fund` for details
      โœ”๏ธ   All requested Node modules have been processed
    โ ธ Updating Jellyseerrโ€‰ERR_PNPM_UNSUPPORTED_ENGINEโ€‰ Unsupported environment (bad pnpm and/or Node.js version)
    
    Your pnpm version is incompatible with "/opt/jellyseerr".
    
    Expected version: ^9.0.0
    Got: 10.6.4
    
    This is happening because the package's manifest has an engines.pnpm field specified.
    To fix this issue, install the required pnpm version globally.
    
    To install the latest version of pnpm, run "pnpm i -g pnpm".
    To check your pnpm version, run "pnpm -v".
    
       โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
       โ”‚                                          โ”‚
       โ”‚   Update available! 10.6.4 โ†’ 10.10.0.    โ”‚
       โ”‚   Changelog: https://pnpm.io/v/10.10.0   โ”‚
       โ”‚     To update, run: pnpm self-update     โ”‚
       โ”‚                                          โ”‚
       โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ
    
    โ ผ Updating Jellyseerr
    [ERROR] in line 73: exit code 0: while executing command $STD pnpm install --frozen-lockfile
    
  4. oOStroudyOo commented on May 10, 2025

    @oOStroudyOo
    ContributorAuthor

    Seems to work fine from a fresh install. Perhaps something wrong with my setup.
    I'll close this and copy/paste my config over to the new one.

    Thank you.

  5. locked as resolved and limited conversation to collaborators on Feb 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions