Homarr update failed #781

New Issue

OVERLORD · 2026-02-04T21:26:34+03:00

OVERLORD commented

2026-02-04 21:26:34 +03:00

Originally created by @Narkowii on GitHub (Apr 9, 2025).

Originally assigned to: @CrazyWolf13 on GitHub.

✅ Have you read and understood the above guidelines?

yes

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

Homarr LXC

📂 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)"

📝 Provide a clear and concise description of the issue.

update failed

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

update via this code

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

❌ Paste the full error output (if available).

✔️ Services Stopped
✔️ Backup Data
⠏ Updating and rebuilding Homarr to v1.15.0 (Patience) ERROR The following patches were not applied: pretty-print-error
Either remove them from "patchedDependencies" or update them to match packages in your dependencies.
⠋ Updating and rebuilding Homarr to v1.15.0 (Patience)
[ERROR] in line 127: exit code 0: while executing command $STD pnpm install

root@homarr:~#

🖼️ Additional context (optional).

No response

Originally created by @Narkowii on GitHub (Apr 9, 2025). Originally assigned to: @CrazyWolf13 on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Homarr LXC ### 📂 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)" ### 📝 Provide a clear and concise description of the issue. update failed ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. update via this code bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homarr.sh)" ### ❌ Paste the full error output (if available). ✔️ Services Stopped ✔️ Backup Data ⠏ Updating and rebuilding Homarr to v1.15.0 (Patience) ERROR The following patches were not applied: pretty-print-error Either remove them from "patchedDependencies" or update them to match packages in your dependencies. ⠋ Updating and rebuilding Homarr to v1.15.0 (Patience) [ERROR] in line 127: exit code 0: while executing command $STD pnpm install root@homarr:~# ### 🖼️ Additional context (optional). _No response_

OVERLORD added the bug label 2026-02-04 21:26:34 +03:00

OVERLORD closed this issue

2026-02-04 21:26:39 +03:00

OVERLORD commented

2026-02-04 21:26:42 +03:00

@MickLesk commented on GitHub (Apr 9, 2025):

@CrazyWolf13

@MickLesk commented on GitHub (Apr 9, 2025): @CrazyWolf13

OVERLORD commented

2026-02-04 21:26:52 +03:00

@CrazyWolf13 commented on GitHub (Apr 9, 2025):

For me the update worked just fine.

Can you ensure you have enough ressources?

12GB Disk
4 GB RAM
2 CPU

Could you try again?

@CrazyWolf13 commented on GitHub (Apr 9, 2025): For me the update worked just fine. Can you ensure you have enough ressources? - 12GB Disk - 4 GB RAM - 2 CPU Could you try again?

OVERLORD commented

2026-02-04 21:26:56 +03:00

@manuel-rw commented on GitHub (Apr 10, 2025):

Hi, Homarr developer here.
@CrazyWolf13 this is probably caused by 94263c445b/package.json (L76).
Since what Homarr version has this been an issue?
@Meierschlumpf must we update the patch or can we get rid of it entirely?

@manuel-rw commented on GitHub (Apr 10, 2025): Hi, Homarr developer here. @CrazyWolf13 this is probably caused by https://github.com/homarr-labs/homarr/blob/94263c445b8a0d0cdbea70ebe45ef932b426204d/package.json#L76. Since what Homarr version has this been an issue? @Meierschlumpf must we update the patch or can we get rid of it entirely?

OVERLORD commented

2026-02-04 21:26:59 +03:00

@CrazyWolf13 commented on GitHub (Apr 10, 2025):

@manuel-rw
Thanks for joining it here ^^

Let us know if we need to do something :)

I myself didn't experience any issues when updating to 1.15

@Narkowii which version did you try to update from ?

( cat /opt/homarr_version.txt )

@CrazyWolf13 commented on GitHub (Apr 10, 2025): @manuel-rw Thanks for joining it here ^^ Let us know if we need to do something :) I myself didn't experience any issues when updating to 1.15 @Narkowii which version did you try to update from ? ( `cat /opt/homarr_version.txt` )

OVERLORD commented

2026-02-04 21:27:02 +03:00

@Meierschlumpf commented on GitHub (Apr 10, 2025):

We probably could consider removing the patch and the usages of pretty-print-error, but I think we'll need other patches in the future which will result in the same issue. I would guess that the problem could be related to the pnpm version as there was a change in the last few weeks where they changed the hashing algorithm of the patches

@Meierschlumpf commented on GitHub (Apr 10, 2025): We probably could consider removing the patch and the usages of pretty-print-error, but I think we'll need other patches in the future which will result in the same issue. I would guess that the problem could be related to the pnpm version as there was a change in the last few weeks where they changed the hashing algorithm of the patches

OVERLORD commented

2026-02-04 21:27:06 +03:00

@manuel-rw commented on GitHub (Apr 10, 2025):

Good point. @CrazyWolf13 how do you ensure that the pnpm version meets the package requirement too? You should use the exact same version whenever possible

@manuel-rw commented on GitHub (Apr 10, 2025): Good point. @CrazyWolf13 how do you ensure that the pnpm version meets the package requirement too? You should use the exact same version whenever possible

OVERLORD commented

2026-02-04 21:27:11 +03:00

@MickLesk commented on GitHub (Apr 10, 2025):

We take a manual look after big releases in Dockerfile/Package.json If it marked in Changelog. Of course, this doesn't always work. I am currently building a core function in the development project that updates things relatively easily with 1 line (NODE_VERSION & NODE_MODULES). But there is still a residual risk, as we cannot monitor all 330 repos permanently.

@MickLesk commented on GitHub (Apr 10, 2025): We take a manual look after big releases in Dockerfile/Package.json If it marked in Changelog. Of course, this doesn't always work. I am currently building a core function in the development project that updates things relatively easily with 1 line (NODE_VERSION & NODE_MODULES). But there is still a residual risk, as we cannot monitor all 330 repos permanently.

OVERLORD commented

2026-02-04 21:27:15 +03:00

@Theahlmightyx1 commented on GitHub (Apr 10, 2025):

I as well am having the exact same error when updating.

@Theahlmightyx1 commented on GitHub (Apr 10, 2025): I as well am having the exact same error when updating.

OVERLORD commented

2026-02-04 21:27:18 +03:00

@Narkowii commented on GitHub (Apr 10, 2025):

@CrazyWolf13

@Narkowii which version did you try to update from ?

( cat /opt/homarr_version.txt )

v1.12.0 to v1.15.10

