All requests give 404 response from Rocket server #628

New issue

Closed

opened 2026-02-20 08:03:52 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-20 08:03:52 -05:00

Owner

Originally created by @Carl-RTP on GitHub (Mar 1, 2020).

Subject of the issue

Updated image for my docker container and since then every request to the server results in a 404.
Can't load the web vault, can't sync clients.

Your environment

Bitwarden_rs version:
1.13.1-edfdda86

Install method:
Docker via OMV4 docker plugin with image: bitwardenrs/server:armv6
Clients used:
BitWarden Chrome extension & Android Application.
Reverse proxy and version:
Using Apache, looks like this:

        ProxyPass /bw http://192.168.1.xx:xx
        ProxyPassReverse /bw http://192.168.1.xx:xx

With assigned port mapped to :80 on docker container.

Other relevant information:

Steps to reproduce

Difficult to say, not sure of the cause, but from a working setup all I changed was the docker image to latest armv6 to then have OMV report it unhealthy and all requests 404.
Unsure of what version was before, but looking at the releases it was probably 1.13.1 also..? as it was set up initially on Feb 3rd (so is probably the f5916ec build that worked) and the most recent release was Jan 5th, so I don't know what differs in the docker image that would cause the issue.

Relevant logs

/--------------------------------------------------------------------\
|                       Starting Bitwarden_RS                        |
|                      Version 1.13.1-edfdda86                       |
|--------------------------------------------------------------------|
| 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 |
\--------------------------------------------------------------------/

[2020-03-01 21:15:31][start][INFO] Rocket has launched from http://0.0.0.0:80
[2020-03-01 21:15:41][request][INFO] POST /identity/connect/token
[2020-03-01 21:15:41][response][INFO] 404 Not Found
[2020-03-01 21:17:36][request][INFO] GET /icons/github.com/icon.png
[2020-03-01 21:17:36][response][INFO] 404 Not Found

Every line following is the same [response][INFO] 404 Not Found

Originally created by @Carl-RTP on GitHub (Mar 1, 2020). ### Subject of the issue  Updated image for my docker container and since then every request to the server results in a 404. Can't load the web vault, can't sync clients. ### Your environment  * Bitwarden_rs version: 1.13.1-edfdda86  * Install method: Docker via OMV4 docker plugin with image: bitwardenrs/server:armv6 * Clients used:  BitWarden Chrome extension & Android Application. * Reverse proxy and version: Using Apache, looks like this: ``` ProxyPass /bw http://192.168.1.xx:xx ProxyPassReverse /bw http://192.168.1.xx:xx ``` With assigned port mapped to :80 on docker container. * Other relevant information: ### Steps to reproduce  Difficult to say, not sure of the cause, but from a working setup all I changed was the docker image to latest armv6 to then have OMV report it unhealthy and all requests 404. Unsure of what version was before, but looking at the releases it was probably 1.13.1 also..? as it was set up initially on Feb 3rd (so is probably the f5916ec build that worked) and the most recent release was Jan 5th, so I don't know what differs in the docker image that would cause the issue. ### Relevant logs  ``` /--------------------------------------------------------------------\ | Starting Bitwarden_RS | | Version 1.13.1-edfdda86 | |--------------------------------------------------------------------| | 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 | \--------------------------------------------------------------------/ [2020-03-01 21:15:31][start][INFO] Rocket has launched from http://0.0.0.0:80 [2020-03-01 21:15:41][request][INFO] POST /identity/connect/token [2020-03-01 21:15:41][response][INFO] 404 Not Found [2020-03-01 21:17:36][request][INFO] GET /icons/github.com/icon.png [2020-03-01 21:17:36][response][INFO] 404 Not Found ``` Every line following is the same `[response][INFO] 404 Not Found`

deekerman closed this issue

2026-02-20 08:03:53 -05:00

deekerman commented

2026-02-20 08:03:53 -05:00

Author

Owner

@jjlin commented on GitHub (Mar 1, 2020):

Likely related to https://github.com/dani-garcia/bitwarden_rs/wiki/Using-an-alternate-base-dir. You probably just need to use

ProxyPass /bw/ http://192.168.1.xx:xx/bw/

AFAICT, you can now drop the ProxyPassReverse, but I'm not particularly familiar with using Apache httpd as a reverse proxy.

@jjlin commented on GitHub (Mar 1, 2020): Likely related to https://github.com/dani-garcia/bitwarden_rs/wiki/Using-an-alternate-base-dir. You probably just need to use ``` ProxyPass /bw/ http://192.168.1.xx:xx/bw/ ``` AFAICT, you can now drop the `ProxyPassReverse`, but I'm not particularly familiar with using Apache httpd as a reverse proxy.

deekerman commented

2026-02-20 08:03:53 -05:00

Author

Owner

@Carl-RTP commented on GitHub (Mar 1, 2020):

That solved it!
Was not aware of that being changed, but it's all good now.

I also had

#       RewriteEngine On
#       RewriteCond %{HTTP_REFERER} my\.domain/bw/
#       RewriteCond %{REQUEST_URI} !^/bw/
#       RewriteRule ^/(.*)$ /bw/$1 [R=307,L]

set to have the web vault work in the folder, but have now removed that since it's no longer necessary 👍

Thanks!

@Carl-RTP commented on GitHub (Mar 1, 2020): That solved it! Was not aware of that being changed, but it's all good now. I also had ``` # RewriteEngine On # RewriteCond %{HTTP_REFERER} my\.domain/bw/ # RewriteCond %{REQUEST_URI} !^/bw/ # RewriteRule ^/(.*)$ /bw/$1 [R=307,L] ``` set to have the web vault work in the folder, but have now removed that since it's no longer necessary 👍 Thanks!