starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2025-12-09 17:23:04 +03:00
Code Issues 429 Packages Projects Releases 10 Wiki Activity

bitwarden_rs: 503 Service Unavailable #2062

New Issue
Closed
opened 2025-10-09 17:43:53 +03:00 by OVERLORD · 16 comments
OVERLORD commented 2025-10-09 17:43:53 +03:00
Owner
Copy Link

Originally created by @markcs on GitHub.

I have bitwarden_rs installed using a reverse proxy between two Linux machines.

Randomly I am unable to access bitwarden and receive the 503 Service Unavailable error. When I connect to the local LAN, and try to connect through the 192.168.x.x address, I am also unable to connect.

If I restart bitwardan_rs docker (docker restart bitwarden_rs) then I can then access the web interface.

I'm not sure what to log within Docker or how to debug this, so advice is welcome. Sorry I've not posted any logs.

Originally created by @markcs on GitHub. I have bitwarden_rs installed using a reverse proxy between two Linux machines. Randomly I am unable to access bitwarden and receive the 503 Service Unavailable error. When I connect to the local LAN, and try to connect through the 192.168.x.x address, I am also unable to connect. If I restart bitwardan_rs docker (docker restart bitwarden_rs) then I can then access the web interface. I'm not sure what to log within Docker or how to debug this, so advice is welcome. Sorry I've not posted any logs.
OVERLORD added the troubleshootingquestion labels 2025-10-09 17:43:53 +03:00
OVERLORD commented 2025-10-09 17:43:56 +03:00
Author
Owner
Copy Link

@markcs commented on GitHub:

Docker logs doesn't show me anything that I think you'll consider important... all I see are icon downloads. Below you can see the last icon download and then when docker was restarted.

Can I activate further debugging in docker?

[2019-07-31 11:45:59][][INFO] Outcome: Success
[2019-07-31 11:45:59][][INFO] Response succeeded.
/--------------------------------------------------------------------
| Starting Bitwarden_RS |

Version 1.9.1-d7ee7cae
This is an unofficial Bitwarden implementation, DO NOT use the
official channels to report bugs/features, regardless of client.
Report URL: https://github.com/dani-garcia/bitwarden_rs/issues/new
--------------------------------------------------------------------/

[2019-08-01 04:49:01][launch][INFO] Configured for staging.
[2019-08-01 04:49:01][launch_][INFO] address: 0.0.0.0
[2019-08-01 04:49:01][launch_][INFO] port: 80
[2019-08-01 04:49:01][launch_][INFO] log: normal
[2019-08-01 04:49:01][launch_][INFO] workers: 10
[2019-08-01 04:49:01][launch_][INFO] secret key: private-cookies disabled
[2019-08-01 04:49:01][launch_][INFO] limits: forms = 32KiB, json* = 10MiB
[2019-08-01 04:49:01][launch_][INFO] keep-alive: 5s
[2019-08-01 04:49:01][launch_][INFO] tls: disabled
[2019-08-01 04:49:01][rocket::fairing::fairings][INFO] Fairings:

@markcs commented on GitHub: Docker logs doesn't show me anything that I think you'll consider important... all I see are icon downloads. Below you can see the last icon download and then when docker was restarted. Can I activate further debugging in docker? [2019-07-31 11:45:59][_][INFO] Outcome: Success [2019-07-31 11:45:59][_][INFO] Response succeeded. /--------------------------------------------------------------------\ | Starting Bitwarden_RS | | Version 1.9.1-d7ee7cae | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Report URL: https://github.com/dani-garcia/bitwarden_rs/issues/new | \--------------------------------------------------------------------/ [2019-08-01 04:49:01][launch][INFO] Configured for staging. [2019-08-01 04:49:01][launch_][INFO] address: 0.0.0.0 [2019-08-01 04:49:01][launch_][INFO] port: 80 [2019-08-01 04:49:01][launch_][INFO] log: normal [2019-08-01 04:49:01][launch_][INFO] workers: 10 [2019-08-01 04:49:01][launch_][INFO] secret key: private-cookies disabled [2019-08-01 04:49:01][launch_][INFO] limits: forms = 32KiB, json* = 10MiB [2019-08-01 04:49:01][launch_][INFO] keep-alive: 5s [2019-08-01 04:49:01][launch_][INFO] tls: disabled [2019-08-01 04:49:01][rocket::fairing::fairings][INFO] Fairings:
OVERLORD commented 2025-10-09 17:43:57 +03:00
Author
Owner
Copy Link