@Narkowii commented on GitHub (Apr 10, 2025): @CrazyWolf13 > > [@Narkowii](https://github.com/Narkowii) which version did you try to update from ? > > ( `cat /opt/homarr_version.txt` ) v1.12.0 to v1.15.10

OVERLORD commented

2026-02-04 21:27:23 +03:00

@niicholai commented on GitHub (Apr 11, 2025):

Edit: changed what Node version you want to see.

Not sure if this is the correct way to go about it (wait for a Dev to see this and confirm it's fine before trying, follow me at your own risk as I'm still learning myself), but I was coming from 5 updates behind getting the same issue. "Update" gave the following output:

✔️ Services Stopped
✔️ Backup Data
⠙ Updating and rebuilding Homarr to v1.15.0 (Patience) ERROR Failed to switch pnpm to v10.8.0. Looks like pnpm CLI is missing at "/root/.local/share/pnpm/.tools/pnpm/10.8.0/bin" or is incorrect
spawnSync /root/.local/share/pnpm/.tools/pnpm/10.8.0/bin/pnpm ENOENT
⠹ Updating and rebuilding Homarr to v1.15.0 (Patience)
[ERROR] in line 127: exit code 0: while executing command $STD pnpm install

After looking through this issue and looking at what changed on the Homarr GitHub, I fixed this on my end by:

(Inside the LXC for Homarr)

To ensure node version is v22.14 or higher (if lower you need to update it):
node -v
Followed by:
corepack enable
And:
corepack prepare pnpm@10.8.0 --activate
Finally (to test if it worked):
pnpm --version
Since they moved from yarn to pnpm I then:
npm uninstall -g yarn
Followed by:
corepack disable yarn
To test if it worked (should get command not found):
yarn --version
Time to update!
update
Reboot after it finishes.
Homarr is now updated and running fine.

Like I said, not sure if that's the way it's supposed to be done, or if this will cause any issues in the future, so anyone reading this may want to wait for a Script Dev volunteer and/or the Homarr dev to confirm this won't bork anything before trying.

@niicholai commented on GitHub (Apr 11, 2025): Edit: changed what Node version you want to see. Not sure if this is the correct way to go about it **_(wait for a Dev to see this and confirm it's fine before trying, follow me at your own risk as I'm still learning myself)_**, but I was coming from 5 updates behind getting the same issue. "Update" gave the following output: ✔️ Services Stopped ✔️ Backup Data ⠙ Updating and rebuilding Homarr to v1.15.0 (Patience) ERROR Failed to switch pnpm to v10.8.0. Looks like pnpm CLI is missing at "/root/.local/share/pnpm/.tools/pnpm/10.8.0/bin" or is incorrect spawnSync /root/.local/share/pnpm/.tools/pnpm/10.8.0/bin/pnpm ENOENT ⠹ Updating and rebuilding Homarr to v1.15.0 (Patience) [ERROR] in line 127: exit code 0: while executing command $STD pnpm install After looking through this issue and looking at what changed on the Homarr GitHub, I fixed this on my end by: (Inside the LXC for Homarr) 1. To ensure node version is v22.14 or higher (if lower you need to update it): `node -v` 2. Followed by: `corepack enable` 3. And: `corepack prepare pnpm@10.8.0 --activate` 4. Finally (to test if it worked): `pnpm --version` 5. Since they moved from yarn to pnpm I then: `npm uninstall -g yarn` 6. Followed by: `corepack disable yarn` 7. To test if it worked (should get command not found): `yarn --version` 8. Time to update! `update` 9. Reboot after it finishes. 10. Homarr is now updated and running fine. Like I said, not sure if that's the way it's supposed to be done, or if this will cause any issues in the future, so anyone reading this may want to wait for a Script Dev volunteer and/or the Homarr dev to confirm this won't bork anything before trying.

OVERLORD commented

2026-02-04 21:27:32 +03:00

@Narkowii commented on GitHub (Apr 11, 2025):

@niicholai

It works for me too !
Thanks !!

@Narkowii commented on GitHub (Apr 11, 2025): @niicholai It works for me too ! Thanks !!

OVERLORD commented

2026-02-04 21:27:34 +03:00

@manuel-rw commented on GitHub (Apr 11, 2025):

Not sure if this is the correct way to go about it (wait for a Dev to see this and confirm it's fine before trying, follow me at your own risk as I'm still learning myself), but I was coming from 5 updates behind getting the same issue. "Update" gave the following output:

✔️ Services Stopped ✔️ Backup Data ⠙ Updating and rebuilding Homarr to v1.15.0 (Patience) ERROR Failed to switch pnpm to v10.8.0. Looks like pnpm CLI is missing at "/root/.local/share/pnpm/.tools/pnpm/10.8.0/bin" or is incorrect spawnSync /root/.local/share/pnpm/.tools/pnpm/10.8.0/bin/pnpm ENOENT ⠹ Updating and rebuilding Homarr to v1.15.0 (Patience) [ERROR] in line 127: exit code 0: while executing command $STD pnpm install

After looking through this issue and looking at what changed on the Homarr GitHub, I fixed this on my end by:

(Inside the LXC for Homarr)
1. To ensure node version is v16.13.0 or higher:
   `node -v`

2. Followed by:
   `corepack enable`

3. And:
   `corepack prepare pnpm@10.8.0 --activate`

4. Finally (to test if it worked):
   `pnpm --version`

5. Since they moved from yarn to pnpm I then:
   `npm uninstall -g yarn`

6. Followed by:
   `corepack disable yarn`

7. To test if it worked (should get command not found):
   `yarn --version`

8. Time to update!
   `update`

9. Reboot after it finishes.

10. Homarr is now updated and running fine.
Like I said, not sure if that's the way it's supposed to be done, or if this will cause any issues in the future, so anyone reading this may want to wait for a Script Dev volunteer and/or the Homarr dev to confirm this won't bork anything before trying.

Hi, thanks for the comment.
You're correct that you should never use yarn any more with Homarr.
It's very likely, that our update to pnpm 10.8.0 caused this - that would also make sense on a timeline perspective.
Your fix shouldn't cause any issues, except that we require Node.js 22 or higher at the moment:

d6a48d132a/package.json (L58)

Using an earlier version could lead to memory leaks, unstability and crashes.
In fact, Node.js 16 has been EoL (End of life) since 2023: https://nodejs.org/en/about/previous-releases, https://github.com/nodejs/release#release-schedul
Lots of CVE's have been discovered after 2023 in that version, hence we strongly recommend you to upgrade: https://security.snyk.io/package/linux/almalinux%3A8/nodejs%3A16%2Fnodejs

I cannot verify whether this will break anything in the script, but as long as you use the correct versions (pnpm =10.8.0 and node.js >=22.14.0), it should be fine.
I also investigated a bit more deeply yesterday and couldn't reproduce this in any of our other installation methods - which leads me to believe that the script is incorrectly using the package manager or has mismatched versions. We always bundle the dependencies directly with our images, but since Proxmox installs from source, it can easily lead to mismatches.

@MickLesk can you also elaborate on your dependency upgrade strategy? I noticed that you did not pin pnpm to a version tag: 1cc8b93fc2/install/homarr-install.sh (L38)
This could result in issues when we do not upgrade due to CVEs or compatibility issues on our side.
And as mentioned, pnpm officially recommends corepack over npm: https://pnpm.io/installation#using-corepack
My guess why is that corepack uses the version specified in package.json - but please correct me on this if you have more info.

Let me know if I can answer any other questions or how we can assist with finding a fix for the script.

@manuel-rw commented on GitHub (Apr 11, 2025): > Not sure if this is the correct way to go about it **_(wait for a Dev to see this and confirm it's fine before trying, follow me at your own risk as I'm still learning myself)_**, but I was coming from 5 updates behind getting the same issue. "Update" gave the following output: > > ✔️ Services Stopped ✔️ Backup Data ⠙ Updating and rebuilding Homarr to v1.15.0 (Patience) ERROR Failed to switch pnpm to v10.8.0. Looks like pnpm CLI is missing at "/root/.local/share/pnpm/.tools/pnpm/10.8.0/bin" or is incorrect spawnSync /root/.local/share/pnpm/.tools/pnpm/10.8.0/bin/pnpm ENOENT ⠹ Updating and rebuilding Homarr to v1.15.0 (Patience) [ERROR] in line 127: exit code 0: while executing command $STD pnpm install > > After looking through this issue and looking at what changed on the Homarr GitHub, I fixed this on my end by: > > (Inside the LXC for Homarr) > > 1. To ensure node version is v16.13.0 or higher: > `node -v` > > 2. Followed by: > `corepack enable` > > 3. And: > `corepack prepare pnpm@10.8.0 --activate` > > 4. Finally (to test if it worked): > `pnpm --version` > > 5. Since they moved from yarn to pnpm I then: > `npm uninstall -g yarn` > > 6. Followed by: > `corepack disable yarn` > > 7. To test if it worked (should get command not found): > `yarn --version` > > 8. Time to update! > `update` > > 9. Reboot after it finishes. > > 10. Homarr is now updated and running fine. > > > Like I said, not sure if that's the way it's supposed to be done, or if this will cause any issues in the future, so anyone reading this may want to wait for a Script Dev volunteer and/or the Homarr dev to confirm this won't bork anything before trying. Hi, thanks for the comment. You're correct that you should never use ``yarn`` any more with Homarr. It's very likely, that [our update to pnpm 10.8.0](https://github.com/homarr-labs/homarr/pull/2820) caused this - that would also make sense on a timeline perspective. Your fix shouldn't cause any issues, except that **we require Node.js 22 or higher** at the moment: https://github.com/homarr-labs/homarr/blob/d6a48d132a55ce28f3c07ec0da219f7f45b76637/package.json#L58 Using an earlier version could lead to memory leaks, unstability and crashes. **In fact, Node.js 16 has been EoL (End of life) since 2023**: https://nodejs.org/en/about/previous-releases, https://github.com/nodejs/release#release-schedul Lots of CVE's have been discovered after 2023 in that version, hence we strongly recommend you to upgrade: https://security.snyk.io/package/linux/almalinux%3A8/nodejs%3A16%2Fnodejs I cannot verify whether this will break anything in the script, but as long as you use the correct versions (``pnpm =10.8.0`` and ``node.js >=22.14.0``), it should be fine. I also investigated a bit more deeply yesterday and couldn't reproduce this in any of our other installation methods - which leads me to believe that the script is incorrectly using the package manager or has mismatched versions. We always bundle the dependencies directly with our images, but since Proxmox installs from source, it can easily lead to mismatches. @MickLesk can you also elaborate on your dependency upgrade strategy? I noticed that you did not pin ``pnpm`` to a version tag: https://github.com/community-scripts/ProxmoxVE/blob/1cc8b93fc2e8139e63e10d203007a9da65f33103/install/homarr-install.sh#L38 This could result in issues when we do not upgrade due to CVEs or compatibility issues on our side. And as mentioned, ``pnpm`` officially recommends ``corepack`` over ``npm``: https://pnpm.io/installation#using-corepack My guess why is that corepack uses the version specified in ``package.json`` - but please correct me on this if you have more info. Let me know if I can answer any other questions or how we can assist with finding a fix for the script.

OVERLORD commented

2026-02-04 21:27:39 +03:00

@niicholai commented on GitHub (Apr 11, 2025):

@manuel-rw That makes sense about Node. I'm on 22.14, I'll edit my comment so people in the future do not get confused!

@niicholai commented on GitHub (Apr 11, 2025): @manuel-rw That makes sense about Node. I'm on 22.14, I'll edit my comment so people in the future do not get confused!

OVERLORD commented

2026-02-04 21:27:43 +03:00

@manuel-rw commented on GitHub (Apr 16, 2025):

@CrazyWolf13 has this been resolved? Is there any further input from our side needed?
If not, can we close this issue?
As mentioned, we do not run any Proxmox based setups and have no testing in this segment.

@manuel-rw commented on GitHub (Apr 16, 2025): @CrazyWolf13 has this been resolved? Is there any further input from our side needed? If not, can we close this issue? As mentioned, we do not run any Proxmox based setups and have no testing in this segment.

OVERLORD commented

2026-02-04 21:27:47 +03:00

@Theahlmightyx1 commented on GitHub (Apr 16, 2025):

@CrazyWolf13 has this been resolved? Is there any further input from our side needed?
If not, can we close this issue?
As mentioned, we do not run any Proxmox based setups and have no testing in this segment.

Yes the above guide posted fixed it for me. Thank you !

@Theahlmightyx1 commented on GitHub (Apr 16, 2025): > @CrazyWolf13 has this been resolved? Is there any further input from our side needed? > If not, can we close this issue? > As mentioned, we do not run any Proxmox based setups and have no testing in this segment. Yes the above guide posted fixed it for me. Thank you !

OVERLORD commented

2026-02-04 21:27:54 +03:00

@manuel-rw commented on GitHub (Apr 16, 2025):

@CrazyWolf13 has this been resolved? Is there any further input from our side needed?
If not, can we close this issue?
As mentioned, we do not run any Proxmox based setups and have no testing in this segment.

Yes the above guide posted fixed it for me. Thank you !

Glad that you were able to fix it, but the idea would be that the script works out of the box (at least that is my understanding).
Hence we should implement the fix in the script itself and not document this here in this random issue.

@manuel-rw commented on GitHub (Apr 16, 2025): > > [@CrazyWolf13](https://github.com/CrazyWolf13) has this been resolved? Is there any further input from our side needed? > > If not, can we close this issue? > > As mentioned, we do not run any Proxmox based setups and have no testing in this segment. > > Yes the above guide posted fixed it for me. Thank you ! Glad that you were able to fix it, but the idea would be that the script works out of the box (at least that is my understanding). Hence we should implement the fix in the script itself and not document this here in this random issue.

OVERLORD commented

2026-02-04 21:27:57 +03:00

@Theahlmightyx1 commented on GitHub (Apr 16, 2025):

@CrazyWolf13 has this been resolved? Is there any further input from our side needed?
If not, can we close this issue?
As mentioned, we do not run any Proxmox based setups and have no testing in this segment.

Yes the above guide posted fixed it for me. Thank you !

Glad that you were able to fix it, but the idea would be that the script works out of the box (at least that is my understanding).
Hence we should implement the fix in the script itself and not document this here in this random issue.

Ahh sorry I misunderstood. And that makes complete sense.

Doing the manual updates via the cli that the users above provided fixed it for me, as for moving forward for new updates I'm not sure it's a permanent fix. As in simply running "update" in the cli will update the container successfull.

With my minimal scripting knowledge, I would say there's a good chance the OP error that I also got could potentially occur again on future updates. So further fixing might need some on the script... sorry if that doesn't answer your question let me know and I can test on another node.

Edit:
i threw the update and install scripts at chatGPT and it said:

No corepack enable anywhere
If you update Node.js or the LXC base image changes, corepack can get disabled silently. The update script doesn’t re-enable it.

No pnpm install check or fallback
If pnpm is missing, corrupt, or unlinked, the script just bombs on pnpm install and doesn't tell you why.

No global package repair/validation
It assumes pnpm just works™. If pretty-print-error or any other dependency is borked, the update will fail but quietly.

which would make sense from what i had to do to fix it via niicholai's help.

hopefully this helps answer your question better. Sorry again im not good at coding hah

@Theahlmightyx1 commented on GitHub (Apr 16, 2025): > > > [@CrazyWolf13](https://github.com/CrazyWolf13) has this been resolved? Is there any further input from our side needed? > > > If not, can we close this issue? > > > As mentioned, we do not run any Proxmox based setups and have no testing in this segment. > > > > Yes the above guide posted fixed it for me. Thank you ! > > Glad that you were able to fix it, but the idea would be that the script works out of the box (at least that is my understanding). > Hence we should implement the fix in the script itself and not document this here in this random issue. Ahh sorry I misunderstood. And that makes complete sense. Doing the manual updates via the cli that the users above provided fixed it for me, as for moving forward for new updates I'm not sure it's a permanent fix. As in simply running "update" in the cli will update the container successfull. With my minimal scripting knowledge, I would say there's a good chance the OP error that I also got could potentially occur again on future updates. So further fixing might need some on the script... sorry if that doesn't answer your question let me know and I can test on another node. Edit: i threw the update and install scripts at chatGPT and it said: No corepack enable anywhere If you update Node.js or the LXC base image changes, corepack can get disabled silently. The update script doesn’t re-enable it. No pnpm install check or fallback If pnpm is missing, corrupt, or unlinked, the script just bombs on pnpm install and doesn't tell you why. No global package repair/validation It assumes pnpm just works™. If pretty-print-error or any other dependency is borked, the update will fail but quietly. which would make sense from what i had to do to fix it via niicholai's help. hopefully this helps answer your question better. Sorry again im not good at coding hah

OVERLORD commented

2026-02-04 21:28:03 +03:00

@CrazyWolf13 commented on GitHub (Apr 17, 2025):

Hi @manuel-rw

I think before I hack something together, we wait for the streamlined function by @MickLesk I think he already got that function in our DEV repo (ProxmoxVED) ready.

In the meantime we'll keep the below commands to overcome this manually, until @MickLesk has the function ready:

corepack enable
corepack prepare pnpm@10.8.0 --activate

Weirdly enough I didn't yet experience this problem, but my installation was one of the first ones too.

So you @manuel-rw suggest enabling corepack for pnpm?
This would mean "uninstalling pnpm" installing corepack and then enabling pnpm through corepack?

Why do you still pin the version, if https://github.com/nodejs/corepack/issues/612 is resolved?
https://github.com/homarr-labs/homarr/blob/dev/Dockerfile

Also I'm not that far into this node stuff, so I appreciate your input here :)

@CrazyWolf13 commented on GitHub (Apr 17, 2025): Hi @manuel-rw I think before I hack something together, we wait for the streamlined function by @MickLesk I think he already got that function in our DEV repo (ProxmoxVED) ready. In the meantime we'll keep the below commands to overcome this manually, until @MickLesk has the function ready: ```bash corepack enable corepack prepare pnpm@10.8.0 --activate ``` Weirdly enough I didn't yet experience this problem, but my installation was one of the first ones too. So you @manuel-rw suggest enabling corepack for pnpm? This would mean "uninstalling pnpm" installing corepack and then enabling pnpm through corepack? Why do you still pin the version, if https://github.com/nodejs/corepack/issues/612 is resolved? https://github.com/homarr-labs/homarr/blob/dev/Dockerfile Also I'm not that far into this node stuff, so I appreciate your input here :)

OVERLORD commented

2026-02-04 21:28:09 +03:00

@manuel-rw commented on GitHub (Apr 25, 2025):

See here:
e1e26b27de/package.json (L56)
We enforce the exact version there and let the package managers do the rest.
You could extract this version in your scripts and install that specific version explicitly or let corepack handle it.
See https://stackoverflow.com/a/72825528
Also works with npm and yarn: (npm|pnpm|yarn)@\d+\.\d+\.\d+(-.+)?

@manuel-rw commented on GitHub (Apr 25, 2025): See here: https://github.com/homarr-labs/homarr/blob/e1e26b27ded3012eb87711bc644fd71a801c6639/package.json#L56 We enforce the exact version there and let the package managers do the rest. You could extract this version in your scripts and install that specific version explicitly or let corepack handle it. See https://stackoverflow.com/a/72825528 Also works with ``npm`` and ``yarn``: ``(npm|pnpm|yarn)@\d+\.\d+\.\d+(-.+)?``

OVERLORD commented

2026-02-04 21:28:13 +03:00

@Theahlmightyx1 commented on GitHub (May 9, 2025):

Trying to update again, followed the guides in this issue's thread do not work this time sadly.
Maybe I am not being patient enough but I swear I've waited close to 30ish minutes and it hangs at

⠋ Updating and rebuilding Homarr to v1.19.0 (Patience)

currently on: v1.16.0

@Theahlmightyx1 commented on GitHub (May 9, 2025): Trying to update again, followed the guides in this issue's thread do not work this time sadly. Maybe I am not being patient enough but I swear I've waited close to 30ish minutes and it hangs at `⠋ Updating and rebuilding Homarr to v1.19.0 (Patience)` currently on: v1.16.0

OVERLORD commented

2026-02-04 21:28:17 +03:00

@jjw867 commented on GitHub (May 12, 2025):

May be related, but installation and update of Homarr now results in this:

...
✔️ Core dependencies installed
✔️ Installed Dependencies
✔️ Installed Node.js 22
✔️ All requested Node modules have been processed
curl: (22) The requested URL returned error: 404
✖️ Failed to download release asset from https://github.com/homarr-labs/homarr/archive/refs/tags/1.19.1.tar.gz

[ERROR] in line 33: exit code 0: while executing command return 1
/dev/fd/63: line 72: SPINNER_PID: unbound variable

@jjw867 commented on GitHub (May 12, 2025): May be related, but installation and update of Homarr now results in this: ... ✔️ Core dependencies installed ✔️ Installed Dependencies ✔️ Installed Node.js 22 ✔️ All requested Node modules have been processed curl: (22) The requested URL returned error: 404 ✖️ Failed to download release asset from https://github.com/homarr-labs/homarr/archive/refs/tags/1.19.1.tar.gz [ERROR] in line 33: exit code 0: while executing command return 1 /dev/fd/63: line 72: SPINNER_PID: unbound variable

OVERLORD commented

2026-02-04 21:28:25 +03:00

@manuel-rw commented on GitHub (May 13, 2025):

@CrazyWolf13 you're missing the v prefix in the tag. The correct URL would be https://github.com/homarr-labs/homarr/archive/refs/tags/v1.19.1.tar.gz .

@manuel-rw commented on GitHub (May 13, 2025): @CrazyWolf13 you're missing the ``v`` prefix in the tag. The correct URL would be https://github.com/homarr-labs/homarr/archive/refs/tags/v1.19.1.tar.gz .

OVERLORD commented

2026-02-04 21:28:30 +03:00

@CrazyWolf13 commented on GitHub (May 13, 2025):

@manuel-rw
yes we are working on it, @MickLesk 's function is outdated on this repo, we need to push changes from or DEV repo to here.

@CrazyWolf13 commented on GitHub (May 13, 2025): @manuel-rw yes we are working on it, @MickLesk 's function is outdated on this repo, we need to push changes from or DEV repo to here.

OVERLORD commented

2026-02-04 21:28:32 +03:00

@yokho commented on GitHub (May 13, 2025):

Hello everyone,
I tried to update this morning and had the same issue described by @jjw867 (401 error due to incorrect url)
the state of the LXC homarr installation seems to be broken, the homarr service is no longer detected by the following script ➡️bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/homarr.sh)" , i receive this message "✖️ No Homarr Installation Found! "

❓ Can you assist rebuilding the homarr installation within the LXC without having to redeploy a new one ? ( i'm quite new to LXC's and community-scripts)

Due to this failed update i'm also checking what I should backup in case of another occurence. If i need to rebuild a new LXC from scratch and import the configurations from a previous instance what are the required config files to move ?
/opt/homarr_db 📁
/opt/homarr-data-backup/.env 📄

@yokho commented on GitHub (May 13, 2025): Hello everyone, I tried to update this morning and had the same issue described by @jjw867 (401 error due to incorrect url) the state of the LXC homarr installation seems to be broken, the homarr service is no longer detected by the following script ➡️bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/homarr.sh)" , i receive this message "✖️ No Homarr Installation Found! " ❓ Can you assist rebuilding the homarr installation within the LXC without having to redeploy a new one ? ( i'm quite new to LXC's and community-scripts) Due to this failed update i'm also checking what I should backup in case of another occurence. If i need to rebuild a new LXC from scratch and import the configurations from a previous instance what are the required config files to move ? /opt/homarr_db 📁 /opt/homarr-data-backup/.env 📄

OVERLORD commented

2026-02-04 21:28:35 +03:00

@CrazyWolf13 commented on GitHub (May 13, 2025):

@yokho
I always recommend a full lxc backup always, never do updates without proper backup first.

Ensure to backup the current lxc if not already done that (daily backup via Proxmox Backup Server works well for me)

Then try the following:

mkdir -p /opt/homarr
update

@CrazyWolf13 commented on GitHub (May 13, 2025): @yokho I always recommend a full lxc backup always, never do updates without proper backup first. Ensure to backup the current lxc if not already done that (daily backup via Proxmox Backup Server works well for me) Then try the following: ```bash mkdir -p /opt/homarr update ```

OVERLORD commented

2026-02-04 21:28:37 +03:00

@yokho commented on GitHub (May 13, 2025):

@yokho I always recommend a full lxc backup always, never do updates without proper backup first.

Ensure to backup the current lxc if not already done that (daily backup via Proxmox Backup Server works well for me)

Then try the following:

mkdir -p /opt/homarr
update

Thanks for the reply @CrazyWolf13 , duly noted on top of my documentation to snapshot everything before updating :D

Regarding the fix it seems to be a little different as the update expect the .env inside the homarr directory, so i cp'ed the homarr-data-backup to homarr
But then the local update script has the issue reported earlier, the tag version lacks the "v" in front of the latest homarr version
update output : curl: (22) The requested URL returned error: 404 ✖️ Failed to download release asset from https://github.com/homarr-labs/homarr/archive/refs/tags/1.19.1.tar.gz

i tried your new branch for the fix over here : https://raw.githubusercontent.com/community-scripts/ProxmoxVE/refs/heads/update_tools.func/ct/homarr.sh
and retried the update via the the classic : bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/homarr.sh)"

Correct me if i'm wrong but it seems that the way the RELEASE variable is filled is returning the shortened version number therefore failing to build the full url for the last homarr release

@yokho commented on GitHub (May 13, 2025): > [@yokho](https://github.com/yokho) I always recommend a full lxc backup always, never do updates without proper backup first. > > Ensure to backup the current lxc if not already done that (daily backup via Proxmox Backup Server works well for me) > > Then try the following: > > mkdir -p /opt/homarr > update Thanks for the reply @CrazyWolf13 , duly noted on top of my documentation to snapshot everything before updating :D Regarding the fix it seems to be a little different as the update expect the .env inside the homarr directory, so i cp'ed the homarr-data-backup to homarr But then the local update script has the issue reported earlier, the tag version lacks the "v" in front of the latest homarr version update output : `curl: (22) The requested URL returned error: 404 ✖️ Failed to download release asset from https://github.com/homarr-labs/homarr/archive/refs/tags/1.19.1.tar.gz` i tried your new branch for the fix over here : https://raw.githubusercontent.com/community-scripts/ProxmoxVE/refs/heads/update_tools.func/ct/homarr.sh and retried the update via the the classic : bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/homarr.sh)" Correct me if i'm wrong but it seems that the way the RELEASE variable is filled is returning the shortened version number therefore failing to build the full url for the last homarr release

OVERLORD commented

2026-02-04 21:28:39 +03:00

@KevinGaudry commented on GitHub (May 13, 2025):

May be related, but installation and update of Homarr now results in this:

... ✔️ Core dependencies installed ✔️ Installed Dependencies ✔️ Installed Node.js 22 ✔️ All requested Node modules have been processed curl: (22) The requested URL returned error: 404 ✖️ Failed to download release asset from https://github.com/homarr-labs/homarr/archive/refs/tags/1.19.1.tar.gz

[ERROR] in line 33: exit code 0: while executing command return 1 /dev/fd/63: line 72: SPINNER_PID: unbound variable

Same issue for me here. Installation broken after trying to update. I Had to restore my backup after trying.

@KevinGaudry commented on GitHub (May 13, 2025): > May be related, but installation and update of Homarr now results in this: > > ... ✔️ Core dependencies installed ✔️ Installed Dependencies ✔️ Installed Node.js 22 ✔️ All requested Node modules have been processed curl: (22) The requested URL returned error: 404 ✖️ Failed to download release asset from https://github.com/homarr-labs/homarr/archive/refs/tags/1.19.1.tar.gz > > [ERROR] in line 33: exit code 0: while executing command return 1 /dev/fd/63: line 72: SPINNER_PID: unbound variable Same issue for me here. Installation broken after trying to update. I Had to restore my backup after trying.

OVERLORD commented

2026-02-04 21:28:42 +03:00

@CrazyWolf13 commented on GitHub (May 13, 2025):

HI @jjw867 @KevinGaudry @yokho little update for you.

Due to last minute bugfixes in our dev repo, which were not tested thoroughly before merge, we have this conflict, because homarr team uses a v{VERSION} scheme.

I already fixed the issue in our DEV repo, and we are currently testing the changes.
If we can't identify any issues, we will probably merge it tomorrow or in the following days.
After successful merge, I'll update here as and will post the proper recovery commands.

@CrazyWolf13 commented on GitHub (May 13, 2025): HI @jjw867 @KevinGaudry @yokho little update for you. Due to last minute bugfixes in our dev repo, which were not tested thoroughly before merge, we have this conflict, because homarr team uses a v{VERSION} scheme. I already fixed the issue in our DEV repo, and we are currently testing the changes. If we can't identify any issues, we will probably merge it tomorrow or in the following days. After successful merge, I'll update here as and will post the proper recovery commands.

OVERLORD commented

2026-02-04 21:28:46 +03:00

@CrazyWolf13 commented on GitHub (May 14, 2025):

Hi
Little update for you here, sorry that this is taking so long!

We fixed the issues and now you could in theory update again. BUT
Some things on homarr side are conflicting with the build process, so it may take some additional time till it's fixed.
I'll update here once they resolved it.

For the ones having to recover here the commands:
But only run the update command once I say homarr fixed the issues.

mkdir -p /opt/homarr
cp /opt/homarr-data-backup/.env /opt/homarr/.env
update

@CrazyWolf13 commented on GitHub (May 14, 2025): Hi Little update for you here, sorry that this is taking so long! We fixed the issues and now you could in theory update again. BUT Some things on homarr side are conflicting with the build process, so it may take some additional time till it's fixed. I'll update here once they resolved it. For the ones having to recover here the commands: But only run the update command once I say homarr fixed the issues. ```bash mkdir -p /opt/homarr cp /opt/homarr-data-backup/.env /opt/homarr/.env update ```

OVERLORD commented

2026-02-04 21:28:50 +03:00

@manuel-rw commented on GitHub (May 14, 2025):

Can confirm that we're on it. Don't know why this wasn't caught by testing, but we'll make sure to prevent such build issues with automated testing. I am going to update you once we fixed the build on our issue. Other installation methods besides Proxmox are unaffected.

@manuel-rw commented on GitHub (May 14, 2025): Can confirm that we're on it. Don't know why this wasn't caught by testing, but we'll make sure to prevent such build issues with automated testing. I am going to update you once we fixed the build on our issue. Other installation methods besides Proxmox are unaffected.

OVERLORD commented

2026-02-04 21:28:54 +03:00

@guus2006 commented on GitHub (May 16, 2025):

A fresh install also seems to be broken:

✔️ Installed Node.js 22
✔️ All requested Node modules have been processed
⠹ Installing Homarr (Patience)
[ERROR] in line 51: exit code 0: while executing command "$@" > /dev/null 2>&1
curl: (22) The requested URL returned error: 400
/dev/fd/63: line 73: SPINNER_PID: unbound variable

@guus2006 commented on GitHub (May 16, 2025): A fresh install also seems to be broken: ✔️ Installed Node.js 22 ✔️ All requested Node modules have been processed ⠹ Installing Homarr (Patience) [ERROR] in line 51: exit code 0: while executing command "$@" > /dev/null 2>&1 curl: (22) The requested URL returned error: 400 /dev/fd/63: line 73: SPINNER_PID: unbound variable

OVERLORD commented

2026-02-04 21:29:02 +03:00

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

if you read the comments before, you see it ^^

@MickLesk commented on GitHub (May 16, 2025): if you read the comments before, you see it ^^

OVERLORD commented

2026-02-04 21:29:08 +03:00

@netwz commented on GitHub (May 16, 2025):

[ERROR] in line 33: exit code 0: while executing command return 1
/dev/fd/63: line 72: SPINNER_PID: unbound variable

for me, the new install fails with:

packages/definitions postinstall$ tsx ./src/docs/codegen.ts
└─│ sh: 1: tsx: not found
└─ Running...
ELIFECYCLE Command failed.
⠦
[ERROR] in line 50: exit code 0: while executing command $STD pnpm install
The silent function has suppressed the error, run the script with verbose mode enabled, which will provide more detailed output.

⠹/dev/fd/63: line 73: SPINNER_PID: unbound variable

same, same but different, right ;-)

