starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-16 05:34:07 +03:00
Code Issues 23 Packages Projects Releases 44 Wiki Activity

Umami: Updating from 3.0.1 to 3.0.3 fails with "pnpm: command not found" #2285

New Issue
Closed
opened 2026-02-05 04:23:47 +03:00 by OVERLORD · 11 comments
OVERLORD commented 2026-02-05 04:23:47 +03:00
Owner
Copy Link

Originally created by @raspberrycoulis on GitHub (Jan 5, 2026).

✅ 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?

Umami

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/umami.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/8.4.14/b502d23c55afcba1 (running kernel: 6.8.12-8-pve)

📝 Provide a clear and concise description of the issue.

I'm running Umami version 3.0.1 and in the UI, it tells me there's an update available. I then run bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/umami.sh)" within the LXC's command prompt and the update script starts. However, after selecting verbose mode and proceeding, it stops then outputs:

  ✔️   Update available: umami 3.0.1 → 3.0.3
  ✔️   Stopped Service
  ✔️   Deployed: umami (3.0.3)
  ⏳   Updating Umamienvironment: line 40: pnpm: command not found
  ✖️   in line 40: exit code 127 (Command not found): while executing command  pnpm install

I then have to restart Umami by running systemctl start umami and then the UI is accessible again.

🔄 Steps to reproduce the issue.

Step 1: Access LXC terminal from within Proxmox UI
Step 2: Run the update script, bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/umami.sh)"
Step 3: Error.

❌ Paste the full error output (if available).

  ✔️   Update available: umami 3.0.1 → 3.0.3
  ✔️   Stopped Service
  ✔️   Deployed: umami (3.0.3)
  ⏳   Updating Umamienvironment: line 40: pnpm: command not found
  ✖️   in line 40: exit code 127 (Command not found): while executing command  pnpm install

🖼️ Additional context (optional).

No response

Originally created by @raspberrycoulis on GitHub (Jan 5, 2026). ### ✅ 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? Umami ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/umami.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/8.4.14/b502d23c55afcba1 (running kernel: 6.8.12-8-pve) ### 📝 Provide a clear and concise description of the issue. I'm running Umami version 3.0.1 and in the UI, it tells me there's an update available. I then run `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/umami.sh)"` within the LXC's command prompt and the update script starts. However, after selecting verbose mode and proceeding, it stops then outputs: ```bash ✔️ Update available: umami 3.0.1 → 3.0.3 ✔️ Stopped Service ✔️ Deployed: umami (3.0.3) ⏳ Updating Umamienvironment: line 40: pnpm: command not found ✖️ in line 40: exit code 127 (Command not found): while executing command pnpm install ``` I then have to restart Umami by running `systemctl start umami` and then the UI is accessible again. ### 🔄 Steps to reproduce the issue. Step 1: Access LXC terminal from within Proxmox UI Step 2: Run the update script, `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/umami.sh)"` Step 3: Error. ### ❌ Paste the full error output (if available). ```bash ✔️ Update available: umami 3.0.1 → 3.0.3 ✔️ Stopped Service ✔️ Deployed: umami (3.0.3) ⏳ Updating Umamienvironment: line 40: pnpm: command not found ✖️ in line 40: exit code 127 (Command not found): while executing command pnpm install ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 04:23:47 +03:00
OVERLORD commented 2026-02-05 04:23:55 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 5, 2026):

How you entered the LXC?

@MickLesk commented on GitHub (Jan 5, 2026): How you entered the LXC?
OVERLORD commented 2026-02-05 04:23:58 +03:00
Author
Owner
Copy Link

@raspberrycoulis commented on GitHub (Jan 5, 2026):

How you entered the LXC?

Yeah, I run the command in the LXC as recommended.

Edit: Sorry read that wrong. I access it via the Proxmox UI then select console, login as root and run the bash script.

@raspberrycoulis commented on GitHub (Jan 5, 2026): > How you entered the LXC? ~~Yeah, I run the command in the LXC as recommended.~~ Edit: Sorry read that wrong. I access it via the Proxmox UI then select console, login as root and run the bash script.
OVERLORD commented 2026-02-05 04:24:00 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 5, 2026):

