starred/vaultwarden

Fork 0

mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-25 17:25:57 +03:00

[GH-ISSUE #6238] CORS error 200 when tried to generate Firefox Relay mail #2378

New issue

Closed

opened 2026-03-03 02:17:46 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 02:17:46 +03:00

Owner

Originally created by @oboeglen on GitHub (Aug 27, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6238

Prerequisites

I have searched the existing Closed AND Open Issues AND Discussions
I have searched and read the documentation

Vaultwarden Support String

No diag

Vaultwarden Build Version

testing

Deployment method

Official Container Image

Custom deployment method

No response

Reverse Proxy

Apache

Host/Server Operating System

Linux

Operating System Version

Debian 12

Clients

Web Vault

Client Version

No response

Steps To Reproduce

Go to Tools and Add Username generator with Firefox Relay

Expected Result

Custom mail address

Actual Result

Blocage d’une requête multiorigines (Cross-Origin Request) : la politique « Same Origin » ne permet pas de consulter la ressource distante située sur https://relay.firefox.com/api/v1/relayaddresses/. Raison : l’en-tête CORS « Access-Control-Allow-Origin » est manquant. Code d’état : 200.

Blocage d’une requête multiorigine (Cross-Origin Request) : la politique « Same Origin » ne permet pas de consulter la ressource distante située sur https://relay.firefox.com/api/v1/relayaddresses/. Raison : échec de la requête CORS. Code d’état : (null).

TypeError: NetworkError when attempting to fetch resource. console-log.service.ts:51:17

Logs

Screenshots or Videos

No response

Additional Context

No response

Originally created by @oboeglen on GitHub (Aug 27, 2025). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6238 ### Prerequisites - [x] I have searched the existing **Closed _AND_ Open** [Issues](https://github.com/dani-garcia/vaultwarden/issues?q=is%3Aissue%20) **_AND_** [Discussions](https://github.com/dani-garcia/vaultwarden/discussions?discussions_q=) - [x] I have searched and read the [documentation](https://github.com/dani-garcia/vaultwarden/wiki/) ### Vaultwarden Support String No diag ### Vaultwarden Build Version testing ### Deployment method Official Container Image ### Custom deployment method _No response_ ### Reverse Proxy Apache ### Host/Server Operating System Linux ### Operating System Version Debian 12 ### Clients Web Vault ### Client Version _No response_ ### Steps To Reproduce Go to Tools and Add Username generator with Firefox Relay ### Expected Result Custom mail address ### Actual Result Blocage d’une requête multiorigines (Cross-Origin Request) : la politique « Same Origin » ne permet pas de consulter la ressource distante située sur https://relay.firefox.com/api/v1/relayaddresses/. Raison : l’en-tête CORS « Access-Control-Allow-Origin » est manquant. Code d’état : 200. Blocage d’une requête multiorigine (Cross-Origin Request) : la politique « Same Origin » ne permet pas de consulter la ressource distante située sur https://relay.firefox.com/api/v1/relayaddresses/. Raison : échec de la requête CORS. Code d’état : (null). TypeError: NetworkError when attempting to fetch resource. [console-log.service.ts:51:17](webpack://bitwarden/libs/logging/src/console-log.service.ts) ### Logs ```text ``` ### Screenshots or Videos _No response_ ### Additional Context _No response_

kerem

2026-03-03 02:17:46 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-03 02:17:47 +03:00

Author

Owner

@BlackDex commented on GitHub (Aug 27, 2025):

CORS errors are never solvable by the server side.
The receiving endpoint needs to allow these.

Also, these are client-side items and this project does not maintain the client-side.

There already is an open issue at Bitwarden regarding this: https://github.com/bitwarden/clients/issues/14011
But it doesn't seem to be a priority or an issue for other self-hosted customers.

@BlackDex commented on GitHub (Aug 27, 2025): CORS errors are never solvable by the server side. The receiving endpoint needs to allow these. Also, these are client-side items and this project does not maintain the client-side. There already is an open issue at Bitwarden regarding this: https://github.com/bitwarden/clients/issues/14011 But it doesn't seem to be a priority or an issue for other self-hosted customers.

kerem referenced this issue

2026-03-03 09:25:46 +03:00

[PR #2379] [MERGED] Several updates and fixes #3083