@netwz commented on GitHub (May 16, 2025): > [ERROR] in line 33: exit code 0: while executing command return 1 > /dev/fd/63: line 72: SPINNER_PID: unbound variable for me, the new install fails with: packages/definitions postinstall$ tsx ./src/docs/codegen.ts └─│ sh: 1: tsx: not found └─ Running... ELIFECYCLE Command failed. ⠦ [ERROR] in line 50: exit code 0: while executing command $STD pnpm install The silent function has suppressed the error, run the script with verbose mode enabled, which will provide more detailed output. ⠹/dev/fd/63: line 73: SPINNER_PID: unbound variable same, same but different, right ;-)

OVERLORD commented

2026-02-04 21:29:12 +03:00

@n3rddoom commented on GitHub (May 16, 2025):

[ERROR] in line 33: exit code 0: while executing command return 1
/dev/fd/63: line 72: SPINNER_PID: unbound variable

for me, the new install fails with:

packages/definitions postinstall$ tsx ./src/docs/codegen.ts └─│ sh: 1: tsx: not found └─ Running... ELIFECYCLE Command failed. ⠦ [ERROR] in line 50: exit code 0: while executing command $STD pnpm install The silent function has suppressed the error, run the script with verbose mode enabled, which will provide more detailed output.

⠹/dev/fd/63: line 73: SPINNER_PID: unbound variable

