github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-07-21 17:42:44 -05:00
Code Issues 534 Packages Projects Releases 83 Wiki Activity

Refused to connect to 'https://api.bitwarden.com/accounts/profile' because it violates the document's Content Security Policy. #5125

New Issue
Closed
opened 2026-03-07 20:13:35 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-03-07 20:13:35 -06:00
Owner
Copy Link
Copy Source

Originally created by @florian-sabonchi on GitHub (Jan 26, 2023).

Subject of the issue

  • vaultwarden version: Version 1.27.0

  • Install method: Docker

  • Clients used: web

  • Reverse proxy and version: treafik

  • MySQL/MariaDB or PostgreSQL version: Postgres

  • Other relevant details: Version 2022.12.0

Steps to reproduce

login to vault warden sometimes passwords are empty

Expected behaviour

passwords should be loaded

Actual behaviour

passwords are not loaded-->

Troubleshooting data

Originally created by @florian-sabonchi on GitHub (Jan 26, 2023). <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue <!-- Sometimes if i try to login to vaultwarden passwords are empty and i receive the following error: Refused to connect to 'https://api.bitwarden.com/accounts/profile' because it violates the document's Content Security Policy.- ERROR Error: Uncaught (in promise): TypeError: Failed to fetch TypeError: Failed to fetch-> ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: Version 1.27.0 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: Docker * Clients used: web * Reverse proxy and version: treafik * MySQL/MariaDB or PostgreSQL version: Postgres * Other relevant details: Version 2022.12.0 ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> login to vault warden sometimes passwords are empty ### Expected behaviour passwords should be loaded ### Actual behaviour passwords are not loaded--> ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->
GiteaMirror commented 2026-03-07 20:13:35 -06:00
Author
Owner
Copy Link
Copy Source

@florian-sabonchi commented on GitHub (Jan 26, 2023):

Screenshot from 2023-01-26 10-22-17

@florian-sabonchi commented on GitHub (Jan 26, 2023): ![Screenshot from 2023-01-26 10-22-17](https://user-images.githubusercontent.com/54689374/214801370-7242da7b-bb2c-4009-83c8-51cd0fad7935.png)
GiteaMirror commented 2026-03-07 20:13:36 -06:00
Author
Owner
Copy Link
Copy Source

@BlackDex commented on GitHub (Jan 26, 2023):

I'm not sure what you are trying to do, but Vaultwarden never ever connects to api.bitwarden.com for anything.
There is just one feature which could cause Vaultwarden to do anything on a Bitwarden endpoint, and those are the favicon's if you configure that you want to use there icon fetching endpoint.

Other then that, all should be fully independent from any Bitwarden endpoint.

I suggest to double check your docker/reverse-proxy configuration.

@BlackDex commented on GitHub (Jan 26, 2023): I'm not sure what you are trying to do, but Vaultwarden never ever connects to `api.bitwarden.com` for anything. There is just one feature which could cause Vaultwarden to do anything on a Bitwarden endpoint, and those are the favicon's if you configure that you want to use there icon fetching endpoint. Other then that, all should be fully independent from any Bitwarden endpoint. I suggest to double check your docker/reverse-proxy configuration.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
wontfix
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#5125