502 Bad Gateway #1478

New Issue

OVERLORD · 2026-02-05T01:03:13+03:00

OVERLORD commented

2026-02-05 01:03:13 +03:00

Originally created by @jgralfs on GitHub (Jan 24, 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 GitHub (Jan 24, 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.

OVERLORD closed this issue

2026-02-05 01:03:15 +03:00

OVERLORD commented

2026-02-05 01:03:20 +03:00

@jgralfs commented on GitHub (Jan 24, 2023):

docker-compose.yml looks like this:

version: '3'
services:
 vaultwarden:
  image: vaultwarden/server:latest
  environment:
    SIGNUPS_ALLOWED: "false"
    ROCKET_ADDRESS: "0.0.0.0"
  restart: unless-stopped
  ports:
    - "80:80"
  volumes:
    - /srv/vaultwarden:/data

@jgralfs commented on GitHub (Jan 24, 2023): docker-compose.yml looks like this: ``` version: '3' services: vaultwarden: image: vaultwarden/server:latest environment: SIGNUPS_ALLOWED: "false" ROCKET_ADDRESS: "0.0.0.0" restart: unless-stopped ports: - "80:80" volumes: - /srv/vaultwarden:/data ```

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#1478