same, same but different, right ;-)

I got sort of tha same error:

╭ Warning ───────────────────────────────────────────────────────────────────────────────────╮
│ │
│ Ignored build scripts: deasync, nice-napi. │
│ Run "pnpm approve-builds" to pick which dependencies should be allowed to run scripts. │
│ │
╰────────────────────────────────────────────────────────────────────────────────────────────╯
⠇
packages/definitions postinstall$ tsx ./src/docs/codegen.ts
│ sh: 1: tsx: not found
└─ Running...
⠼ ELIFECYCLE Command failed.
⠙
[ERROR] in line 50: exit code 0: while executing command $STD pnpm install
The silent function has suppressed the error, run the script with verbose mode enabled, which will provide more detailed output.

⠴/dev/fd/63: line 73: SPINNER_PID: unbound variable

@n3rddoom commented on GitHub (May 16, 2025): > > [ERROR] in line 33: exit code 0: while executing command return 1 > > /dev/fd/63: line 72: SPINNER_PID: unbound variable > > for me, the new install fails with: > > packages/definitions postinstall$ tsx ./src/docs/codegen.ts └─│ sh: 1: tsx: not found └─ Running... ELIFECYCLE Command failed. ⠦ [ERROR] in line 50: exit code 0: while executing command $STD pnpm install The silent function has suppressed the error, run the script with verbose mode enabled, which will provide more detailed output. > > ⠹/dev/fd/63: line 73: SPINNER_PID: unbound variable > > same, same but different, right ;-) I got sort of tha same error: ╭ Warning ───────────────────────────────────────────────────────────────────────────────────╮ │ │ │ Ignored build scripts: deasync, nice-napi. │ │ Run "pnpm approve-builds" to pick which dependencies should be allowed to run scripts. │ │ │ ╰────────────────────────────────────────────────────────────────────────────────────────────╯ ⠇ packages/definitions postinstall$ tsx ./src/docs/codegen.ts │ sh: 1: tsx: not found └─ Running... ⠼ ELIFECYCLE Command failed. ⠙ [ERROR] in line 50: exit code 0: while executing command $STD pnpm install The silent function has suppressed the error, run the script with verbose mode enabled, which will provide more detailed output. ⠴/dev/fd/63: line 73: SPINNER_PID: unbound variable

OVERLORD commented

2026-02-04 21:29:17 +03:00

@tonyinwi commented on GitHub (May 18, 2025):

A fresh install also seems to be broken:

Can confirm. Anyone have any workarounds?

@tonyinwi commented on GitHub (May 18, 2025): > A fresh install also seems to be broken: Can confirm. Anyone have any workarounds?

OVERLORD commented

2026-02-04 21:29:22 +03:00

@CrazyWolf13 commented on GitHub (May 18, 2025):

PR is merged, I tested it successfully.
You should be able to update just fine using the update command.

If your LXC is in broken state, do the following:

mkdir -p /opt/homarr
cp /opt/homarr-data-backup/.env /opt/homarr/.env
update

and as a general advice, always do backup before updating software, this implies to everything in IT.

@CrazyWolf13 commented on GitHub (May 18, 2025): PR is merged, I tested it successfully. You should be able to update just fine using the `update` command. If your LXC is in broken state, do the following: ```bash mkdir -p /opt/homarr cp /opt/homarr-data-backup/.env /opt/homarr/.env update ``` and as a general advice, always do backup before updating software, this implies to everything in IT.

OVERLORD commented

2026-02-04 21:29:27 +03:00

@CrazyWolf13 commented on GitHub (May 18, 2025):

For anything receiving the info that no update is required, type the following command:

rm /opt/homarr_version.txt

@CrazyWolf13 commented on GitHub (May 18, 2025): For anything receiving the info that no update is required, type the following command: ```bash rm /opt/homarr_version.txt ```

OVERLORD commented

2026-02-04 21:29:30 +03:00

@snoopy12345 commented on GitHub (May 18, 2025):

@CrazyWolf13

For me still not working, just tried to do a new install and got errors. Do I have to wait a bit until the fix works for a new LXC too? Also my former LXC has no .env in the backup directory. 🙈🙈🙈

@snoopy12345 commented on GitHub (May 18, 2025): @CrazyWolf13 For me still not working, just tried to do a new install and got errors. Do I have to wait a bit until the fix works for a new LXC too? Also my former LXC has no .env in the backup directory. 🙈🙈🙈

OVERLORD commented

2026-02-04 21:29:36 +03:00

@CrazyWolf13 commented on GitHub (May 18, 2025):

@snoopy12345
Post the errors.

Numerous people including myself reported success.

@CrazyWolf13 commented on GitHub (May 18, 2025): @snoopy12345 Post the errors. Numerous people including myself reported success.

OVERLORD commented

2026-02-04 21:29:39 +03:00

@snoopy12345 commented on GitHub (May 18, 2025):

@CrazyWolf13 ok here what i just got, clean install new LXC with known command from website:

@homarr/nextjs:build: https://nextjs.org/telemetry
@homarr/nextjs:build:
⠏@homarr/nextjs:build: ▲ Next.js 15.3.2
@homarr/nextjs:build:
⠙@homarr/nextjs:build: Creating an optimized production build ...
⠴@homarr/nextjs:build: Killed
@homarr/nextjs:build: ELIFECYCLE Command failed with exit code 137.
@homarr/nextjs:build: ELIFECYCLE Command failed with exit code 137.
@homarr/nextjs:build: ERROR: command finished with error: command (/opt/homarr/apps/nextjs) /usr/bin/pnpm run build exited (137)
@homarr/nextjs#build: command (/opt/homarr/apps/nextjs) /usr/bin/pnpm run build exited (137)

