Connection refused after updating #1280

New Issue

OVERLORD · 2026-02-05T00:30:07+03:00

OVERLORD commented

2026-02-05 00:30:07 +03:00

Originally created by @Tropaion on GitHub (May 26, 2022).

I have vaultwarden running in a Proxmox Debian LXC.
Before, everything worked without problems, but after updating to the latest version when I try to access via browser it says: "Connection refused".
But it's weird, because vaultwarden started without problems and doesn't show any error:

root@VaultWarden:~# systemctl status vaultwarden
* vaultwarden.service - Vaultwarden Server (Rust Edition)
     Loaded: loaded (/etc/systemd/system/vaultwarden.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2022-05-26 00:08:41 UTC; 28s ago
       Docs: https://github.com/dani-garcia/vaultwarden
   Main PID: 139 (vaultwarden)
      Tasks: 10 (limit: 115715)
     Memory: 5.4M
        CPU: 36ms
     CGroup: /system.slice/vaultwarden.service
             `-139 /opt/vaultwarden/vaultwarden

May 26 00:08:41 VaultWarden vaultwarden[139]: | This is an *unofficial* Bitwarden implementation, DO NOT use the   |
May 26 00:08:41 VaultWarden vaultwarden[139]: | official channels to report bugs/features, regardless of client.   |
May 26 00:08:41 VaultWarden vaultwarden[139]: | Send usage/configuration questions or feature requests to:         |
May 26 00:08:41 VaultWarden vaultwarden[139]: |   https://vaultwarden.discourse.group/                             |
May 26 00:08:41 VaultWarden vaultwarden[139]: | Report suspected bugs/issues in the software itself at:            |
May 26 00:08:41 VaultWarden vaultwarden[139]: |   https://github.com/dani-garcia/vaultwarden/issues/new            |
May 26 00:08:41 VaultWarden vaultwarden[139]: \--------------------------------------------------------------------/
May 26 00:08:41 VaultWarden vaultwarden[139]: [2022-05-26 00:08:41.280][start][INFO] Rocket has launched from http://127.0.0.1:80
May 26 00:08:41 VaultWarden vaultwarden[139]: [2022-05-26 00:08:41.281][parity_ws][INFO] Listening for new connections on 0.0.0.0:3012.

Originally created by @Tropaion on GitHub (May 26, 2022). I have vaultwarden running in a Proxmox Debian LXC. Before, everything worked without problems, but after updating to the latest version when I try to access via browser it says: "Connection refused". But it's weird, because vaultwarden started without problems and doesn't show any error: ``` root@VaultWarden:~# systemctl status vaultwarden * vaultwarden.service - Vaultwarden Server (Rust Edition) Loaded: loaded (/etc/systemd/system/vaultwarden.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2022-05-26 00:08:41 UTC; 28s ago Docs: https://github.com/dani-garcia/vaultwarden Main PID: 139 (vaultwarden) Tasks: 10 (limit: 115715) Memory: 5.4M CPU: 36ms CGroup: /system.slice/vaultwarden.service `-139 /opt/vaultwarden/vaultwarden May 26 00:08:41 VaultWarden vaultwarden[139]: | This is an *unofficial* Bitwarden implementation, DO NOT use the | May 26 00:08:41 VaultWarden vaultwarden[139]: | official channels to report bugs/features, regardless of client. | May 26 00:08:41 VaultWarden vaultwarden[139]: | Send usage/configuration questions or feature requests to: | May 26 00:08:41 VaultWarden vaultwarden[139]: | https://vaultwarden.discourse.group/ | May 26 00:08:41 VaultWarden vaultwarden[139]: | Report suspected bugs/issues in the software itself at: | May 26 00:08:41 VaultWarden vaultwarden[139]: | https://github.com/dani-garcia/vaultwarden/issues/new | May 26 00:08:41 VaultWarden vaultwarden[139]: \--------------------------------------------------------------------/ May 26 00:08:41 VaultWarden vaultwarden[139]: [2022-05-26 00:08:41.280][start][INFO] Rocket has launched from http://127.0.0.1:80 May 26 00:08:41 VaultWarden vaultwarden[139]: [2022-05-26 00:08:41.281][parity_ws][INFO] Listening for new connections on 0.0.0.0:3012. ```

OVERLORD closed this issue

2026-02-05 00:30:08 +03:00

OVERLORD commented

2026-02-05 00:30:17 +03:00

@BlackDex commented on GitHub (May 26, 2022):

Change ROCKET_ADDRESS to 0.0.0.0 it currently is running on 127.0.0.1 which is probably causing the issue right now

@BlackDex commented on GitHub (May 26, 2022): Change `ROCKET_ADDRESS` to `0.0.0.0` it currently is running on 127.0.0.1 which is probably causing the issue right now

OVERLORD commented

2026-02-05 00:30:21 +03:00

@Tropaion commented on GitHub (May 26, 2022):

Ok weird, now it works. Never had a problem with that before.

Thanks for your help.

@Tropaion commented on GitHub (May 26, 2022): Ok weird, now it works. Never had a problem with that before. Thanks for your help.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#1280