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 update failed #1030

New Issue
Closed
opened 2026-02-04 22:41:15 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-04 22:41:15 +03:00
Owner
Copy Link

Originally created by @leon47331 on GitHub (May 29, 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?

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📝 Provide a clear and concise description of the issue.

When I try to update the homepage, it starts updating, but at the point "Creating an optimized production build...", it gets stuck and crashes most of the time. Now the Homepage won't work anymore. The output looks like this:

/Latest version:     1.0.30001718
Updating caniuse-lite version
$ pnpm up caniuse-lite
 /caniuse-lite has been successfully updated

No target browser changes
 \Lockfile is up to date, resolution step is skipped
 |Already up to date
 \Done in 938ms using pnpm v10.8.0
 \
> homepage@1.2.0 build /opt/homepage
> next build

 \   ▲ Next.js 15.2.4

 ✓ Linting and checking validity of types    
 /   Creating an optimized production build ...
 -

Sometimes this happens:

✓ Linting and checking validity of types    
   Creating an optimized production build ...
 \ ELIFECYCLE  Command failed.

or:

Next.js build worker exited with code: null and signal: SIGKILL
 - ELIFECYCLE  Command failed with exit code 1.

[ERROR] in line 78: exit code 0: while executing command pnpm build

🔄 Steps to reproduce the issue.

update

❌ Paste the full error output (if available).

The LXC-Container crashes or freezes.

🖼️ Additional context (optional).

No response

Originally created by @leon47331 on GitHub (May 29, 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? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📝 Provide a clear and concise description of the issue. When I try to update the homepage, it starts updating, but at the point "Creating an optimized production build...", it gets stuck and crashes most of the time. Now the Homepage won't work anymore. The output looks like this: ``` /Latest version: 1.0.30001718 Updating caniuse-lite version $ pnpm up caniuse-lite /caniuse-lite has been successfully updated No target browser changes \Lockfile is up to date, resolution step is skipped |Already up to date \Done in 938ms using pnpm v10.8.0 \ > homepage@1.2.0 build /opt/homepage > next build \ ▲ Next.js 15.2.4 ✓ Linting and checking validity of types / Creating an optimized production build ... - ``` Sometimes this happens: ``` ✓ Linting and checking validity of types Creating an optimized production build ... \ ELIFECYCLE  Command failed. ``` or: ``` Next.js build worker exited with code: null and signal: SIGKILL - ELIFECYCLE  Command failed with exit code 1. [ERROR] in line 78: exit code 0: while executing command pnpm build ``` ### 🔄 Steps to reproduce the issue. `update` ### ❌ Paste the full error output (if available). The LXC-Container crashes or freezes. ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 22:41:15 +03:00
OVERLORD commented 2026-02-04 22:41:19 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (May 29, 2025):

Maybe try with more RAM?

@MickLesk commented on GitHub (May 29, 2025): Maybe try with more RAM?
OVERLORD commented 2026-02-04 22:41:25 +03:00
Author
Owner
Copy Link

@leon47331 commented on GitHub (Jun 1, 2025):

I've assigned more RAM and was waiting patiently, and it indeed worked!!

@leon47331 commented on GitHub (Jun 1, 2025): I've assigned more RAM and was waiting patiently, and it indeed worked!!
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#1030
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?