hm strange, should be in bashrc. run before: npm install -g pnpm

@MickLesk commented on GitHub (Jan 5, 2026): hm strange, should be in bashrc. run before: npm install -g pnpm
OVERLORD commented 2026-02-05 04:24:02 +03:00
Author
Owner
Copy Link

@raspberrycoulis commented on GitHub (Jan 5, 2026):

hm strange, should be in bashrc. run before: npm install -g pnpm

I'll try it later and report back. I did upgrade from v2 to v3 and had to fix a few things post migration (as opposed to a new install) so that could explain it.

@raspberrycoulis commented on GitHub (Jan 5, 2026): > hm strange, should be in bashrc. run before: npm install -g pnpm I'll try it later and report back. I did upgrade from v2 to v3 and had to fix a few things post migration (as opposed to a new install) so that could explain it.
OVERLORD commented 2026-02-05 04:24:08 +03:00
Author
Owner
Copy Link

@raspberrycoulis commented on GitHub (Jan 5, 2026):

hm strange, should be in bashrc. run before: npm install -g pnpm

So I ran npm install -g pnpm before running the update script and there was no error, but oddly it said no update was available as it is on version 3.0.3 now, so it looks like my original attempt worked despite the error.

@raspberrycoulis commented on GitHub (Jan 5, 2026): > hm strange, should be in bashrc. run before: npm install -g pnpm So I ran `npm install -g pnpm` before running the update script and there was no error, but oddly it said no update was available as it is on version 3.0.3 now, so it looks like my original attempt worked despite the error.
OVERLORD commented 2026-02-05 04:24:10 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 8, 2026):

try to edit /root/.umami and update again

@MickLesk commented on GitHub (Jan 8, 2026): try to edit /root/.umami and update again
OVERLORD commented 2026-02-05 04:24:13 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Jan 9, 2026):

@raspberrycoulis

rm .umami
update
npm install -g pnpm

does that work?

@CrazyWolf13 commented on GitHub (Jan 9, 2026): @raspberrycoulis ```bash rm .umami update npm install -g pnpm ``` does that work?
OVERLORD commented 2026-02-05 04:24:16 +03:00
Author
Owner
Copy Link

@raspberrycoulis commented on GitHub (Jan 9, 2026):

@raspberrycoulis

rm .umami
update
npm install -g pnpm

does that work?

It seemed the initial bash script did work, but I had to start the Umami service manually after. So at the moment, my version is the latest but just had some weirdness with the update.

@raspberrycoulis commented on GitHub (Jan 9, 2026): > @raspberrycoulis > ```bash > rm .umami > update > npm install -g pnpm > ``` > > does that work? It seemed the initial bash script did work, but I had to start the Umami service manually after. So at the moment, my version is the latest but just had some weirdness with the update.
OVERLORD commented 2026-02-05 04:24:20 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Jan 9, 2026):

@raspberrycoulis
okay, so everthing is working now and we can close this issue then?

@CrazyWolf13 commented on GitHub (Jan 9, 2026): @raspberrycoulis okay, so everthing is working now and we can close this issue then?
OVERLORD commented 2026-02-05 04:24:23 +03:00
Author
Owner
Copy Link

@raspberrycoulis commented on GitHub (Jan 9, 2026):

@raspberrycoulis
okay, so everthing is working now and we can close this issue then?

I guess! If I get a similar issue trying the next update, I'll try the steps here but all good now it seems. Thanks.

@raspberrycoulis commented on GitHub (Jan 9, 2026): > @raspberrycoulis > okay, so everthing is working now and we can close this issue then? I guess! If I get a similar issue trying the next update, I'll try the steps here but all good now it seems. Thanks.
OVERLORD commented 2026-02-05 04:24:26 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Jan 9, 2026):

great, sure and if those steps don't solve it just create a new issue again ^^

@CrazyWolf13 commented on GitHub (Jan 9, 2026): great, sure and if those steps don't solve it just create a new issue again ^^
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2285
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?