502 Bad Gateway #1785

Closed
opened 2026-04-06 02:24:04 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @jgralfs on 1/23/2023

I am running vaultwarden/server:latest in an almalinux 9 container on a proxmox host unsing the nginx proxy manager as a proxy.

I am able to start the container and everything is working fine but after a few minutes I get 502 Bad Gateway errors. When restarting the container everything works again for a few minutes.

*Originally created by @jgralfs on 1/23/2023* I am running vaultwarden/server:latest in an almalinux 9 container on a proxmox host unsing the nginx proxy manager as a proxy. I am able to start the container and everything is working fine but after a few minutes I get 502 Bad Gateway errors. When restarting the container everything works again for a few minutes.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/vaultwarden#1785