Since the last update to 1.28.0 I have noticed the following warning message in the log of Vaultwarden whenever I access the admin page or log out of it:
[2023-03-31 19:04:06.058][rocket::server::_][WARN] Responding with registered (admin_login) /admin 401 catcher.
However, I have no problems with the actual login. What is the reason for these messages?
In order to implement the redirection to the login page (i.e. for other pages in the admin panel like opening /admin/organizations/overview) we switched from Rocket’s forwarding mechanism to explicit error catching:
So now the server checks if you are authorized already and displays the login page (with the information which page you tried to open) in case you are not.
Perhaps I have not noticed it until now. Can the message then be ignored? Since they appear as a warning, I was wondering if I need to change something in my configuration. I think it is the normal state when visiting the admin page and not logged in.
I updated from version 1.27.x to version 1.28.0 and then to 1.28.1. Just successfully changed the clear text ADMIN_TOKEN to an argon2 based token using the docker command line and the Admin panel. Login works fine, but I also get the following warnings in the vaultwarden log files, when login into the admin interface:
11.04.2023 7:20:53 /--------------------------------------------------------------------
11.04.2023 7:20:53 | Starting Vaultwarden |
11.04.2023 7:20:53 | Version 1.28.1 |
11.04.2023 7:20:53 |--------------------------------------------------------------------|
11.04.2023 7:20:53 | This is an unofficial Bitwarden implementation, DO NOT use the |
11.04.2023 7:20:53 | official channels to report bugs/features, regardless of client. |
11.04.2023 7:20:53 | Send usage/configuration questions or feature requests to: |
11.04.2023 7:20:53 | dani-garcia/vaultwarden · Discussions · GitHub or |
11.04.2023 7:20:53 | https://vaultwarden.discourse.group/ |
11.04.2023 7:20:53 | Report suspected bugs/issues in the software itself at: |
11.04.2023 7:20:53 | Sign in to GitHub · GitHub |
11.04.2023 7:20:53 --------------------------------------------------------------------/
11.04.2023 7:20:53
11.04.2023 7:20:53 [INFO] Using saved config from data/config.json for configuration.
11.04.2023 7:20:53
11.04.2023 7:20:53 [WARNING] The following environment variables are being overriden by the config.json file.
11.04.2023 7:20:53 [WARNING] Please use the admin panel to make changes to them:
11.04.2023 7:20:53 [WARNING] ADMIN_TOKEN
11.04.2023 7:20:53
11.04.2023 7:21:11 [2023-04-11 05:21:11.742][vaultwarden::api::admin::][WARN] Request guard AdminToken failed: “Unauthorized”.
11.04.2023 7:21:11 [2023-04-11 05:21:11.742][rocket::server::][WARN] Responding with registered (admin_login) /admin 401 catcher.
11.04.2023 7:21:11 [2023-04-11 05:21:11.742][vaultwarden::api::admin][ERROR] Authorization failed.
11.04.2023 7:21:13 [2023-04-11 05:21:13.050][vaultwarden::api::admin::][WARN] Request guard AdminToken failed: “Unauthorized”.
11.04.2023 7:21:13 [2023-04-11 05:21:13.050][rocket::server::][WARN] Responding with registered (admin_login) /admin 401 catcher.
11.04.2023 7:24:34 [2023-04-11 05:24:34.654][vaultwarden::api::admin::][WARN] Request guard AdminToken failed: “Unauthorized”.
11.04.2023 7:24:34 [2023-04-11 05:24:34.654][rocket::server::][WARN] Responding with registered (admin_login) /admin 401 catcher.
Is there anything left I need to reconfigure to get rid of these?
Please note: WEBSOCKET_ENABLED=false