Tasks: 4 successful, 5 total
Cached: 0 cached, 5 total
Time: 1m28.661s
Failed: @homarr/nextjs#build

...Finishing writing to cache...                                                     WARNING  no output files found for task @homarr/cli#build. Please check your `outputs` key in `turbo.json`

WARNING no output files found for task @homarr/db#build. Please check your outputs key in turbo.json
WARNING no output files found for task @homarr/tasks#build. Please check your outputs key in turbo.json
WARNING no output files found for task @homarr/websocket#build. Please check your outputs key in turbo.json
⠦ ERROR run failed: command exited (137)
⠦ ELIFECYCLE Command failed with exit code 137.
⠧
[ERROR] in line 51: exit code 0: while executing command $STD pnpm build
⠼/dev/fd/63: line 73: SPINNER_PID: unbound variable

@snoopy12345 commented on GitHub (May 18, 2025): @CrazyWolf13 ok here what i just got, clean install new LXC with known command from website: @homarr/nextjs:build: https://nextjs.org/telemetry @homarr/nextjs:build: ⠏@homarr/nextjs:build: ▲ Next.js 15.3.2 @homarr/nextjs:build: ⠙@homarr/nextjs:build: Creating an optimized production build ... ⠴@homarr/nextjs:build: Killed @homarr/nextjs:build: ELIFECYCLE Command failed with exit code 137. @homarr/nextjs:build: ELIFECYCLE Command failed with exit code 137. @homarr/nextjs:build: ERROR: command finished with error: command (/opt/homarr/apps/nextjs) /usr/bin/pnpm run build exited (137) @homarr/nextjs#build: command (/opt/homarr/apps/nextjs) /usr/bin/pnpm run build exited (137) Tasks: 4 successful, 5 total Cached: 0 cached, 5 total Time: 1m28.661s Failed: @homarr/nextjs#build ...Finishing writing to cache... WARNING no output files found for task @homarr/cli#build. Please check your `outputs` key in `turbo.json` WARNING no output files found for task @homarr/db#build. Please check your `outputs` key in `turbo.json` WARNING no output files found for task @homarr/tasks#build. Please check your `outputs` key in `turbo.json` WARNING no output files found for task @homarr/websocket#build. Please check your `outputs` key in `turbo.json` ⠦ ERROR run failed: command exited (137) ⠦ ELIFECYCLE Command failed with exit code 137. ⠧ [ERROR] in line 51: exit code 0: while executing command $STD pnpm build ⠼/dev/fd/63: line 73: SPINNER_PID: unbound variable

OVERLORD commented

2026-02-04 21:29:44 +03:00

@n3rddoom commented on GitHub (May 18, 2025):

Got this from a fresh install, completely stopped this, can't use the workarounds. update command not found and there's no homarr_data_backup

...Finishing writing to cache... WARNING no output files found for task @homarr/cli#build. Please check your outputs key in turbo.json
WARNING no output files found for task @homarr/db#build. Please check your outputs key in turbo.json
WARNING no output files found for task @homarr/tasks#build. Please check your outputs key in turbo.json
WARNING no output files found for task @homarr/websocket#build. Please check your outputs key in turbo.json
✔️ Installed Homarr
⠹0: line 70: RELEASE: unbound variable
/dev/fd/63: line 73: SPINNER_PID: unbound variable

@n3rddoom commented on GitHub (May 18, 2025): Got this from a fresh install, completely stopped this, can't use the workarounds. update command not found and there's no homarr_data_backup > ...Finishing writing to cache... WARNING no output files found for task @homarr/cli#build. Please check your `outputs` key in `turbo.json` WARNING no output files found for task @homarr/db#build. Please check your `outputs` key in `turbo.json` WARNING no output files found for task @homarr/tasks#build. Please check your `outputs` key in `turbo.json` WARNING no output files found for task @homarr/websocket#build. Please check your `outputs` key in `turbo.json` ✔️ Installed Homarr ⠹0: line 70: RELEASE: unbound variable /dev/fd/63: line 73: SPINNER_PID: unbound variable

OVERLORD commented

2026-02-04 21:29:47 +03:00

@snoopy12345 commented on GitHub (May 19, 2025):

Got this from a fresh install, completely stopped this, can't use the workarounds. update command not found and there's no homarr_data_backup

same for me, you have also no .env in the backup diretory?

@snoopy12345 commented on GitHub (May 19, 2025): > Got this from a fresh install, completely stopped this, can't use the workarounds. update command not found and there's no homarr_data_backup > same for me, you have also no .env in the backup diretory?

OVERLORD commented

2026-02-04 21:29:51 +03:00

@Theahlmightyx1 commented on GitHub (May 19, 2025):

cp /opt/homarr-data-backup/.env /opt/homarr/.env

I do not have and env file .. sorry for dumb question, but can i still run the update or no?

root@homarr:# ls /opt/
homarr homarr-data-backup homarr_db Homarr_version.txt run_homarr.sh
root@homarr:# ls /opt/homarr-data-backup/
root@homarr:~# ls -a /opt/homarr-data-backup/

. ..

looks like i have one in /opt/homarr however

@Theahlmightyx1 commented on GitHub (May 19, 2025): > cp /opt/homarr-data-backup/.env /opt/homarr/.env I do not have and env file .. sorry for dumb question, but can i still run the update or no? root@homarr:~# ls /opt/ homarr homarr-data-backup homarr_db Homarr_version.txt run_homarr.sh root@homarr:~# ls /opt/homarr-data-backup/ root@homarr:~# ls -a /opt/homarr-data-backup/ . .. looks like i have one in /opt/homarr however

OVERLORD commented

2026-02-04 21:29:57 +03:00

@n3rddoom commented on GitHub (May 19, 2025):

I don't have a backup directory at all. It created the /opt/homarr folder but then nothing else works. I have 'pct enter' to get to it, but update doesn't work either.

@n3rddoom commented on GitHub (May 19, 2025): I don't have a backup directory at all. It created the /opt/homarr folder but then nothing else works. I have 'pct enter' to get to it, but update doesn't work either.

OVERLORD commented

2026-02-04 21:30:02 +03:00

@Theahlmightyx1 commented on GitHub (May 19, 2025):

okay so i ran cp /opt/homarr/.env /opt/homarr-data-backup/
update and

  ✔️   Services Stopped
  ✔️   Backup Data
  ✔️   Node.js 22 already installed
  ✔️   All requested Node modules have been processed
  ✔️   Updated homarr
  ✔️   Started Services
  ✔️   Updated Successfully
      It's recommended to reboot the LXC after an update, would you like to reboot the LXC now ? (y/n): y
root@homarr:~# reboot
Failed to set wall message, ignoring: Transport endpoint is not connected
Call to Reboot failed: Transport endpoint is not connected
root@homarr:~# reboot -f

seems to be good now!

@Theahlmightyx1 commented on GitHub (May 19, 2025): okay so i ran cp /opt/homarr/.env /opt/homarr-data-backup/ update and ``` ✔️ Services Stopped ✔️ Backup Data ✔️ Node.js 22 already installed ✔️ All requested Node modules have been processed ✔️ Updated homarr ✔️ Started Services ✔️ Updated Successfully It's recommended to reboot the LXC after an update, would you like to reboot the LXC now ? (y/n): y root@homarr:~# reboot Failed to set wall message, ignoring: Transport endpoint is not connected Call to Reboot failed: Transport endpoint is not connected root@homarr:~# reboot -f ``` seems to be good now!

OVERLORD commented

2026-02-04 21:30:07 +03:00

@n3rddoom commented on GitHub (May 19, 2025):

Unfortunately:
bash: update: command not found

@n3rddoom commented on GitHub (May 19, 2025): Unfortunately: `bash: update: command not found`

OVERLORD commented

2026-02-04 21:30:12 +03:00

@n3rddoom commented on GitHub (May 19, 2025):

Found the service to work by manually doing a bash command. What a ride. I hope a fresh install will work for me some day.

@n3rddoom commented on GitHub (May 19, 2025): Found the service to work by manually doing a bash command. What a ride. I hope a fresh install will work for me some day.

OVERLORD commented

2026-02-04 21:30:19 +03:00

@snoopy12345 commented on GitHub (May 19, 2025):

For me so far nothing is working anymore 🤯

@snoopy12345 commented on GitHub (May 19, 2025): For me so far nothing is working anymore 🤯

OVERLORD commented

2026-02-04 21:30:25 +03:00

@CrazyWolf13 commented on GitHub (May 19, 2025):

Yeah for all here searching the .env file:

In linux files with a dot-prefix are hidden.
Though you should still be able to copy it without issues and you can list files with a dot like this:
ls -al

The .env file is either in /opt/homarr or in /opt/homarr-data-backup depending where the update was exited.
It doesn't delete itself unless you manually deleted it.

@n3rddoom
If the update command is not working, you are not correctly using the container shell like you are supposed to, you can also run the install command again in the container shell to run the update:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homarr.sh)"

@snoopy12345
For the install I created a PR which should fix it, there was an unbound variable.

