502 Bad Gateway #936

New Issue

OVERLORD · 2025-10-09T16:57:30+03:00

OVERLORD commented

2025-10-09 16:57:30 +03:00

Originally created by @jgralfs on GitHub.

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. 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

2025-10-09 16:57:30 +03:00

OVERLORD commented

2025-10-09 16:57:33 +03:00

@jgralfs commented on GitHub:

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: 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 ```

OVERLORD referenced this issue

2025-10-09 17:19:40 +03:00

Users are affected by organization policies from orgs they are not in #1558

OVERLORD referenced this issue

2025-10-09 18:23:30 +03:00

[PR #1353] [MERGED] Extra features for admin interface. #3442

OVERLORD referenced this issue

2025-10-09 18:23:34 +03:00

[PR #1353] Extra features for admin interface. #3445

Sign in to join this conversation.