mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #1770] Email Verification Results in 404 #1055
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#1055
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 @lolcatlolcat on GitHub (Jun 16, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1770
Trying to use the email verification feature of vaultwarden but everytime the user receives the link via email, the link just takes them to a 404 page. Nothing I can see in the logs offhand that immediately point to some issue, any ideas?
Vaultwarden is running in docker on debian buster and frontended by an Haproxy instance fwiw.
@BlackDex commented on GitHub (Jun 16, 2021):
You either are using a very very old version of vaultwarden (previously bitwarden_rs), or the reverse proxy is not allowing something. Could you post the Support string from the /admin/diagnostics page, and also some of the logs during the time this request was done?
@lolcatlolcat commented on GitHub (Jun 16, 2021):
I updated to the latest version of
vaultwardenthis morning so it shouldn't be a version issue.Here is the support string info:
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
I'm trying to get some logs but
docker logs -f vaultwardenisn't showing me anything past my successful login, Even when I get the 404, it's not being reflected in the output there. Should I look somewhere else?@BlackDex commented on GitHub (Jun 19, 2021):
Try to check your reverse proxy logs.