@janost commented on GitHub:

@markcs During application start up you can see the version on stdout:

Aug 01 12:39:49 galaxy podman[2453]: |                       Starting Bitwarden_RS                        |
Aug 01 12:39:49 galaxy podman[2453]: |                       Version 1.9.1-8be2ed62                       |
@janost commented on GitHub: @markcs During application start up you can see the version on stdout: ``` Aug 01 12:39:49 galaxy podman[2453]: | Starting Bitwarden_RS | Aug 01 12:39:49 galaxy podman[2453]: | Version 1.9.1-8be2ed62 | ```
OVERLORD commented 2025-10-09 17:43:57 +03:00
Author
Owner
Copy Link

@markcs commented on GitHub:

I've installed the latest image and will update here if this occurs again. Otherwise I'll report back in a few days if it is all good.

BTW, how do I check what version of bitwarden_rs I have running?

@markcs commented on GitHub: I've installed the latest image and will update here if this occurs again. Otherwise I'll report back in a few days if it is all good. BTW, how do I check what version of bitwarden_rs I have running?
OVERLORD commented 2025-10-09 17:43:58 +03:00
Author
Owner
Copy Link

@mprasil commented on GitHub:

There was recent fix for some panic when getting icons, perhaps you've been experiencing the same problem? Can you try with the latest image and see if you still encounter the problem?

@mprasil commented on GitHub: There was recent fix for some panic when getting icons, perhaps you've been experiencing the same problem? Can you try with the latest image and see if you still encounter the problem?
OVERLORD commented 2025-10-09 17:43:58 +03:00
Author
Owner
Copy Link

@mprasil commented on GitHub:

When the service is broken, see docker logs for the container. This should help narrowing down the problem.

@mprasil commented on GitHub: When the service is broken, see docker logs for the container. This should help narrowing down the problem.
OVERLORD commented 2025-10-09 17:43:59 +03:00
Author
Owner
Copy Link

@markcs commented on GitHub:

I haven't seen this again, so the upgrade appears to have fixed this.

We can close. Thanks for your help

@markcs commented on GitHub: I haven't seen this again, so the upgrade appears to have fixed this. We can close. Thanks for your help
OVERLORD commented 2025-10-09 17:43:59 +03:00
Author
Owner
Copy Link

@dani-garcia commented on GitHub:

I fixed another error that mentioned missing pair recently can you try to update your image?

If the error still happens, try to run it with RUST_BACKTRACE=1 and paste the detailed error message here.

@dani-garcia commented on GitHub: I fixed another error that mentioned missing pair recently can you try to update your image? If the error still happens, try to run it with RUST_BACKTRACE=1 and paste the detailed error message here.
OVERLORD commented 2025-10-09 17:44:00 +03:00
Author
Owner
Copy Link

@markcs commented on GitHub:

Ok, I pulled the latest and saw the error again.

I started docker like this. Is this correct for BACKTRACE=1?

docker run -d --name bitwarden_rs --restart unless-stopped -e LOG_FILE=/data/bitwarden.log -v /home/mark/docker/bw-data-rs/:/data/ -p 8082:80 -e "RUST_BACKTRACE=1" mprasil/bitwarden:latest

