mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-11 09:13:02 +03:00
New organisation results in "GET /api/plans => 401 Unauthorized" #1038
Reference in New Issue
Block a user
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?
Originally created by @bhenstra on GitHub.
New organisation results in "GET /api/plans => 401 Unauthorized"
Running vaultwarden and vaultwaden-web on Arch Linux:
When I click the button "+ New organisation" the "New organisation" text is visible with a animated gif / loading indicator.
In the log file there's the following eror:
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, SENDS_ALLOWED, ADMIN_TOKEN, INVITATION_ORG_NAME, IP_HEADER, LOG_TIMESTAMP_FORMAT, DISABLE_ADMIN_TOKEN, SMTP_HOST, SMTP_SECURITY, SMTP_PORT, SMTP_FROM, SMTP_FROM_NAME, SMTP_USERNAME, SMTP_PASSWORD, SMTP_AUTH_MECHANISM, SMTP_TIMEOUT, SMTP_ACCEPT_INVALID_CERTS
Install method: pacman
Clients used: web vault
Reverse proxy and version: Caddy v2.6.1
MySQL/MariaDB or PostgreSQL version: not applicable
Other relevant details: I did install Vaultwarden + Vaultwarden-Web and Caddy on Arch Linux before. I have two servers running like this. I am not sure why this error appears and I am hoping you can help. Please let me know if I have to provide more details. Thank you.

Steps to reproduce
Click "+ New organisation"
Expected behaviour
Create a new organisation.
Actual behaviour
When I click the button "+ New organisation" the "New organisation" text is visible with a animated gif / loading indicator.
Troubleshooting data
caddy config (note: real domain name has been removed)
file: /etc/caddy/conf.d/real.domain-name-replaced.com
file: /etc/caddy/caddy_security.conf
@BlackDex commented on GitHub:
First, those headers set by caddy could break some functionality.
Second, it looks like that Vaultwarden version you are using isn't supporting the 2022.9.0 web-vault version. I think the Vaultwarden version is matching the released version and not the master branch.
That would cause the issue you have currently.
Either install a git release of Vaultwarden, or revert to the latest 2022.8.x web-vault.