Updated to v1.42.1 - Bad Gateway
Hi everyone, I update my homarr to v1.42.1 and I rebooted and webgui is not working anymore keep getting error code 502 bad gateway. How can I resolve this issue.
I did create a backup and snapshot of the old version, I can just roll back but is there a fix for the new update?
16 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?
I will just rollback to the older version until this issue is resolved.
As asked by Cakey above, can you share installation method, logs etc?
I used the update command in the cli
it did say error code on line 159 I think but I can't remember
But how did you install it?
on proxmox container
Proxmox VE Helper-Scripts
Proxmox VE Helper-Scripts
The official website for the Proxmox VE Helper-Scripts (Community) repository. Featuring over 400+ scripts to help you manage your Proxmox Virtual Environment.
So you had a similar screen to this?
yes! I think that was the error
Probably related to
https://discord.com/channels/972958686051962910/1428874658748305570
https://discord.com/channels/972958686051962910/1429156423740428399
@CrazyWolf13 did you already update yourself?
We have yet another user with this problem, can you try to help?
you say you have a backup?
can you run the update again with verbose enabled?
so I can see the actual error?
I did upgrade successfully without issues.
My guess is network timeout (maybe today aws downtime to fetch packages)?
or another thing would be ressource limit, do you particularly "older" or "slower" hardware?
yeah
I just rolled back
sure
ok it works now
when I first did the install I did it silent mode
any idea why it would cause an error?
we can close this case
thanks for you help!
Either a network timeout or some other issue but seems like it's all working
alright