@markcs commented on GitHub: Ok, I pulled the latest and saw the error again. I started docker like this. Is this correct for BACKTRACE=1? docker run -d --name bitwarden_rs --restart unless-stopped -e LOG_FILE=/data/bitwarden.log -v /home/mark/docker/bw-data-rs/:/data/ -p 8082:80 -e "RUST_BACKTRACE=1" mprasil/bitwarden:latest
OVERLORD commented 2025-10-09 17:44:00 +03:00
Author
Owner
Copy Link

@markcs commented on GitHub:

Sorry to comment on a closed issue, but I am still seeing this.
Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.

:~$ docker logs bitwarden_rs > bitwarden.log

thread '' panicked at 'called Result::unwrap() on an Err value: MissingPair', src/libcore/result.rs:1051:5
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace.

-> is this error causing the issue?

the log

@markcs commented on GitHub: Sorry to comment on a closed issue, but I am still seeing this. Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /. :~$ docker logs bitwarden_rs > bitwarden.log thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: MissingPair', src/libcore/result.rs:1051:5 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace. -> is this error causing the issue? the log
OVERLORD commented 2025-10-09 17:44:00 +03:00
Author
Owner
Copy Link

@mprasil commented on GitHub:

Yay! Closing this now.

@mprasil commented on GitHub: Yay! Closing this now.
OVERLORD commented 2025-10-09 17:44:01 +03:00
Author
Owner
Copy Link

@markcs commented on GitHub:

This has happened again to me. I have the bitwarden.log using the logging described here: https://github.com/dani-garcia/bitwarden_rs/wiki/Logging

Does this contain any sensitive information?

@mprasil @dani-garcia

@markcs commented on GitHub: This has happened again to me. I have the bitwarden.log using the logging described here: https://github.com/dani-garcia/bitwarden_rs/wiki/Logging Does this contain any sensitive information? @mprasil @dani-garcia
OVERLORD commented 2025-10-09 17:44:01 +03:00
Author
Owner
Copy Link

@markcs commented on GitHub:

@dani-garcia I've seen the issue again, but nothing really in the logs.

This is how I started bitwarden_rs:

./docker run -d --name bitwarden_rs --restart unless-stopped -e LOG_FILE=/data/bitwarden.log -v /home/mark/docker/bw-data-rs/:/data/ -p 8082:80 -e RUST_BACKTRACE=1 mprasil/bitwarden:latest

@markcs commented on GitHub: @dani-garcia I've seen the issue again, but nothing really in the logs. This is how I started bitwarden_rs: `./docker run -d --name bitwarden_rs --restart unless-stopped -e LOG_FILE=/data/bitwarden.log -v /home/mark/docker/bw-data-rs/:/data/ -p 8082:80 -e RUST_BACKTRACE=1 mprasil/bitwarden:latest`
OVERLORD commented 2025-10-09 17:44:02 +03:00
Author
Owner
Copy Link

@markcs commented on GitHub:

@dani-garcia

I saw the issue again after restarting bitwarden with the above command. The logs contain all the icon fetching plus these warnings.

[2019-08-08 04:08:23][rocket::rocket][INFO] GET /icons/%22c/icon.png image/webp:
[2019-08-08 04:08:23][_][INFO] Matched: GET /icons//icon.png (icon)
[2019-08-08 04:08:23][bitwarden_rs::api::icons][WARN] Invalid domain: ""c"

[2019-08-08 04:08:34][bitwarden_rs::api::icons][ERROR] Error downloading icon: Empty response. Empty response

[2019-08-08 04:08:35][html5ever::tree_builder][WARN] foster parenting not implemented
[2019-08-08 04:08:35][html5ever::tree_builder][WARN] foster parenting not implemented
[2019-08-08 04:08:35][html5ever::tree_builder][WARN] foster parenting not implemented
[2019-08-08 04:08:35][bitwarden_rs::api::icons][INFO] Download failed for http://www.homepharmacy.com.a u/favicon.ico
[2019-08-08 04:08:35][bitwarden_rs::api::icons][ERROR] Error downloading icon: Empty response. Empty re sponse