@CrazyWolf13 commented on GitHub (May 19, 2025): Yeah for all here searching the .env file: In linux files with a dot-prefix are hidden. Though you should still be able to copy it without issues and you can list files with a dot like this: `ls -al` The .env file is either in /opt/homarr or in /opt/homarr-data-backup depending where the update was exited. It doesn't delete itself unless you manually deleted it. @n3rddoom If the `update` command is not working, you are not correctly using the container shell like you are supposed to, you can also run the install command again in the container shell to run the update: `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homarr.sh)"` @snoopy12345 For the install I created a PR which should fix it, there was an unbound variable.

OVERLORD commented

2026-02-04 21:30:29 +03:00

@proddy commented on GitHub (May 19, 2025):

Tried a fresh install just now, and same error unfortunately.

@proddy commented on GitHub (May 19, 2025): Tried a fresh install just now, and same error unfortunately. <img width="712" alt="Image" src="https://github.com/user-attachments/assets/65d027ac-e7aa-46f6-9866-599904701e0a" />

OVERLORD commented

2026-02-04 21:30:37 +03:00

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

Sorry, but this Script is getting annoying. There are dirty fixes every day. I would like to coordinate with the others to remove homarr completely. That's worse than actualbudget

@MickLesk commented on GitHub (May 19, 2025): Sorry, but this Script is getting annoying. There are dirty fixes every day. I would like to coordinate with the others to remove homarr completely. That's worse than actualbudget

OVERLORD commented

2026-02-04 21:30:41 +03:00

@manuel-rw commented on GitHub (May 19, 2025):

Hi @MickLesk , sorry to hear that. The instability mainly came from the script not following the same process as we do for our docker images. We missed these things, hence the script failed.
Homarr itself is stable, works fine and doesn't exhibit the same issues in the other installation methods.
We're collaborating as much and as directly as we can with @CrazyWolf13 to work on the script.

@manuel-rw commented on GitHub (May 19, 2025): Hi @MickLesk , sorry to hear that. The instability mainly came from the script not following the same process as we do for our docker images. We missed these things, hence the script failed. Homarr itself is stable, works fine and doesn't exhibit the same issues in the other installation methods. We're collaborating as much and as directly as we can with @CrazyWolf13 to work on the script.

OVERLORD commented

2026-02-04 21:30:48 +03:00

@tremor021 commented on GitHub (May 19, 2025):

@manuel-rw Mick is sensitive to scripts breaking a lot of time is short periods of time :) I must admit i'm also annoyed with such scripts, especially if something in install procedure changes very often. But if its the scripts fault something doesn't work, it only us to blame and we appreciate you taking time to help us out debug/troubleshoot it. We do make mistakes sometimes as everyone else.

As i understand, @CrazyWolf13 is on your discord. This might be a good thing as you can probably tell him if you're about to make a change that can potentially break the install script. Maybe this way we can account for it ahead of time and prevent the script breaking, so users get unaffected.

Again, thanks for being so helpful.

@tremor021 commented on GitHub (May 19, 2025): @manuel-rw Mick is sensitive to scripts breaking a lot of time is short periods of time :) I must admit i'm also annoyed with such scripts, especially if something in install procedure changes very often. But if its the scripts fault something doesn't work, it only us to blame and we appreciate you taking time to help us out debug/troubleshoot it. We do make mistakes sometimes as everyone else. As i understand, @CrazyWolf13 is on your discord. This might be a good thing as you can probably tell him if you're about to make a change that can potentially break the install script. Maybe this way we can account for it ahead of time and prevent the script breaking, so users get unaffected. Again, thanks for being so helpful.

OVERLORD commented

2026-02-04 21:30:53 +03:00

@manuel-rw commented on GitHub (May 19, 2025):

Mick is sensitive to scripts breaking a lot of time is short periods of time :) I must admit i'm also annoyed with such scripts, especially if something in install procedure changes very often.

This is completely justified, frequently breaking components aren't fun.

But if its the scripts fault something doesn't work, it only us to blame and we appreciate you taking time to help us out debug/troubleshoot it. We do make mistakes sometimes as everyone else.

Just to re-iterate, I'm not blaming @CrazyWolf13 or any of the contributors here for anything. I appreciate your work to make it easier to install software.

As i understand, @CrazyWolf13 is on your discord. This might be a good thing as you can probably tell him if you're about to make a change that can potentially break the install script. Maybe this way we can account for it ahead of time and prevent the script breaking, so users get unaffected.

He has access to our internal development channels, and we are working together proactively. One key difference between the Homarr project and other products are the automated dependency updates and highly automated CI. This keeps Homarr very up to date and less vulnerable to CVEs but requires us to perform automated testing to avoid breaking things. Since the Proxmox Scripts install Homarr from source, which is highly discouraged by us for most cases, it can run into this kind of issues more frequently than the other installations.

I'm not implying that you should change the script, but I'm saying that running from source requires more additional work and carefully organized dependency management. Whenever possible, we do announce changes in advance.

Since 1.0.0, we do adhere to the conventional commits and semantic versioning. As per spec, breaking changes for the consumer (user) will be marked as such by the version increment and the commit prefix.

@CrazyWolf13 perhaps we could consider implementing periodic testing, where we run your script or the commands used inside it, to assert whether the current version of Homarr works with it. Happy to accept any ideas or contributions :)

Again, thanks for being so helpful.

You're welcome, and thanks for all commenters and contributors helping on this.

@manuel-rw commented on GitHub (May 19, 2025): > Mick is sensitive to scripts breaking a lot of time is short periods of time :) I must admit i'm also annoyed with such scripts, especially if something in install procedure changes very often. This is completely justified, frequently breaking components aren't fun. > But if its the scripts fault something doesn't work, it only us to blame and we appreciate you taking time to help us out debug/troubleshoot it. We do make mistakes sometimes as everyone else. Just to re-iterate, I'm not blaming @CrazyWolf13 or any of the contributors here for anything. I appreciate your work to make it easier to install software. > As i understand, @CrazyWolf13 is on your discord. This might be a good thing as you can probably tell him if you're about to make a change that can potentially break the install script. Maybe this way we can account for it ahead of time and prevent the script breaking, so users get unaffected. He has access to our internal development channels, and we are working together proactively. One key difference between the Homarr project and other products are the automated dependency updates and highly automated CI. This keeps Homarr very up to date and less vulnerable to CVEs but requires us to perform automated testing to avoid breaking things. Since the Proxmox Scripts install Homarr from source, [which is highly discouraged by us](https://homarr.dev/docs/1.18.0/getting-started/installation/source) for most cases, it can run into this kind of issues more frequently than the other installations. I'm not implying that you should change the script, but I'm saying that running from source requires more additional work and carefully organized dependency management. Whenever possible, we do announce changes in advance. Since 1.0.0, we do adhere to the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) and [semantic versioning](https://semver.org/). As per spec, breaking changes for the consumer (user) will be marked as such by the version increment and the commit prefix. @CrazyWolf13 perhaps we could consider implementing periodic testing, where we run your script or the commands used inside it, to assert whether the current version of Homarr works with it. Happy to accept any ideas or contributions :) > Again, thanks for being so helpful. You're welcome, and thanks for all commenters and contributors helping on this.

OVERLORD commented

2026-02-04 21:30:55 +03:00

@n3rddoom commented on GitHub (May 19, 2025):

Yeah for all here searching the .env file:

In linux files with a dot-prefix are hidden. Though you should still be able to copy it without issues and you can list files with a dot like this: ls -al

The .env file is either in /opt/homarr or in /opt/homarr-data-backup depending where the update was exited. It doesn't delete itself unless you manually deleted it.

@n3rddoom If the update command is not working, you are not correctly using the container shell like you are supposed to, you can also run the install command again in the container shell to run the update: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homarr.sh)"

@snoopy12345 For the install I created a PR which should fix it, there was an unbound variable.

My apologies for not being clear on my comment. After the script install failure. I had to pct enter the container, create the homarr-data-backup folder, then copied the .env from /opt/homarr. After that, I ran the full command you mentioned and then the service install correctly. I had the unbound variable error so I'm pretty sure that's why the update command didn't work. But I got through it. I appreciate the work and help.

@n3rddoom commented on GitHub (May 19, 2025): > Yeah for all here searching the .env file: > > In linux files with a dot-prefix are hidden. Though you should still be able to copy it without issues and you can list files with a dot like this: `ls -al` > > The .env file is either in /opt/homarr or in /opt/homarr-data-backup depending where the update was exited. It doesn't delete itself unless you manually deleted it. > > [@n3rddoom](https://github.com/n3rddoom) If the `update` command is not working, you are not correctly using the container shell like you are supposed to, you can also run the install command again in the container shell to run the update: `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homarr.sh)"` > > [@snoopy12345](https://github.com/snoopy12345) For the install I created a PR which should fix it, there was an unbound variable. My apologies for not being clear on my comment. After the script install failure. I had to pct enter the container, create the homarr-data-backup folder, then copied the .env from /opt/homarr. After that, I ran the full command you mentioned and then the service install correctly. I had the unbound variable error so I'm pretty sure that's why the update command didn't work. But I got through it. I appreciate the work and help.

OVERLORD commented

2026-02-04 21:31:01 +03:00

@snoopy12345 commented on GitHub (May 19, 2025):

no matter what i try at the moment for me updating the old LXC homarr fails (Hangup) and also a fresh install fails with the know issue:

