mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #6486] DuckDuckGo Email alias can not be generated #2448
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#2448
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 @bibi0019 on GitHub (Nov 23, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6486
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, EMERGENCY_ACCESS_ALLOWED, EMAIL_CHANGE_ALLOWED, ADMIN_TOKEN, INVITATION_ORG_NAME, IP_HEADER
Config:
Vaultwarden Build Version
v1.34.3
Deployment method
Manually Extracted from Container Image
Custom deployment method
No response
Reverse Proxy
caddy 2.10.2
Host/Server Operating System
Linux
Operating System Version
Ubuntu 22.04 LTS
Clients
Web Vault
Client Version
No response
Steps To Reproduce
Expected Result
The Email Alias will be generated
Actual Result
The email alias is not generated due to Content Security Policy
Logs
Screenshots or Videos
Additional Context
I've found that the api https://quack.duckduckgo.com/api/email/addresses is not included in Content Security Policy located in
github.com/dani-garcia/vaultwarden@319d982113/src/util.rs (L119)@BlackDex commented on GitHub (Nov 23, 2025):
Not something we can fix, DDG also does a CORS check, which we can't fix.
No Self-Hosted instance of Bitwarden is able to use this feature, that includes Vaultwarden too.
See: https://github.com/bitwarden/clients/issues/14011