-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to generate forwarded email aliases via Firefox Relay in generator tool #9143
Comments
Hello @dvejmz, Thank you for your report. I was able to reproduce this behaviour and have flagged it to the Engineering department. Thank you again, |
I have the same error |
1 similar comment
I have the same error |
I'm able to reproduce the error through the bitwarden extension as well. I really loved the integration there! |
Same error here as well. Use it a lot, and the Bitwarden extension is a big convenience and makes it really easy. Would love to see this fixed! |
Something that I've realized is that in Firefox at least, it looks like in most email text boxes when you right click have the option for "Use Relay Email Mask" which automatically generates and fills the line with a mask. Seems like a pretty nice stop gap, although I do like the idea of having a more universal option through Bitwarden. |
Steps To Reproduce
Expected Result
The generator generates a new, valid Firefox Relay email alias linked with my Firefox Relay account and displays it on screen.
Actual Result
The generator doesn't generate anything. Instead, the following error toast appears: "Unknown Firefox Relay error occurred.".
Screenshots or Videos
Additional Context
Upon inspection on my browser devtools network tab, I can see the web client sends the following request to the Firefox Relay API servers.
And the response it gets back from the Firefox Relay servers is a HTTP 400 with the following message
Operating System
Linux
Operating System Version
No response
Web Browser
Firefox
Browser Version
125.0.3
Build Version
2024.4.2
Issue Tracking Info
The text was updated successfully, but these errors were encountered: