starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Homepage install fails due to pnpm bug #326

New Issue
Closed
opened 2026-02-04 17:58:44 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-04 17:58:44 +03:00
Owner
Copy Link

Originally created by @jaxley on GitHub (Jan 13, 2025).

✅ Have you read and understood the above guidelines?

yes

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

homepage

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/homepage.sh)"

📝 Provide a clear and concise description of the issue.

Installation appears to hang. It will fail eventually and will not complete the install and config. You have to stop the LXC adn run pct destroy <num> and attempt reinstall again.

When I installed with default settings and verbose and was able to see the issue. pnpm is generating a bunch of 429 errors and eventually gives up trying to pnpm install the app.

This appears to be a bug reported https://github.com/pnpm/pnpm/issues/8953

When I added a command to the install script locally to downgrade pnpm to the previous version (as indicated in the issue), it installs fine.

Annoyingly, I tried the original script again and it installed cleanly - so there's some variability in the outcome...Fun!

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Run the installer
Select default with verbose
After the Installed Node.js step, pnpm will start throwing errors.

❌ Paste the full error output (if available).

ERR_PNPM_FETCH_429

🖼️ Additional context (optional).

Here's a diff that forces install of the old pnpm version:

root@pve:~# diff -u homepage0.sh homepage.sh 
--- homepage0.sh        2025-01-13 12:28:31.468399245 -0800
+++ homepage.sh 2025-01-13 12:28:53.942346053 -0800
@@ -36,7 +36,7 @@
     if ! command -v npm >/dev/null 2>&1; then
       echo "Installing NPM..."
       apt-get install -y npm >/dev/null 2>&1
-      npm install -g pnpm >/dev/null 2>&1
+      npm install -g pnpm@9.15.2 >/dev/null 2>&1
       echo "Installed NPM..."
     fi
   fi
@@ -51,6 +51,7 @@
     rm -rf homepage-${RELEASE}
     cd /opt/homepage
     npx --yes update-browserslist-db@latest >/dev/null 2>&1
+    npm install -g pnpm@9.15.2 >/dev/null 2>&1
     pnpm install >/dev/null 2>&1
     export NEXT_PUBLIC_VERSION="v$RELEASE"
     export NEXT_PUBLIC_REVISION="source"
Originally created by @jaxley on GitHub (Jan 13, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? homepage ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/homepage.sh)" ### 📝 Provide a clear and concise description of the issue. Installation appears to hang. It will fail eventually and will not complete the install and config. You have to stop the LXC adn run `pct destroy <num>` and attempt reinstall again. When I installed with default settings and verbose and was able to see the issue. pnpm is generating a bunch of 429 errors and eventually gives up trying to `pnpm install` the app. This appears to be a bug reported https://github.com/pnpm/pnpm/issues/8953 When I added a command to the install script locally to downgrade pnpm to the previous version (as indicated in the issue), it installs fine. Annoyingly, I tried the original script again and it installed cleanly - so there's some variability in the outcome...Fun! ### ⚙️ What settings are you using? - [X] Default Settings - [X] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Run the installer Select default with verbose After the `Installed Node.js` step, pnpm will start throwing errors. ### ❌ Paste the full error output (if available). ERR_PNPM_FETCH_429 ### 🖼️ Additional context (optional). Here's a diff that forces install of the old pnpm version: ``` root@pve:~# diff -u homepage0.sh homepage.sh --- homepage0.sh 2025-01-13 12:28:31.468399245 -0800 +++ homepage.sh 2025-01-13 12:28:53.942346053 -0800 @@ -36,7 +36,7 @@ if ! command -v npm >/dev/null 2>&1; then echo "Installing NPM..." apt-get install -y npm >/dev/null 2>&1 - npm install -g pnpm >/dev/null 2>&1 + npm install -g pnpm@9.15.2 >/dev/null 2>&1 echo "Installed NPM..." fi fi @@ -51,6 +51,7 @@ rm -rf homepage-${RELEASE} cd /opt/homepage npx --yes update-browserslist-db@latest >/dev/null 2>&1 + npm install -g pnpm@9.15.2 >/dev/null 2>&1 pnpm install >/dev/null 2>&1 export NEXT_PUBLIC_VERSION="v$RELEASE" export NEXT_PUBLIC_REVISION="source" ```
OVERLORD added the not a script issue label 2026-02-04 17:58:44 +03:00
OVERLORD commented 2026-02-04 17:58:50 +03:00
Author
Owner
Copy Link

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

pnpm bug. is fixed accorfing to them

@michelroegl-brunner commented on GitHub (Jan 13, 2025): pnpm bug. is fixed accorfing to them
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 not a script issue
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#326
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?