mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-11 09:13:02 +03:00
Unexpected "email domain not eligible for invitations" failure #1598
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 @bland328 on GitHub.
Subject of the issue
I've run into just one email address that I can't invite to Bitwarden_rs because of an
Email domain not eligible for invitationserror. The email address is question is a valid gmail.com address, and I've had no problem with other gmail.com addresses.Your environment
Steps to reproduce
When logged in to the Bitwarden_rs web interface as Owner, I attempt to invite "xxxxxxxxx99@gmail.com"
(I've redacted the real address, which is nine lowercase alpha characters followed by two digits.)
Expected behaviour
It should work, just like all the other invitations I've sent, including one to "xxxxx99@gmail.com"
(fewer alpha characters in this case, but otherwise the same form as above.)
Actual behaviour
This error message slides in from the right:
An error has occurred.Email domain not eligible for invitationsRelevant logs
These four lines (the third being blank) are logged when I click Save.
(I've redacted the UUID in the first line.)
[2020-09-29 11:05:32.140][request][INFO] POST /api/organizations/[REDACTED_UUID]/users/invite[2020-09-29 11:05:32.141][error][ERROR] Email domain not eligible for invitations[2020-09-29 11:05:32.141][response][INFO] POST /api/organizations/<org_id>/users/invite (send_invite) => 400 Bad RequestAdditional information
Since running into this problem, I've successfully invited other
@gmail.comaccounts, but this particular address continues to fail.Also, I haven't yet tried restarting the Docker container. I realize that might put things right, but I'm hanging on for now in case I can collect useful troubleshooting data before I do that.
I'm happy to collect any additional information that might help troubleshoot this. Thanks for any assistance.
@bland328 commented on GitHub:
Makes sense. Sorry for the false alarm, and thanks greatly for your help!
@bland328 commented on GitHub:
Ah-ha! Thank you--I do have domains restricted, which I apparently did long ago upon initial set up, and forgot about.
What threw me off was that I do already have an @gmail.com user successfully invited, which I must've forgotten was done from the admin interface.
I was able to successfully invite the new @gmail.com user via the admin interface, despite the domain whitelist setting--is that intentional?
@BlackDex commented on GitHub:
Do you have anything configured regarding allowed domains? Or not inviting users? Are you able to invite the user via the admin interface?
@jjlin commented on GitHub:
Yes, the admin page generally ignores any configured restrictions, considering anyone with access to the admin page can disable those restrictions anyway.