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 13 Packages Projects Releases 10 Wiki Activity

Homarr script location moved but not updated #1601

New Issue
Closed
opened 2026-02-05 01:43:43 +03:00 by OVERLORD · 13 comments
OVERLORD commented 2026-02-05 01:43:43 +03:00
Owner
Copy Link

Originally created by @Lemcott on GitHub (Sep 8, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Homarr

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📈 Which Proxmox version are you on?

9.0.6

📝 Provide a clear and concise description of the issue.

install script calls
https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/homarr.sh

but this is incorrect. updated address below:

https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homarr.sh

This happens with both github and gitea scripts.

🔄 Steps to reproduce the issue.

attempt to install homarr using either github or gitea scripts

❌ Paste the full error output (if available).

✔️ Deployed: homarr (1.36.1)
⠋ Installing Homarr (Patience)
[ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1
⠸ Installing Homarr (Patience)
[ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/install/${var_install}.sh)"

🖼️ Additional context (optional).

No response

Originally created by @Lemcott on GitHub (Sep 8, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Homarr ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homarr.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📈 Which Proxmox version are you on? 9.0.6 ### 📝 Provide a clear and concise description of the issue. install script calls https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/homarr.sh but this is incorrect. updated address below: https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homarr.sh This happens with both github and gitea scripts. ### 🔄 Steps to reproduce the issue. attempt to install homarr using either github or gitea scripts ### ❌ Paste the full error output (if available). ✔️ Deployed: homarr (1.36.1) ⠋ Installing Homarr (Patience) [ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1 ⠸ Installing Homarr (Patience) [ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/install/${var_install}.sh)" ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 01:43:43 +03:00
OVERLORD commented 2026-02-05 01:43:49 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 8, 2025):

What? Its all correct. Its an var.

The issue is not what you think. Run in verbose and you see the error

@MickLesk commented on GitHub (Sep 8, 2025): What? Its all correct. Its an var. The issue is not what you think. Run in verbose and you see the error
OVERLORD commented 2026-02-05 01:43:51 +03:00
Author
Owner
Copy Link

@Lemcott commented on GitHub (Sep 8, 2025):

@MickLesk hope this clears it up, sorry for modifying the links to say homarr:

current, incorrect:
/main/install/${var_install}.sh

change to:
/main/ct/${var_install}.sh

@Lemcott commented on GitHub (Sep 8, 2025): @MickLesk hope this clears it up, sorry for modifying the links to say homarr: current, incorrect: /main/install/${var_install}.sh change to: /main/ct/${var_install}.sh
OVERLORD commented 2026-02-05 01:43:54 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 8, 2025):

How you Update the Script?
With Update? Whats inside of /usr/bin/update? Its an General function, so it should Not Work on thousands of scripts

@MickLesk commented on GitHub (Sep 8, 2025): How you Update the Script? With Update? Whats inside of /usr/bin/update? Its an General function, so it should Not Work on thousands of scripts
OVERLORD commented 2026-02-05 01:43:57 +03:00
Author
Owner
Copy Link

@Lemcott commented on GitHub (Sep 8, 2025):

I don't know how to make it any more clear, sorry? I try to run the github/gitea scripts on the site, it creates the lxc, everything is good, then it goes to install homarr on the LXC and fails:

end of PVE Shell output when running the script:
✔️ Deployed: homarr (1.36.1)
⠋ Installing Homarr (Patience)
[ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1
⠸ Installing Homarr (Patience)
[ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/install/${var_install}.sh)"

you can clearly see the script is attempting to call /main/install/homarr.sh which does not exist and 404's, the script is actually located at /main/ct/homarr.sh I can jump into the container after this failure and homarr is not running.

even just testing in a browser one pulls up the sh, the other 404's. the script calls the one that 404's:
https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homarr.sh
https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/homarr.sh

I'll run it again in verbose mode to show anything else that comes up.

@Lemcott commented on GitHub (Sep 8, 2025): I don't know how to make it any more clear, sorry? I try to run the github/gitea scripts on the site, it creates the lxc, everything is good, then it goes to install homarr on the LXC and fails: end of PVE Shell output when running the script: ✔️ Deployed: homarr (1.36.1) ⠋ Installing Homarr (Patience) [ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1 ⠸ Installing Homarr (Patience) [ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL [https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/install/${var_install}.sh](https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/install/$%7Bvar_install%7D.sh))" you can clearly see the script is attempting to call /main/install/homarr.sh which *does not exist* and 404's, the script is actually located at /main/ct/homarr.sh I can jump into the container after this failure and homarr is not running. even just testing in a browser one pulls up the sh, the other 404's. the script calls the one that 404's: https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homarr.sh https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/homarr.sh I'll run it again in verbose mode to show anything else that comes up.
OVERLORD commented 2026-02-05 01:44:00 +03:00
Author
Owner
Copy Link

@Lemcott commented on GitHub (Sep 8, 2025):

oh wait, I can't. advanced install does not offer verbose, and without it I wont be able to enter static ipv4 so the install will fail in a different way before I can get to that point.

@Lemcott commented on GitHub (Sep 8, 2025): oh wait, I can't. advanced install does not offer verbose, and without it I wont be able to enter static ipv4 so the install will fail in a different way before I can get to that point.
OVERLORD commented 2026-02-05 01:44:02 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 8, 2025):

The call is correct - its an subshell...

Verbose is the Last question in advanced. Try this

@MickLesk commented on GitHub (Sep 8, 2025): The call is correct - its an subshell... Verbose is the Last question in advanced. Try this
OVERLORD commented 2026-02-05 01:44:04 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Sep 8, 2025):