Failed: @homarr/nextjs#build

⠸ ...Finishing writing to cache... WARNING no output files found for task @homarr/cli#build. Please check your outputs key in turbo.json
WARNING no output files found for task @homarr/db#build. Please check your outputs key in turbo.json
WARNING no output files found for task @homarr/tasks#build. Please check your outputs key in turbo.json
WARNING no output files found for task @homarr/websocket#build. Please check your outputs key in turbo.json
ERROR run failed: command exited (137)
ELIFECYCLE Command failed with exit code 137.
⠼
[ERROR] in line 51: exit code 0: while executing command $STD pnpm build
⠙/dev/fd/63: line 73: SPINNER_PID: unbound variable

Any else ideas what i could try from my side?

@snoopy12345 commented on GitHub (May 19, 2025): no matter what i try at the moment for me updating the old LXC homarr fails (Hangup) and also a fresh install fails with the know issue: Failed: @homarr/nextjs#build ⠸ ...Finishing writing to cache... WARNING no output files found for task @homarr/cli#build. Please check your `outputs` key in `turbo.json` WARNING no output files found for task @homarr/db#build. Please check your `outputs` key in `turbo.json` WARNING no output files found for task @homarr/tasks#build. Please check your `outputs` key in `turbo.json` WARNING no output files found for task @homarr/websocket#build. Please check your `outputs` key in `turbo.json` ERROR run failed: command exited (137) ELIFECYCLE Command failed with exit code 137. ⠼ [ERROR] in line 51: exit code 0: while executing command $STD pnpm build ⠙/dev/fd/63: line 73: SPINNER_PID: unbound variable Any else ideas what i could try from my side?

OVERLORD commented

2026-02-04 21:31:03 +03:00

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

increase your RAM to 6gb and 4 cores and test again

@MickLesk commented on GitHub (May 19, 2025): increase your RAM to 6gb and 4 cores and test again

OVERLORD commented

2026-02-04 21:31:06 +03:00

@snoopy12345 commented on GitHub (May 19, 2025):

increase your RAM to 6gb and 4 cores and test again

Thx Mick, this absolutely did the trick. Both upgrading the old instance & install a new LXC working with these settings.

@snoopy12345 commented on GitHub (May 19, 2025): > increase your RAM to 6gb and 4 cores and test again Thx Mick, this absolutely did the trick. Both upgrading the old instance & install a new LXC working with these settings.

OVERLORD commented

2026-02-04 21:31:11 +03:00

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

@manuel-rw Do you have an approximate resource estimate for Docker? Yes, I know it runs on alpine, but I've noticed the resources in the latest versions. My installation on my extra slow mini pc (N95 / N100) took almost 30 minutes with a permanent 99.8% RAM (4GB). I will probably open a PR to increase the resources to 3/6 (CPU / RAM).

@MickLesk commented on GitHub (May 19, 2025): @manuel-rw Do you have an approximate resource estimate for Docker? Yes, I know it runs on alpine, but I've noticed the resources in the latest versions. My installation on my extra slow mini pc (N95 / N100) took almost 30 minutes with a permanent 99.8% RAM (4GB). I will probably open a PR to increase the resources to 3/6 (CPU / RAM).

OVERLORD commented

2026-02-04 21:31:16 +03:00

@h0m35t4r commented on GitHub (May 19, 2025):

Not sure if this was the right thing to do but I noticed the filesystem was full after a failed update. I had to clear the package cache with pnpm store prune in order to reclaim enough disk space to continue with an update

@h0m35t4r commented on GitHub (May 19, 2025): Not sure if this was the right thing to do but I noticed the filesystem was full after a failed update. I had to clear the package cache with `pnpm store prune` in order to reclaim enough disk space to continue with an update

OVERLORD commented

2026-02-04 21:31:21 +03:00

@manuel-rw commented on GitHub (May 19, 2025):

You do not run Homarr using docker in the Promox LXC, no?
Homarr itself will consume about 400–600 MB on average but could take up to 1 GB.
N95 and N100 should be more than capable to run Homarr, I have 3 nodes with N95 myself (k3s) and it runs just fine.
My personal instance running on bare-metal with Docker is consuming about 500MB on average with 17 integrations set up.
But I do not use virtualization in any of my setups, so I don't know how much overhead is caused by it.

@manuel-rw commented on GitHub (May 19, 2025): You do not run Homarr using docker in the Promox LXC, no? Homarr itself will consume about 400–600 MB on average but could take up to 1 GB. N95 and N100 should be more than capable to run Homarr, I have 3 nodes with N95 myself (k3s) and it runs just fine. My personal instance running on bare-metal with Docker is consuming about 500MB on average with 17 integrations set up. But I do not use virtualization in any of my setups, so I don't know how much overhead is caused by it.

OVERLORD commented

2026-02-04 21:31:27 +03:00

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

no its an bare-metal on debian without docker.

@MickLesk commented on GitHub (May 19, 2025): no its an bare-metal on debian without docker.

OVERLORD commented

2026-02-04 21:31:31 +03:00

@manuel-rw commented on GitHub (May 19, 2025):

Just noticed from a post in our Discord, since we build the application inside the LXC, significant higher amounts of RAM will be needed. My above message only applies to running Homarr, not building it. I'm not sure whether 4GB is default, but I've seen it in a lot of screenshots here. That is likely not sufficient for the build. Building NextJS apps takes ridiculous resources... I sometimes see up to 10GB on my development machine when building.

We are considering to distribute a pre-built package for Debian, see https://github.com/homarr-labs/homarr/issues/3146 .
This would eliminate:

all build times within the LXC
any potential for Homarr to be built incorrectly due to outdated scripts
the higher RAM requirement
slow startup

@manuel-rw commented on GitHub (May 19, 2025): Just noticed from a post in our Discord, since we build the application inside the LXC, significant higher amounts of RAM will be needed. My above message only applies to **running** Homarr, not **building** it. I'm not sure whether 4GB is default, but I've seen it in a lot of screenshots here. That is likely not sufficient for the build. Building NextJS apps takes ridiculous resources... I sometimes see up to 10GB on my development machine when building. We are considering to distribute a pre-built package for Debian, see https://github.com/homarr-labs/homarr/issues/3146 . This would eliminate: - all build times within the LXC - any potential for Homarr to be built incorrectly due to outdated scripts - the higher RAM requirement - slow startup

OVERLORD commented

2026-02-04 21:31:35 +03:00

@ebenfarnworth commented on GitHub (Aug 8, 2025):

Between v1.30.0 and v1.31.0, how dose one re run the proxmox update/install script when failed? homarr_version.txt dose not seam to exist in this version. Currently I have a homarr install that failed to update and dose not load or function. Running update gives:
✔️ No update required. homarr is already at v1.31.0

I tried deleting all contents of /opt/homarr and then copying back in the original .env file.
I also tried making a fresh install and then copying over the data, database folders and the .env file to the new install. But that did not work either. I think I just need to get the update script to run re-download and install everything and give it more memory.

@ebenfarnworth commented on GitHub (Aug 8, 2025): Between v1.30.0 and v1.31.0, how dose one re run the proxmox update/install script when failed? `homarr_version.txt` dose not seam to exist in this version. Currently I have a homarr install that failed to update and dose not load or function. Running update gives: ✔️ No update required. homarr is already at v1.31.0 I tried deleting all contents of /opt/homarr and then copying back in the original .env file. I also tried making a fresh install and then copying over the data, database folders and the .env file to the new install. But that did not work either. I think I just need to get the update script to run re-download and install everything and give it more memory.

OVERLORD commented

2026-02-04 21:31:38 +03:00

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

~/.homarr

1 sec Check the homarr.sh and you see the File.

@MickLesk commented on GitHub (Aug 8, 2025): ~/.homarr 1 sec Check the homarr.sh and you see the File.

OVERLORD referenced this issue

2026-02-05 05:10:59 +03:00

[PR #781] [MERGED] Fix Z-Wave JS UI Breaking Change in CHANGELOG.md #2745

Sign in to join this conversation.

Branches Tags

main

github-action-update-changelog

pr-update-app-files

docker_deb13

feat/cloudinit-sshkeys

feat/sqlserver2025

automated/update-github-versions

add-script-opencloud-1770212555

add-script-openclaw-1770212634

github-action-archive-changelog

update_apps_tool

add-script-wishlist-1770193085

MickLesk-patch-2

add-script-writefreely-1770188758

add-script-wealthfolio-1770143943

fix/vaultwarden-update-script

remove_memos

disable_npm

feature/codeberg-functions-forgejo-readeck

add-script-rustypaste-1770019426

add-script-kitchenowl-1770017260

fix/2fauth-php-version

tools_func_addcodeberg

CrazyWolf13-patch-2

add-script-shelfmark-1769790178

CrazyWolf13-patch-1

add-script-ampache-1769790139

add-script-languagetool-1769790155

remove_php_deps

ref_koilection

fix/php-module-improvements

tremor021-patch-1

fix/open-archiver-meilisearch-migration

cloudflare_dns

MickLesk-patch-1

michelroegl-brunner-patch-2

fix/version-display

fix/debian13-root-ownership

feat/interactive_prompts

feature/smart-error-recovery

core_stable

update_docs

refactor/tools-func-stability

certbot_npm

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#781