Update to 1.20
hello, I have homarr installed in proxmox. I upgraded to version 1.20 using the "update" command through the proxmox container console. the dashboard stopped opening (nginx error 501) and the log shows the following information:
root@homarr:~# systemctl status homarr
× homarr.service - Homarr Service
Loaded: loaded (/etc/systemd/system/homarr.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Sat 2025-05-17 15:55:18 MSK; 1min 40s ago
Duration: 316ms
Process: 144 ExecStart=/opt/run_homarr.sh (code=exited, status=1/FAILURE)
Main PID: 144 (code=exited, status=1/FAILURE)
CPU: 246ms
May 17 15:55:18 homarr run_homarr.sh[173]: at TracingChannel.traceSync (node:diagnostics_channel:322:14)
May 17 15:55:18 homarr run_homarr.sh[173]: at wrapModuleLoad (node:internal/modules/cjs/loader:235:24)
May 17 15:55:18 homarr run_homarr.sh[173]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5)
May 17 15:55:18 homarr run_homarr.sh[173]: at node:internal/main/run_main_module:36:49 {
May 17 15:55:18 homarr run_homarr.sh[173]: code: 'MODULE_NOT_FOUND',
May 17 15:55:18 homarr run_homarr.sh[173]: requireStack: []
May 17 15:55:18 homarr run_homarr.sh[173]: }
May 17 15:55:18 homarr run_homarr.sh[173]: Node.js v22.15.0
May 17 15:55:18 homarr systemd[1]: homarr.service: Main process exited, code=exited, status=1/FAILURE
May 17 15:55:18 homarr systemd[1]: homarr.service: Failed with result 'exit-code'.
how can this be fixed? I have already restarted the container.
30 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
Please run journalctl instead. We need more information & logs
They are actively fixing this btw last I checked on GitHub.
I believe it is both a homarr issue and helper scripts issue
https://github.com/community-scripts/ProxmoxVE/issues/3778
GitHub
Homarr update failed · Issue #3778 · community-scripts/ProxmoxVE
✅ 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 -fs...
I am having the same problem
this is what I am seeing

Nginx fails too
same thing happen I was about to post a help and seen this
hello, any updates on the fix?
hi y'all I'm the one from community-scripts that made the homarr script, I've just now released a fix:
https://github.com/community-scripts/ProxmoxVE/issues/3778#issuecomment-2889166076
GitHub
Homarr update failed · Issue #3778 · community-scripts/ProxmoxVE
✅ 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 -fs...
@Sami
@dron_wic
@ĐɆ₳ĐⱠł₲Ⱨ₮ @Walter H. White
ok thank you @CrazyWolf13 I will update mine now
@CrazyWolf13 I am not getting any updates when running the update command

type:
rm /opt/homarr_version.txt
yeah thanks, it's running the update now
mine updated as expected. Thank you
Yeah mine just finished updating and it is working normally again. Thanks @CrazyWolf13
Hmm, did not work for me, getting stuck on this.

Oh man you’re a life saver thank you so much already started backing up all my lxc and vms also about to buy a extra pc for backing up proxmox automatically and gonna use duplicati as another backup to my nas
that's wonderful 🙂
ohhh that's not so good, seems like you used webui and lost connection?
I suggest locating the .env file with
ls -al
it's either in /opt/homarr or /opt/homarr-backup-data, make sure to backup that file to another location.
then
After I tried that it gave me this

No big deal if I need to reinstall since I had not configured that much, but keeping it for now as long as you want it for debugging 🙂
Kinda want to be sure it does not happen to my other instance I have for work before updating that though
that's very weird, it shows excited (killed), I cannot see any other problem, did you exit it anyhow?
No I did not exit by myself or anything, and I tried it on my other build now and it hangs on the exact same thing
Can you try increasing memory?
https://github.com/community-scripts/ProxmoxVE/issues/3778#issuecomment-2890523477
could it be that the LXC is not powerful enough?
You read my thoughts haha
will try
137
indicates OOM, "out of memory"the lxc was on 4GB and 512MB swap, increased to 6GB and 1GB Swap. lets see if that works
That seemed to work indeed, could be good to know if anyone else stumbles upon the same issue. Maybe adjust the LXC defaults? @CrazyWolf13
yeah just noticed, PR is already made
Thank you for the help 🙂