check the build.func, $var_install gets created there. it is the NSAPP variable with -install.sh appended.

None of our scripts would
work if this was broken.

@michelroegl-brunner commented on GitHub (Sep 8, 2025): check the build.func, $var_install gets created there. it is the NSAPP variable with -install.sh appended. None of our scripts would work if this was broken.
OVERLORD commented 2026-02-05 01:44:09 +03:00
Author
Owner
Copy Link

@Lemcott commented on GitHub (Sep 8, 2025):

okay, so assume I'm wrong about the root cause... (I'm not sure why at any point any of the scripts call /main/install/ when tteck moved everything to /main/ct back in 2023? but I guess I'm totally wrong?)

why am I getting this error and how do I resolve it?

@Lemcott commented on GitHub (Sep 8, 2025): okay, so assume I'm wrong about the root cause... (I'm not sure why at any point any of the scripts call /main/install/ when tteck moved everything to /main/ct back in 2023? but I guess I'm totally wrong?) why am I getting this error and how do I resolve it?
OVERLORD commented 2026-02-05 01:44:11 +03:00
Author
Owner
Copy Link

@Lemcott commented on GitHub (Sep 8, 2025):

and no, it is not a networking error. I can ping raw.githubusercontent.com just fine

main/install/ 404's where as main/ct does not.

@Lemcott commented on GitHub (Sep 8, 2025): and no, it is not a networking error. I can ping raw.githubusercontent.com just fine main/install/ 404's where as main/ct does not.
OVERLORD commented 2026-02-05 01:44:14 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 8, 2025):

Without verbose Nobody can Help you. Call the Script in verbose and Post full Output

@MickLesk commented on GitHub (Sep 8, 2025): Without verbose Nobody can Help you. Call the Script in verbose and Post full Output
OVERLORD commented 2026-02-05 01:44:16 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Sep 8, 2025):

You are wrong.
There are two files.
1.) homarr.sh in /ct

This file handels the lxc creation and update of the app.

  1. homarr-install.sh in /install

This handels the app install itself. it gets called in the build.func in line 1150 or so after the lxc is created.

This system is in place since the beginning, we portet that from ttek.

The error you are seeing is just that sonething inside the -insttal script failed not that it is not there. Run im verbose and we can help you.

Here lives the install file: https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/homarr-install.sh

@michelroegl-brunner commented on GitHub (Sep 8, 2025): You are wrong. There are two files. 1.) homarr.sh in /ct This file handels the lxc creation and update of the app. 2. homarr-install.sh in /install This handels the app install itself. it gets called in the build.func in line 1150 or so after the lxc is created. This system is in place since the beginning, we portet that from ttek. The error you are seeing is just that sonething inside the -insttal script failed not that it is not there. Run im verbose and we can help you. Here lives the install file: https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/homarr-install.sh
OVERLORD commented 2026-02-05 01:44:20 +03:00
Author
Owner
Copy Link

@Lemcott commented on GitHub (Sep 8, 2025):

The issue we are now faced with is that the verbose install went through without error, but I ran it again without verbose and it failed the same way. same exact settings save for a different ipv4, container number, and verbose.

So now I have two homarr LXC's where one is completed and works (at least so far) but the other is in the same failed state I experienced previously - not sure if there's anything I can pull from it for you to review before I delete it.

@Lemcott commented on GitHub (Sep 8, 2025): The issue we are now faced with is that the verbose install went through without error, but I ran it again without verbose and it failed the same way. same exact settings save for a different ipv4, container number, and verbose. So now I have two homarr LXC's where one is completed and works (at least so far) but the other is in the same failed state I experienced previously - not sure if there's anything I can pull from it for you to review before I delete it.
OVERLORD commented 2026-02-05 01:44:21 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Sep 8, 2025):

To be totally honest, sometimes it just fails on some stupid things noone can really say why.

If you have the willingnes to try a install without verbose again would be great. Sometimes it breaks when it is run in silent mode.

If it fails again in silent we can have a better look. If it goes through it maybe was just a fluke

@michelroegl-brunner commented on GitHub (Sep 8, 2025): To be totally honest, sometimes it just fails on some stupid things noone can really say why. If you have the willingnes to try a install without verbose again would be great. Sometimes it breaks when it is run in silent mode. If it fails again in silent we can have a better look. If it goes through it maybe was just a fluke
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#1601
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?