[2019-08-08 04:08:35][bitwarden_rs::api::icons][INFO] Download failed for https://host3.sabameeting.com /favicon.ico
[2019-08-08 04:08:35][bitwarden_rs::api::icons][ERROR] Error downloading icon: Empty response. Empty re sponse

@markcs commented on GitHub: @dani-garcia I saw the issue again after restarting bitwarden with the above command. The logs contain all the icon fetching plus these warnings. [2019-08-08 04:08:23][rocket::rocket][INFO] GET /icons/%22c/icon.png image/webp: [2019-08-08 04:08:23][_][INFO] Matched: GET /icons/<domain>/icon.png (icon) [2019-08-08 04:08:23][bitwarden_rs::api::icons][WARN] Invalid domain: "\"c" [2019-08-08 04:08:34][bitwarden_rs::api::icons][ERROR] Error downloading icon: Empty response. Empty response [2019-08-08 04:08:35][html5ever::tree_builder][WARN] foster parenting not implemented [2019-08-08 04:08:35][html5ever::tree_builder][WARN] foster parenting not implemented [2019-08-08 04:08:35][html5ever::tree_builder][WARN] foster parenting not implemented [2019-08-08 04:08:35][bitwarden_rs::api::icons][INFO] Download failed for http://www.homepharmacy.com.a u/favicon.ico [2019-08-08 04:08:35][bitwarden_rs::api::icons][ERROR] Error downloading icon: Empty response. Empty re sponse [2019-08-08 04:08:35][bitwarden_rs::api::icons][INFO] Download failed for https://host3.sabameeting.com /favicon.ico [2019-08-08 04:08:35][bitwarden_rs::api::icons][ERROR] Error downloading icon: Empty response. Empty re sponse
OVERLORD commented 2025-10-09 17:44:03 +03:00
Author
Owner
Copy Link

@mprasil commented on GitHub:

@markcs you are using old/wrong image. Use bitwardenrs/server.

@mprasil commented on GitHub: @markcs you are using old/wrong image. Use `bitwardenrs/server`.
OVERLORD commented 2025-10-09 17:44:03 +03:00
Author
Owner
Copy Link

@markcs commented on GitHub:

@mprasil @dani-garcia

Thanks for the tip. So now I restarted bitwarden with.
docker run -d --name bitwarden_rs --restart unless-stopped -e LOG_FILE=/data/bitwarden.log -v /home/mark/docker/bw-data-rs/:/data/ -p 8082:80 -e RUST_BACKTRACE=1 bitwardenrs/server:latest

Version Version 1.9.1-8be2ed62

But I'm still seeing the same issue.

The RUST_BACKTRACE is not giving any more printouts in the logs

EDIT: started bitwarden_rs again with the logging described here: https://github.com/dani-garcia/bitwarden_rs/wiki/Logging

@markcs commented on GitHub: @mprasil @dani-garcia Thanks for the tip. So now I restarted bitwarden with. `docker run -d --name bitwarden_rs --restart unless-stopped -e LOG_FILE=/data/bitwarden.log -v /home/mark/docker/bw-data-rs/:/data/ -p 8082:80 -e RUST_BACKTRACE=1 bitwardenrs/server:latest ` Version Version 1.9.1-8be2ed62 But I'm still seeing the same issue. The RUST_BACKTRACE is not giving any more printouts in the logs EDIT: started bitwarden_rs again with the logging described here: https://github.com/dani-garcia/bitwarden_rs/wiki/Logging
OVERLORD commented 2025-10-09 17:44:04 +03:00
Author
Owner
Copy Link

@dani-garcia commented on GitHub:

If you have failed login attempts it would contain the IP and email address of the attempt. Other than that I don't think so, mostly just random identifiers.

@dani-garcia commented on GitHub: If you have failed login attempts it would contain the IP and email address of the attempt. Other than that I don't think so, mostly just random identifiers.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
bug
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
troubleshooting
wontfix
No Label question troubleshooting
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#2062
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?