[GH-ISSUE #11961] New Jellyseerr script breaks "update" functionality on existing installations when using "update" and choosing to migrate to Seerr #2514

Closed
opened 2026-02-26 12:52:41 +03:00 by kerem · 2 comments
Owner

Originally created by @giannisg2004 on GitHub (Feb 16, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11961

Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 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 13

📈 Which Proxmox version are you on?

9.1.5

📝 Provide a clear and concise description of the issue.

The update functionality of the Jellyseerr script seems broken after the new script went live that migrates to Seerr.

Running update from within the LXC, and answeryes to migrating to Seerr, yields:

Switched update script to Seerr. Running update...   
/usr/bin/update: line 40: syntax error near unexpected token ('    
/usr/bin/update: line 40:     msg_info "Creating Backup (Patience)"'  
/usr/bin/update: line 2: syntax error near unexpected token )'  
/usr/bin/update: line 2: ts/ProxmoxVE/main/misc/build.func)' 

This looks like a shell parsing error.

Looking at the (new) jellyseer.sh script that update executes, I see on lines 48-50:

    sed -i 's|https://github.com/community-scripts/ProxmoxVE/raw/main/ct/jellyseerr.sh|https://github.com/community-scripts/ProxmoxVE/raw/main/ct/seerr.sh|g' /usr/bin/update
    msg_ok "Switched update script to Seerr. Running update..."
    exec /usr/bin/update

Is it possible that rewriting /usr/bin/update and immediately executing it (without specifying bash), falls back to dash, which is trying do command substitution in bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/jellyseerr.sh)" before continuing in bash, and fails when it encounters <(...) at the beginning of the script?

🔄 Steps to reproduce the issue.

  1. Run update from inside the LXC
  2. Answer yes to migrating to Seerr
  3. script fails

Paste the full error output (if available).

usr/bin/update: line 40: syntax error near unexpected token ('
/usr/bin/update: line 40: msg_info "Creating Backup (Patience)"'
/usr/bin/update: line 2: syntax error near unexpected token )'
/usr/bin/update: line 2: ts/ProxmoxVE/main/misc/build.func)'

🖼️ Additional context (optional).

No response

Originally created by @giannisg2004 on GitHub (Feb 16, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11961 ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 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? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 9.1.5 ### 📝 Provide a clear and concise description of the issue. The update functionality of the Jellyseerr script seems broken after the new script went live that migrates to Seerr. Running `update` from within the LXC, and answer`yes` to migrating to Seerr, yields: ``` Switched update script to Seerr. Running update... /usr/bin/update: line 40: syntax error near unexpected token (' /usr/bin/update: line 40: msg_info "Creating Backup (Patience)"' /usr/bin/update: line 2: syntax error near unexpected token )' /usr/bin/update: line 2: ts/ProxmoxVE/main/misc/build.func)' ``` This looks like a shell parsing error. Looking at the (new) jellyseer.sh script that `update` executes, I see on lines 48-50: ``` sed -i 's|https://github.com/community-scripts/ProxmoxVE/raw/main/ct/jellyseerr.sh|https://github.com/community-scripts/ProxmoxVE/raw/main/ct/seerr.sh|g' /usr/bin/update msg_ok "Switched update script to Seerr. Running update..." exec /usr/bin/update ``` Is it possible that rewriting /usr/bin/update and immediately executing it (without specifying bash), falls back to dash, which is trying do command substitution in `bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/jellyseerr.sh)"` before continuing in bash, and fails when it encounters `<(...)` at the beginning of the script? ### 🔄 Steps to reproduce the issue. 1. Run `update` from inside the LXC 2. Answer `yes` to migrating to Seerr 3. script fails ### ❌ Paste the full error output (if available). usr/bin/update: line 40: syntax error near unexpected token (' /usr/bin/update: line 40: msg_info "Creating Backup (Patience)"' /usr/bin/update: line 2: syntax error near unexpected token )' /usr/bin/update: line 2: ts/ProxmoxVE/main/misc/build.func)' ### 🖼️ Additional context (optional). _No response_
kerem 2026-02-26 12:52:41 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@Soulful-Sailer commented on GitHub (Feb 16, 2026):

I can confirm this happens for me as well

<!-- gh-comment-id:3906399289 --> @Soulful-Sailer commented on GitHub (Feb 16, 2026): I can confirm this happens for me as well
Author
Owner

@tumeden commented on GitHub (Feb 16, 2026):

Happening with me as well

Do you want to migrate to Seerr now? (y/N): y

  ✔️   Switched update script to Seerr. Running update...
/usr/bin/update: line 40: syntax error near unexpected token `('
/usr/bin/update: line 40: `    msg_info "Creating Backup (Patience)"'
/usr/bin/update: line 2: syntax error near unexpected token `)'
/usr/bin/update: line 2: `xVE/main/misc/build.func)'

Edit:
You can run this in your LXC with overseer and it will do the migration. Just did it with mine.

curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/seerr.sh -o /usr/bin/update && chmod +x /usr/bin/update && update
  ✔️   Stopped Overseerr
  ✔️   Created Backup
  ✔️   Migrated Overseerr to Seerr
  ✔️   Update available: seerr not installed → 3.0.1
  ✔️   Stopped Service
  ✔️   Created Backup
  ✔️   Deployed: seerr (3.0.1)
  ✔️   Update Node.js 22
  ✔️   Installed Node.js modules: pnpm@^10.0.0
  ✔️   Updated PNPM Version
  ✔️   Updated Seerr
  ✔️   Restored Backup
  ✔️   Started Service
  ✔️   Updated successfully!
<!-- gh-comment-id:3906579594 --> @tumeden commented on GitHub (Feb 16, 2026): Happening with me as well ```` Do you want to migrate to Seerr now? (y/N): y ✔️ Switched update script to Seerr. Running update... /usr/bin/update: line 40: syntax error near unexpected token `(' /usr/bin/update: line 40: ` msg_info "Creating Backup (Patience)"' /usr/bin/update: line 2: syntax error near unexpected token `)' /usr/bin/update: line 2: `xVE/main/misc/build.func)' ```` Edit: You can run this in your LXC with overseer and it will do the migration. Just did it with mine. ```` curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/seerr.sh -o /usr/bin/update && chmod +x /usr/bin/update && update ```` ```` ✔️ Stopped Overseerr ✔️ Created Backup ✔️ Migrated Overseerr to Seerr ✔️ Update available: seerr not installed → 3.0.1 ✔️ Stopped Service ✔️ Created Backup ✔️ Deployed: seerr (3.0.1) ✔️ Update Node.js 22 ✔️ Installed Node.js modules: pnpm@^10.0.0 ✔️ Updated PNPM Version ✔️ Updated Seerr ✔️ Restored Backup ✔️ Started Service ✔️ Updated successfully! ````
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#2514
No description provided.