SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Jellyseer Update FAIL #314

New Issue
Closed
opened 2025-11-20 04:46:50 -05:00 by saavagebueno · 7 comments
saavagebueno commented 2025-11-20 04:46:50 -05:00
Owner
Copy Link

Originally created by @seneca13 on GitHub (Jan 7, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Jellyseerr LXC

📂 What was the exact command used to execute the script?

update

📝 Provide a clear and concise description of the issue.

After updating "Jellyseerr LXC" by using "update", Jellyseerr gets broken.
Update requires deleting of certain directories before building, at least if updating from v2.0.1 or older!

The same problem has been reported in this closed issue report:
Jellyseerr breaking change #216

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

run Update

❌ Paste the full error output (if available).

Update reported to be successfull,
but Webfrontend is not reachable

🖼️ Additional context (optional).

This solved the problem:

Installing PNPM Package Manager:

curl -fsSL https://get.pnpm.io/install.sh | sh -
source /root/.bashrc

manual update, according to the github release page

cd /opt/jellyseerr
git pull
rm -r dist
rm -r .next 
rm -r node_modules
CYPRESS_INSTALL_BINARY=0 pnpm install --frozen-lockfile
pnpm build
systemctl restart jellyseerr
Originally created by @seneca13 on GitHub (Jan 7, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Jellyseerr LXC ### 📂 What was the exact command used to execute the script? update ### 📝 Provide a clear and concise description of the issue. After updating "Jellyseerr LXC" by using "update", Jellyseerr gets broken. Update requires deleting of certain directories before building, at least if updating from v2.0.1 or older! The same problem has been reported in this closed issue report: [ Jellyseerr breaking change #216 ](https://github.com/community-scripts/ProxmoxVE/issues/216) ### ⚙️ What settings are you using? - [X] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. run Update ### ❌ Paste the full error output (if available). Update reported to be successfull, but Webfrontend is not reachable ### 🖼️ Additional context (optional). This solved the problem: **Installing PNPM Package Manager:** ``` curl -fsSL https://get.pnpm.io/install.sh | sh - source /root/.bashrc ``` **manual update, according to the [github release page](https://github.com/Fallenbagel/jellyseerr/releases/tag/v2.1.0)** ``` cd /opt/jellyseerr git pull rm -r dist rm -r .next rm -r node_modules CYPRESS_INSTALL_BINARY=0 pnpm install --frozen-lockfile pnpm build systemctl restart jellyseerr ```
saavagebueno commented 2025-11-20 04:46:51 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Jan 10, 2025):

I can not find the issue here tbh. We do the update exactly as described by you above.

@michelroegl-brunner commented on GitHub (Jan 10, 2025): I can not find the issue here tbh. We do the update exactly as described by you above.
saavagebueno commented 2025-11-20 04:46:51 -05:00
Author
Owner
Copy Link

@seneca13 commented on GitHub (Jan 10, 2025):

My update broke, used my backup and did the manual steps to get a working update.., but like I wrote above

...., at least if updating from v2.0.1 or older!

@seneca13 commented on GitHub (Jan 10, 2025): My update broke, used my backup and did the manual steps to get a working update.., but like I wrote above >...., at least if updating from v2.0.1 or older!
saavagebueno commented 2025-11-20 04:46:51 -05:00
Author
Owner
Copy Link

@lichenophile commented on GitHub (Jan 10, 2025):

My update also failed.

I've attempted updates post v2.0.1 with some failures, can't recall how I got it working again priod but have never been certain it's actually updated since the app just shows as 'dev' or something similar.

Gave the instuctions in OP a go with no luck:

root@jellyseerr:/opt/jellyseerr# CYPRESS_INSTALL_BINARY=0 pnpm install --frozen-lockfile
 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

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

Expected version: ^22.0.0
Got: v20.12.2

This is happening because the package's manifest has an engines.node field specified.
To fix this issue, install the required Node version.
@lichenophile commented on GitHub (Jan 10, 2025): My update also failed. I've attempted updates post v2.0.1 with some failures, can't recall how I got it working again priod but have never been certain it's actually updated since the app just shows as 'dev' or something similar. Gave the instuctions in OP a go with no luck: ``` root@jellyseerr:/opt/jellyseerr# CYPRESS_INSTALL_BINARY=0 pnpm install --frozen-lockfile  ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version) Your Node version is incompatible with "/opt/jellyseerr". Expected version: ^22.0.0 Got: v20.12.2 This is happening because the package's manifest has an engines.node field specified. To fix this issue, install the required Node version. ```
saavagebueno commented 2025-11-20 04:46:51 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Jan 11, 2025):

Try to update your node version as stated in the error messsge.

@michelroegl-brunner commented on GitHub (Jan 11, 2025): Try to update your node version as stated in the error messsge.
saavagebueno commented 2025-11-20 04:46:51 -05:00
Author
Owner
Copy Link

@lichenophile commented on GitHub (Jan 11, 2025):

Yeah I tried that, it upgraded node to 20.18.1 only, so I did some googling and tried
curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
apt-get install nodejs -y
then proceeded from where I left off with

CYPRESS_INSTALL_BINARY=0 pnpm install --frozen-lockfile
pnpm build
systemctl restart jellyseerr

Not sure if this was the correct way to go about it, but it seems to have worked

@lichenophile commented on GitHub (Jan 11, 2025): Yeah I tried that, it upgraded node to 20.18.1 only, so I did some googling and tried `curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -` `apt-get install nodejs -y` then proceeded from where I left off with ``` CYPRESS_INSTALL_BINARY=0 pnpm install --frozen-lockfile pnpm build systemctl restart jellyseerr ``` Not sure if this was the correct way to go about it, but it seems to have worked
saavagebueno commented 2025-11-20 04:46:52 -05:00
Author
Owner
Copy Link

@pafade89 commented on GitHub (Jan 16, 2025):

Yeah I tried that, it upgraded node to 20.18.1 only, so I did some googling and tried curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash - apt-get install nodejs -y then proceeded from where I left off with

CYPRESS_INSTALL_BINARY=0 pnpm install --frozen-lockfile
pnpm build
systemctl restart jellyseerr

Not sure if this was the correct way to go about it, but it seems to have worked

Can confirm that it also works for me. I think the script should upgrade the node version to 22.x.

@pafade89 commented on GitHub (Jan 16, 2025): > Yeah I tried that, it upgraded node to 20.18.1 only, so I did some googling and tried `curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -` `apt-get install nodejs -y` then proceeded from where I left off with > > ``` > CYPRESS_INSTALL_BINARY=0 pnpm install --frozen-lockfile > pnpm build > systemctl restart jellyseerr > ``` > > Not sure if this was the correct way to go about it, but it seems to have worked Can confirm that it also works for me. I think the script should upgrade the node version to 22.x.
saavagebueno commented 2025-11-20 04:46:52 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 16, 2025):

Merged for new Installs. Check PR and Changelog or discussion for manually Update nodeJS

@MickLesk commented on GitHub (Jan 16, 2025): Merged for new Installs. Check PR and Changelog or discussion for manually Update nodeJS
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#314
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?