github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-07-17 01:12:27 -05:00
Code Issues 481 Packages Projects Releases 83 Wiki Activity

[GH-ISSUE #2553] Vaultwarden refuses to connect over specified port #10117

New Issue
Closed
opened 2026-04-20 13:29:46 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 13:29:46 -05:00
Owner
Copy Link

Originally created by @Slips-PC on GitHub (Jun 10, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2553

Subject of the issue

When I try to connect to vaultwarden in any way, all connections are refused.

Deployment environment

  • vaultwarden version: 1.25.0

  • Install method: Docker Image

  • Clients used: Web, extension

  • Reverse proxy and version: nginx/1.18.0

  • MySQL/MariaDB or PostgreSQL version: 13+225

  • Other relevant details:

Steps to reproduce

The vaultwarden docker image was started using the command `docker run -d --name vaultwarden -v /vw-data/:/data/ -p 8185:8185 vaultwarden/server:latest` and connection was attempted both over a reverse proxy and directly connecting to the IP.

Expected behaviour

The web vault is shown.

Actual behaviour

Vaultwarden's connection fails, either via a 502 for nginx or a refused connection when attempting to connect over the port.

Troubleshooting data

The vaultwarden docker logs don't suggest anything to be out of the ordinary.

root@slipfox:~# docker logs vaultwarden
/--------------------------------------------------------------------\
|                        Starting Vaultwarden                        |
|                           Version 1.25.0                           |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Send usage/configuration questions or feature requests to:         |
|   https://vaultwarden.discourse.group/                             |
| Report suspected bugs/issues in the software itself at:            |
|   https://github.com/dani-garcia/vaultwarden/issues/new            |
\--------------------------------------------------------------------/

[INFO] No .env file found.

[DEPRECATED]: `SMTP_SSL` or `SMTP_EXPLICIT_TLS` is set. Please use `SMTP_SECURITY` instead.
[2022-06-10 18:40:16.245][start][INFO] Rocket has launched from http://0.0.0.0:80

It was working previously, but stopped sometime in the past day.

Originally created by @Slips-PC on GitHub (Jun 10, 2022). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2553 <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue When I try to connect to vaultwarden in any way, all connections are refused. ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: 1.25.0 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: Docker Image * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) -->Web, extension * Reverse proxy and version: <!-- if applicable -->nginx/1.18.0 * MySQL/MariaDB or PostgreSQL version: <!-- if applicable -->13+225 * Other relevant details: ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> The vaultwarden docker image was started using the command `docker run -d --name vaultwarden -v /vw-data/:/data/ -p 8185:8185 vaultwarden/server:latest` and connection was attempted both over a reverse proxy and directly connecting to the IP. ### Expected behaviour The web vault is shown. ### Actual behaviour Vaultwarden's connection fails, either via a 502 for nginx or a refused connection when attempting to connect over the port. ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data --> The vaultwarden docker logs don't suggest anything to be out of the ordinary. ``` root@slipfox:~# docker logs vaultwarden /--------------------------------------------------------------------\ | Starting Vaultwarden | | Version 1.25.0 | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Send usage/configuration questions or feature requests to: | | https://vaultwarden.discourse.group/ | | Report suspected bugs/issues in the software itself at: | | https://github.com/dani-garcia/vaultwarden/issues/new | \--------------------------------------------------------------------/ [INFO] No .env file found. [DEPRECATED]: `SMTP_SSL` or `SMTP_EXPLICIT_TLS` is set. Please use `SMTP_SECURITY` instead. [2022-06-10 18:40:16.245][start][INFO] Rocket has launched from http://0.0.0.0:80 ``` It was working previously, but stopped sometime in the past day.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#10117
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?