Homepage v1.0.0 - Build Issues #638

Closed
opened 2026-02-04 20:29:53 +03:00 by OVERLORD · 11 comments
Owner

Originally created by @MickLesk on GitHub (Mar 14, 2025).

Originally assigned to: @MickLesk on GitHub.

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.

v1.0.0. released since 1hour. Script doesnt work anymore.

Please dont update now.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

https://github.com/gethomepage/homepage/releases/tag/v1.0.0

Paste the full error output (if available).

⠋Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry

⠙ ▲ Next.js 15.1.7

✓ Linting and checking validity of types
Creating an optimized production build ...
⠧Next.js build worker exited with code: null and signal: SIGKILL
⠇ ELIFECYCLE  Command failed with exit code 1.

[ERROR] in line 48: exit code 0: while executing command $STD pnpm build

🖼️ Additional context (optional).

No response

Originally created by @MickLesk on GitHub (Mar 14, 2025). Originally assigned to: @MickLesk on GitHub. ### ✅ 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. v1.0.0. released since 1hour. Script doesnt work anymore. Please dont update now. ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. https://github.com/gethomepage/homepage/releases/tag/v1.0.0 ### ❌ Paste the full error output (if available). ⠋Attention: Next.js now collects completely anonymous telemetry regarding usage. This information is used to shape Next.js' roadmap and prioritize features. You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: https://nextjs.org/telemetry ⠙ ▲ Next.js 15.1.7 ✓ Linting and checking validity of types Creating an optimized production build ... ⠧Next.js build worker exited with code: null and signal: SIGKILL ⠇ ELIFECYCLE  Command failed with exit code 1. ⠋ [ERROR] in line 48: exit code 0: while executing command $STD pnpm build ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 20:29:53 +03:00
Author
Owner

@jershbytes commented on GitHub (Mar 14, 2025):

Glad I'm not the only one seeing this issue!

@jershbytes commented on GitHub (Mar 14, 2025): Glad I'm not the only one seeing this issue!
Author
Owner

@MickLesk commented on GitHub (Mar 14, 2025):

You need to increase RAM, CPU and DISK (4096/4/7) and it builds, but you need a new variable too

https://github.com/gethomepage/homepage/discussions/4789

@MickLesk commented on GitHub (Mar 14, 2025): You need to increase RAM, CPU and DISK (4096/4/7) and it builds, but you need a new variable too https://github.com/gethomepage/homepage/discussions/4789
Author
Owner

@jershbytes commented on GitHub (Mar 14, 2025):

You need to increase RAM, CPU and DISK (4096/4/7) and it builds, but you need a new variable too

gethomepage/homepage#4789

So I did the first part , was able to to isntall. Issue i seem to be having is if i change the systemd service it jsut fails do we need to make a .env in the root of the folder.

@jershbytes commented on GitHub (Mar 14, 2025): > You need to increase RAM, CPU and DISK (4096/4/7) and it builds, but you need a new variable too > > [gethomepage/homepage#4789](https://github.com/gethomepage/homepage/discussions/4789) So I did the first part , was able to to isntall. Issue i seem to be having is if i change the systemd service it jsut fails do we need to make a .env in the root of the folder.
Author
Owner

@jershbytes commented on GitHub (Mar 14, 2025):

You need to increase RAM, CPU and DISK (4096/4/7) and it builds, but you need a new variable too
gethomepage/homepage#4789

So I did the first part , was able to to isntall. Issue i seem to be having is if i change the systemd service it jsut fails do we need to make a .env in the root of the folder.

That did the trick doing adding .env to /opt/hompeage fixed it.

HOMEPAGE_ALLOWED_HOSTS=localhost:3000
@jershbytes commented on GitHub (Mar 14, 2025): > > You need to increase RAM, CPU and DISK (4096/4/7) and it builds, but you need a new variable too > > [gethomepage/homepage#4789](https://github.com/gethomepage/homepage/discussions/4789) > > So I did the first part , was able to to isntall. Issue i seem to be having is if i change the systemd service it jsut fails do we need to make a .env in the root of the folder. That did the trick doing adding `.env` to `/opt/hompeage` fixed it. ``` HOMEPAGE_ALLOWED_HOSTS=localhost:3000 ```
Author
Owner

@tremor021 commented on GitHub (Mar 14, 2025):

Jesus Christ, its like every release they break something

@tremor021 commented on GitHub (Mar 14, 2025): Jesus Christ, its like every release they break something
Author
Owner

@MickLesk commented on GitHub (Mar 15, 2025):

You need to increase RAM, CPU and DISK (4096/4/7) and it builds, but you need a new variable too
gethomepage/homepage#4789

So I did the first part , was able to to isntall. Issue i seem to be having is if i change the systemd service it jsut fails do we need to make a .env in the root of the folder.

That did the trick doing adding .env to /opt/hompeage fixed it.

HOMEPAGE_ALLOWED_HOSTS=localhost:3000

Yap exactly have fix my own install 2h ago. But Not prepared an Scriptupdate now

@MickLesk commented on GitHub (Mar 15, 2025): > > > You need to increase RAM, CPU and DISK (4096/4/7) and it builds, but you need a new variable too > > > [gethomepage/homepage#4789](https://github.com/gethomepage/homepage/discussions/4789) > > > > So I did the first part , was able to to isntall. Issue i seem to be having is if i change the systemd service it jsut fails do we need to make a .env in the root of the folder. > > That did the trick doing adding `.env` to `/opt/hompeage` fixed it. > > ``` > HOMEPAGE_ALLOWED_HOSTS=localhost:3000 > ``` Yap exactly have fix my own install 2h ago. But Not prepared an Scriptupdate now
Author
Owner

@vhsdream commented on GitHub (Mar 15, 2025):

We can get away with building with 3GB RAM - how does that sound @MickLesk ? I have a fix in waiting.

@vhsdream commented on GitHub (Mar 15, 2025): We can get away with building with 3GB RAM - how does that sound @MickLesk ? I have a fix in waiting.
Author
Owner

@MickLesk commented on GitHub (Mar 15, 2025):

And .env File and service?

@MickLesk commented on GitHub (Mar 15, 2025): And .env File and service?
Author
Owner

@vhsdream commented on GitHub (Mar 15, 2025):

Actually, it appears you don't need to update the service file - just having the .env file by itself works; however localhost:3000 does not work for me, I need to add the LXC IP.

Is that variable that I see in the ct script ($IP) available during the installation script? If so then I can use that to automatically add the machine IP, otherwise we'll have to create another var.

Update: was able to build with 2 CPU, 3GB RAM.

@vhsdream commented on GitHub (Mar 15, 2025): Actually, it appears you don't need to update the service file - just having the .env file by itself works; however `localhost:3000` does not work for me, I need to add the LXC IP. Is that variable that I see in the ct script ($IP) available during the installation script? If so then I can use that to automatically add the machine IP, otherwise we'll have to create another var. Update: was able to build with 2 CPU, 3GB RAM.
Author
Owner

@MickLesk commented on GitHub (Mar 15, 2025):

3GB failed at my n100 dev PC.

export NodeOptions to 2048 maybe helps

@MickLesk commented on GitHub (Mar 15, 2025): 3GB failed at my n100 dev PC. export NodeOptions to 2048 maybe helps
Author
Owner

@tanujdargan commented on GitHub (Mar 15, 2025):

Just about worked with 3GB on my server and I did a workaround for now by adding the env variable to next.config.js.

@tanujdargan commented on GitHub (Mar 15, 2025): Just about worked with 3GB on my server and I did a workaround for now by adding the env variable to next.config.js.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#638