starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-26 01:35:54 +03:00
Code Issues 39 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #389] Docker: Internal server error when accessing /admin #225

New issue
Closed
opened 2026-03-03 01:26:54 +03:00 by kerem · 7 comments
kerem commented 2026-03-03 01:26:54 +03:00
Owner
Copy link

Originally created by @Flameborn on GitHub (Feb 9, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/389

Hello,

I am getting a HTTP 500 server error when accessing https://bw.domain.tld/admin, or the custom port on http://localhost:4000/admin via the latest docker image.

The ADMIN_TOKEN environment variable is configured.

My log:

Feb 09 20:26:34 sapphire systemd-docker[9754]: [2019-02-09 20:26:34][rocket::rocket][INFO] GET /admin:
Feb 09 20:26:34 sapphire systemd-docker[9754]: [2019-02-09 20:26:34][][INFO] Matched: GET /<p..> [10] (web_files)
Feb 09 20:26:34 sapphire systemd-docker[9754]: [2019-02-09 20:26:34][][ERROR] Response was a non-Responder Err: Os { code: 2, kind: NotFound, message: "No
such file or directory" }.
Feb 09 20:26:34 sapphire systemd-docker[9754]: [2019-02-09 20:26:34][][INFO] Outcome: Failure
Feb 09 20:26:34 sapphire systemd-docker[9754]: [2019-02-09 20:26:34][][WARN] Responding with 500 Internal Server Error catcher.
Feb 09 20:26:34 sapphire systemd-docker[9754]: [2019-02-09 20:26:34][_][INFO] Response succeeded.

Originally created by @Flameborn on GitHub (Feb 9, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/389 Hello, I am getting a HTTP 500 server error when accessing _https://bw.domain.tld/admin_, or the custom port on _http://localhost:4000/admin_ via the latest docker image. The ADMIN_TOKEN environment variable is configured. My log: Feb 09 20:26:34 sapphire systemd-docker[9754]: [2019-02-09 20:26:34][rocket::rocket][INFO] GET /admin: Feb 09 20:26:34 sapphire systemd-docker[9754]: [2019-02-09 20:26:34][_][INFO] Matched: GET /<p..> [10] (web_files) Feb 09 20:26:34 sapphire systemd-docker[9754]: [2019-02-09 20:26:34][_][ERROR] Response was a non-`Responder` `Err`: Os { code: 2, kind: NotFound, message: "No such file or directory" }. Feb 09 20:26:34 sapphire systemd-docker[9754]: [2019-02-09 20:26:34][_][INFO] Outcome: Failure Feb 09 20:26:34 sapphire systemd-docker[9754]: [2019-02-09 20:26:34][_][WARN] Responding with 500 Internal Server Error catcher. Feb 09 20:26:34 sapphire systemd-docker[9754]: [2019-02-09 20:26:34][_][INFO] Response succeeded.
kerem closed this issue 2026-03-03 01:26:55 +03:00
kerem commented 2026-03-03 01:26:55 +03:00
Author
Owner
Copy link

@dani-garcia commented on GitHub (Feb 10, 2019):

Can you check the logs when you start the server? You should get something like this:

[2019-02-10 15:03:26][rocket::rocket][INFO] �   Mounting /admin:
[2019-02-10 15:03:26][_][INFO] GET /admin [2] (admin_login)
[2019-02-10 15:03:26][_][INFO] POST /admin (post_admin_login)
[2019-02-10 15:03:26][_][INFO] GET /admin (admin_page)
[2019-02-10 15:03:26][_][INFO] POST /admin/invite (invite_user)
[2019-02-10 15:03:26][_][INFO] POST /admin/users/<uuid>/delete (delete_user)
[2019-02-10 15:03:26][_][INFO] POST /admin/users/<uuid>/deauth (deauth_user)
[2019-02-10 15:03:26][_][INFO] POST /admin/config (post_config)
[2019-02-10 15:03:26][_][INFO] POST /admin/config/delete (delete_config)

It should be just slightly before the unofficial bitwarden warning.
If you get that in the logs, and the admin panel still gives that error it probably means that the ADMIN_TOKEN couldn't be found.

<!-- gh-comment-id:462136057 --> @dani-garcia commented on GitHub (Feb 10, 2019): Can you check the logs when you start the server? You should get something like this: ``` [2019-02-10 15:03:26][rocket::rocket][INFO] � Mounting /admin: [2019-02-10 15:03:26][_][INFO] GET /admin [2] (admin_login) [2019-02-10 15:03:26][_][INFO] POST /admin (post_admin_login) [2019-02-10 15:03:26][_][INFO] GET /admin (admin_page) [2019-02-10 15:03:26][_][INFO] POST /admin/invite (invite_user) [2019-02-10 15:03:26][_][INFO] POST /admin/users/<uuid>/delete (delete_user) [2019-02-10 15:03:26][_][INFO] POST /admin/users/<uuid>/deauth (deauth_user) [2019-02-10 15:03:26][_][INFO] POST /admin/config (post_config) [2019-02-10 15:03:26][_][INFO] POST /admin/config/delete (delete_config) ``` It should be just slightly before the unofficial bitwarden warning. If you get that in the logs, and the admin panel still gives that error it probably means that the ADMIN_TOKEN couldn't be found.
kerem commented 2026-03-03 01:26:56 +03:00
Author
Owner
Copy link

@Flameborn commented on GitHub (Feb 10, 2019):

After mounting the /api/ endpoints, I see:

Feb 10 14:14:32 sapphire systemd-docker[2731]: [2019-02-10 14:14:32][rocket::rocket][INFO] Mounting /admin:

There are no other admin-related mounts, the next line is an entry about mounting /identity.

<!-- gh-comment-id:462137552 --> @Flameborn commented on GitHub (Feb 10, 2019): After mounting the /api/ endpoints, I see: Feb 10 14:14:32 sapphire systemd-docker[2731]: [2019-02-10 14:14:32][rocket::rocket][INFO] Mounting /admin: There are no other admin-related mounts, the next line is an entry about mounting /identity.
kerem commented 2026-03-03 01:26:56 +03:00
Author
Owner
Copy link

@dani-garcia commented on GitHub (Feb 10, 2019):

That means that the admin_token wasn't detected, so the admin routes weren't mounted. Can you double check that you are setting the variable correctly? The docker steps are explained here: https://github.com/dani-garcia/bitwarden_rs/wiki/Enabling-admin-page

<!-- gh-comment-id:462140267 --> @dani-garcia commented on GitHub (Feb 10, 2019): That means that the admin_token wasn't detected, so the admin routes weren't mounted. Can you double check that you are setting the variable correctly? The docker steps are explained here: https://github.com/dani-garcia/bitwarden_rs/wiki/Enabling-admin-page
kerem commented 2026-03-03 01:26:56 +03:00
Author
Owner
Copy link

@Flameborn commented on GitHub (Feb 10, 2019):

I have a SystemD unit, which uses systemd-docker, the environment variables are set like this:

[Service]
TimeoutStartSec=0
Environment=SIGNUPS_ALLOWED=false ADMIN_TOKEN=RANDOM_STRING ...

The admin token has uppercase and lowercase letters, plus numbers only.

<!-- gh-comment-id:462141003 --> @Flameborn commented on GitHub (Feb 10, 2019): I have a SystemD unit, which uses systemd-docker, the environment variables are set like this: [Service] TimeoutStartSec=0 Environment=SIGNUPS_ALLOWED=false ADMIN_TOKEN=RANDOM_STRING ... The admin token has uppercase and lowercase letters, plus numbers only.
kerem commented 2026-03-03 01:26:56 +03:00
Author
Owner
Copy link

@dani-garcia commented on GitHub (Feb 10, 2019):

Can you check that the SIGNUPS_ALLOWED actually works? Our wiki recommends setting the EnvironmentFile, but I don't know a lot about systemd to actually now if that makes a difference.

You could also try to set both variables in different lines:
[Service]
TimeoutStartSec=0
Environment=SIGNUPS_ALLOWED=false
Environment=ADMIN_TOKEN=RANDOM_STRING

I think there is a possibility that systemd is interpreting everything after the first = like the value of the first variable.

<!-- gh-comment-id:462141353 --> @dani-garcia commented on GitHub (Feb 10, 2019): Can you check that the SIGNUPS_ALLOWED actually works? [Our wiki recommends](https://github.com/dani-garcia/bitwarden_rs/wiki/Setup-as-a-systemd-service) setting the `EnvironmentFile`, but I don't know a lot about systemd to actually now if that makes a difference. You could also try to set both variables in different lines: [Service] TimeoutStartSec=0 Environment=SIGNUPS_ALLOWED=false Environment=ADMIN_TOKEN=RANDOM_STRING I think there is a possibility that systemd is interpreting everything after the first `=` like the value of the first variable.
kerem commented 2026-03-03 01:26:56 +03:00
Author
Owner
Copy link

@Flameborn commented on GitHub (Feb 10, 2019):

According to this, the Environment directive allows a list of variable assignments, separated by spaces.

I've modified my unit file to have separate Environment directives, unfortunately, still no go.

systemctl show bitwarden prints a truncated line of environment variables, similarly to the way I had originally defined in the unit file.

<!-- gh-comment-id:462142967 --> @Flameborn commented on GitHub (Feb 10, 2019): According to [this](https://coreos.com/os/docs/latest/using-environment-variables-in-systemd-units.html), the Environment directive allows a list of variable assignments, separated by spaces. I've modified my unit file to have separate Environment directives, unfortunately, still no go. _systemctl show bitwarden_ prints a truncated line of environment variables, similarly to the way I had originally defined in the unit file.
kerem commented 2026-03-03 01:26:56 +03:00
Author
Owner
Copy link

@Flameborn commented on GitHub (Feb 10, 2019):

Found the issue.

According to the wiki, the --env directive can be omitted, however, this is only true if the environment variables are specified as arguments to the run command. As this was not the case for me, since I had the directives in the unit file, along with specified -e directives as well, adding --env passed them along, as it is documented [here](https://github.com/ibuildthecloud/systemd-docker]

<!-- gh-comment-id:462145118 --> @Flameborn commented on GitHub (Feb 10, 2019): Found the issue. According to [the wiki](https://github.com/dani-garcia/bitwarden_rs/wiki/Running-with-systemd-docker), the _--env_ directive can be omitted, however, this is only true if the environment variables are specified as arguments to the run command. As this was not the case for me, since I had the directives in the unit file, along with specified _-e_ directives as well, adding _--env_ passed them along, as it is documented [here](https://github.com/ibuildthecloud/systemd-docker]
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
revert-7033-patch-1
cached-config-operations
test_dylint
1.35.8
1.35.7
1.35.6
1.35.5
1.35.4
1.35.3
1.35.2
1.35.1
1.35.0
1.34.3
1.34.2
1.34.1
1.34.0
1.33.2
1.33.1
1.33.0
1.32.7
1.32.6
1.32.5
1.32.4
1.32.3
1.32.2
1.32.1
1.32.0
1.31.0
1.30.5
1.30.4
1.30.3
1.30.2
1.30.1
1.30.0
1.29.2
1.29.1
1.29.0
1.28.1
1.28.0
1.27.0
1.26.0
1.25.2
1.25.1
1.25.0
1.24.0
1.23.1
1.23.0
1.22.2
1.22.1
1.22.0
1.21.0
1.20.0
1.19.0
1.18.0
1.17.0
1.16.3
1.16.2
1.16.1
1.16.0
1.15.1
1.15.0
1.14.2
1.14.1
1.14
1.13.1
1.13.0
1.12.0
1.11.0
1.10.0
1.9.1
1.9.0
1.8.0
1.7.0
1.6.1
1.6.0
1.5.0
1.4.0
1.3.0
1.2.0
1.1.0
1.0.0
0.13.0
0.12.0
0.11.0
0.10.0
0.9.0
Labels
Clear labels   
SSO

   
Third party

   
better for forum

   
bug

   
bug

   
documentation

   
duplicate

   
enhancement

   
future Vault

   
future Vault

   
future Vault

   
good first issue

   
help wanted

   
low priority

   
notes

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
troubleshooting

   
wontfix
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vaultwarden#225
No description provided.