mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
organization vault and members pages hang; 500 internal error #2115
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 @ebdavison on GitHub (Dec 19, 2024).
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Failed HTTP Checks:
Config:
Vaultwarden Build Version
1.32.6
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
nginx 1.22.1
Host/Server Operating System
Linux
Operating System Version
Fedora 35
Clients
Web Vault
Client Version
No response
Steps To Reproduce
Expected Result
vault items and/or member list to show up
Actual Result
erros in console
Logs
Screenshots or Videos
Additional Context
No response
@BlackDex commented on GitHub (Dec 19, 2024):
It shows an internal server error. Could you provide the Vaultwarden logs please.
And if you see nothing strange the set the
LOG_LEVELtodebugand try again.You should at least have some logs of Vaultwarden which shows the request is being made. Same btw for nginx, the request should be seen there.
@ebdavison commented on GitHub (Dec 19, 2024):
Nothing in the vaultwarden logs. I will set the
LOG_LEVELand see what shows up.@ebdavison commented on GitHub (Dec 19, 2024):
@ebdavison commented on GitHub (Dec 19, 2024):
and the matching nginx logs:
@BlackDex commented on GitHub (Dec 19, 2024):
That is a very strange issue. While the code could made a bit more safe, this actually could never happen unless the database is corrupted or someone deleted a user manually with foreign keys disabled.
@BlackDex commented on GitHub (Dec 20, 2024):
Since this would cause inaccurate data and seems like a serious database issue on which Vaultwarden could not do anything it self. We have Foreign Keys enabled for a reason to prevent these kind of issue.
And, this is not an actual bug in Vaultwarden per say, as we would probably still panic here or error out, I'm going to move this to discussions.
I would suggest to check the integerty of the database and try to figure out which user is still a member of the org but not in the
userstable anymore.