Originally created by @rotda on GitHub (Feb 27, 2020).
Hi ,
since the last update of my bitwarden_rs docker image .
It doesn't work I get for every request an 404.
Docker logs:
/--------------------------------------------------------------------\
| Starting Bitwarden_RS |
| Version 1.13.1-cd890754 |
|--------------------------------------------------------------------|
| 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 |
\--------------------------------------------------------------------/
Configured for staging.
=> address: 0.0.0.0
=> port: 80
=> log: normal
=> workers: 10
=> secret key: private-cookies disabled
=> limits: forms = 32KiB, json* = 10MiB
=> keep-alive: 5s
=> tls: disabled
Mounting /bitwarden/:
=> GET /bitwarden (web_index)
=> GET /bitwarden/app-id.json (app_id)
=> GET /bitwarden/<p..> [10] (web_files)
=> GET /bitwarden/attachments/<uuid>/<file..> (attachments)
=> GET /bitwarden/alive (alive)
=> GET /bitwarden/bwrs_static/<filename> (static_files)
Mounting /bitwarden/api:
GET /bitwarden/app-id.json
GET /bitwarden/attachments/<uuid>/<file..>
GET /bitwarden/bwrs_static/<filename>
GET /bitwarden/icons/<domain>/icon.png
POST /bitwarden/identity/connect/token
GET /bitwarden/notifications/hub
POST /bitwarden/notifications/hub/negotiate
Rocket has launched from http://0.0.0.0:80
Rocket has launched from http://0.0.0.0:80
GET / text/html:
GET /
=> Error: No matching routes for GET / text/html.
=> Warning: Responding with 404 Not Found catcher.
404 Not Found
=> Response succeeded.
GET / text/html:
GET /
=> Error: No matching routes for GET / text/html.
=> Warning: Responding with 404 Not Found catcher.
404 Not Found
=> Response succeeded.
Originally created by @rotda on GitHub (Feb 27, 2020).
Hi ,
since the last update of my bitwarden_rs docker image .
It doesn't work I get for every request an 404.
Docker logs:
```
/--------------------------------------------------------------------\
| Starting Bitwarden_RS |
| Version 1.13.1-cd890754 |
|--------------------------------------------------------------------|
| 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 |
\--------------------------------------------------------------------/
Configured for staging.
=> address: 0.0.0.0
=> port: 80
=> log: normal
=> workers: 10
=> secret key: private-cookies disabled
=> limits: forms = 32KiB, json* = 10MiB
=> keep-alive: 5s
=> tls: disabled
Mounting /bitwarden/:
=> GET /bitwarden (web_index)
=> GET /bitwarden/app-id.json (app_id)
=> GET /bitwarden/<p..> [10] (web_files)
=> GET /bitwarden/attachments/<uuid>/<file..> (attachments)
=> GET /bitwarden/alive (alive)
=> GET /bitwarden/bwrs_static/<filename> (static_files)
Mounting /bitwarden/api:
GET /bitwarden/app-id.json
GET /bitwarden/attachments/<uuid>/<file..>
GET /bitwarden/bwrs_static/<filename>
GET /bitwarden/icons/<domain>/icon.png
POST /bitwarden/identity/connect/token
GET /bitwarden/notifications/hub
POST /bitwarden/notifications/hub/negotiate
Rocket has launched from http://0.0.0.0:80
Rocket has launched from http://0.0.0.0:80
GET / text/html:
GET /
=> Error: No matching routes for GET / text/html.
=> Warning: Responding with 404 Not Found catcher.
404 Not Found
=> Response succeeded.
GET / text/html:
GET /
=> Error: No matching routes for GET / text/html.
=> Warning: Responding with 404 Not Found catcher.
404 Not Found
=> Response succeeded.
```
It seems in the new version of the docker image, now everything is behind https://:/bitwarden/ and not as is in the past direct /
@rotda commented on GitHub (Feb 28, 2020):
Can be closed.
It seems in the new version of the docker image, now everything is behind https://<localhost>:<port>/bitwarden/ and not as is in the past direct /
I don't think this is the default behavior. You might have miss-configured the DOMAIN setting. In the past the support for sub-path wasn't there, so maybe part of your setting was ignored, but it's now used.
@mprasil commented on GitHub (Feb 28, 2020):
I don't think this is the default behavior. You might have miss-configured the `DOMAIN` setting. In the past the support for sub-path wasn't there, so maybe part of your setting was ignored, but it's now used.
I don't think this is the default behavior. You might have miss-configured the DOMAIN setting. In the past the support for sub-path wasn't there, so maybe part of your setting was ignored, but it's now used.
How I can modify it now?
@pilot1981 commented on GitHub (Dec 31, 2022):
> I don't think this is the default behavior. You might have miss-configured the `DOMAIN` setting. In the past the support for sub-path wasn't there, so maybe part of your setting was ignored, but it's now used.
How I can modify it now?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @rotda on GitHub (Feb 27, 2020).
Hi ,
since the last update of my bitwarden_rs docker image .
It doesn't work I get for every request an 404.
Docker logs:
@rotda commented on GitHub (Feb 28, 2020):
Can be closed.
It seems in the new version of the docker image, now everything is behind https://:/bitwarden/ and not as is in the past direct /
@mprasil commented on GitHub (Feb 28, 2020):
I don't think this is the default behavior. You might have miss-configured the
DOMAINsetting. In the past the support for sub-path wasn't there, so maybe part of your setting was ignored, but it's now used.@pilot1981 commented on GitHub (Dec 31, 2022):
How I can modify it now?