mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 17:55:58 +03:00
[GH-ISSUE #2737] Unable to create an organization with web-vault v2022.9.0 #1362
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#1362
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @ecesarini on GitHub (Sep 12, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2737
Hi,
I upgraded my web-vault to v2022.9.0 and get an error trying to add new organization in web vault.
The page shows an infinite loading spinning wheel. In browser console you can see some errors about uncaught promise in js.
I'm running docker container with vaultwarden v1.25.2. The problem didn't occur with previous web-vault v2022.8.1.
Maybe could it be related to the latest commits in the vaultwarden currently not included in my vaultwarden docker image?
I attached two screenshots about the error.
thank you very much,
EC
@BlackDex commented on GitHub (Sep 12, 2022):
If you want to use the latest version i suggest to use the Vaultwarden
testingtagged images.@ecesarini commented on GitHub (Sep 12, 2022):
Thank you,
I pulled the latest vaultwarden:testing (1.25.2-edca4248) image and I've run a new container but I get the same error when I try to add a new organization.
I'm not running a custom rebuilt web-vault, I'm using the latest relased v2022.9.0 in the bw_web_builds project.
Thank you again.
@BlackDex commented on GitHub (Sep 12, 2022):
Aren't you using the web-vault from the Vaultwarden container??
Also check the reverse proxy. Maybe something is going wrong there?
@BlackDex commented on GitHub (Sep 12, 2022):
Confirmed
@BlackDex commented on GitHub (Sep 12, 2022):
@ecesarini thanks for reporting this issue. This was a small oversight during the checks when supporting the latest web-vault.
I created a PR already which fixes this issue. #2738