mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #737] missing information in email invite #500
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#500
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 @josuemotte on GitHub (Nov 20, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/737
Hello,
We upgraded the docker image to the latest version and it seems that all verification emails are sent without the join organization link, while the github link is still working
According to the source of the email, it seems that the verification is well formatted but somehow, no matter the client, the link doesn't show up correctly :
email_issue.txt
Are there any change we need to make on our side to get the email verification work again ?
Thanks
@tomuta commented on GitHub (Nov 20, 2019):
What is your
DOMAINenvironment variable set to? Based on the attached file it looks like it may be set to something likeDOMAIN="xxxxxx". It should be without double quotes likeDOMAIN=xxxxxx.@josuemotte commented on GitHub (Nov 20, 2019):
I've changed it but no luck still the same issue, it was "prout.io" now it's prout.io
@dani-garcia commented on GitHub (Nov 20, 2019):
According to that email source, DOMAIN is set to
"https://bitwarden.prout.rocks", quotes included. The rest of the URL seems correct to me, check the value from the admin page to see if there are quotes there too.@josuemotte commented on GitHub (Nov 20, 2019):
Strange it was still in the admin page, it's fixed thank you