# Bitwarden/Vaultwarden can’t connect on Windows via Browser-plugin

**URL:** <https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563>\
**Category:** Help\
**Created:** [April 13, 2022, 9:55am UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563 "2022-04-13T09:55:56Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![buchy](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@buchy](https://vaultwarden.discourse.group/u/buchy)\
**Post date:** [April 13, 2022, 9:55am UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563/1 "2022-04-13T09:55:56Z")

</div>

Hi,  
i need help with my selfhosted Vaultwarden on Synology NAS. I’ll set everything up on the NAS/reverse proxy etc., it works on NAS, on all android devices but not on windows Browsers such as Chrome, FF, Opera on their plugin Bitwarden.

When i setup Bitwarden connection to my NAS i still get Error mesage: failed to fetch.

any idea why it doesn’t want to work?

Thanks for help.

---

<div class="post-metadata">

**Author:** ![cksapp](https://avatars.discourse-cdn.com/v4/letter/c/b9e5f3/32.png) [@cksapp](https://vaultwarden.discourse.group/u/cksapp)\
**Post date:** [April 13, 2022, 3:59pm UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563/2 "2022-04-13T15:59:19Z")

</div>

Perhaps more detail would be of assistance to diagnose the issue here.  
I presume as you’ve said you successfully got the android applications to work you are familiar with [setting the URL for your self-hosted instance](https://bitwarden.com/help/change-client-environment/).

Can you confirm you’ve done this for the browser extensions? Is your Vaultwarden publicly accessible or is it only a private instance?  
How are you trying to connect, with IP or hostname? And do you have a valid certificate installed?

---

<div class="post-metadata">

**Author:** ![buchy](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@buchy](https://vaultwarden.discourse.group/u/buchy)\
**Post date:** [April 13, 2022, 4:44pm UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563/3 "2022-04-13T16:44:33Z")

</div>

Hi,

Yes the selfhosted vaultwarden is publicly accessible with valid certificate. I connect via ddns hostname - it works via web and android app, but on windows via Browsers plugin dont.

 ![SmartSelect_20220413-184044_Opera](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/2cc4f69cc2f1bdd3dc41cb4d426d70f7112c938b.jpeg)

Sorry for the screenshot it is in slovak language.  
I dont understand it works publicly via web, on android Phone/ Tablet but on any windows Browser: Chrome/Opera/FF dont.

I try connect via external IP and i get the error 404 not found nginx

---

<div class="post-metadata">

**Author:** ![stefan0xC](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/stefan0xc/32/1765_2.png) [@stefan0xC](https://vaultwarden.discourse.group/u/stefan0xC)\
**Post date:** [April 13, 2022, 10:07pm UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563/4 "2022-04-13T22:07:15Z")

</div>

You have not answered if you have [connected the extension](https://bitwarden.com/help/change-client-environment/) to your server?  
I.d. if you have filled out this field:  
 ![Setting the Server URL](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/986ecade8f209173439bbc2c61403853b0023be8.png)

---

<div class="post-metadata">

**Author:** ![buchy](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@buchy](https://vaultwarden.discourse.group/u/buchy)\
**Post date:** [April 13, 2022, 10:43pm UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563/5 "2022-04-13T22:43:52Z")

</div>

Yes i have connected the extensions in bitwarden plugin for webBrowsers same as in the android app.

 ![2022_04_14_00_46_54_](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/a5ea1ab055867aac0847084d522c6f4bee89616f.jpeg)

The Point is selfhosted Vaultwarden works well but only on android app Bitwarden with all the necessary settings, not on windows webBrowser Chrome etc… Bitwarden plugin! and i do not know why?  
i get the Error failed to fetch.

---

<div class="post-metadata">

**Author:** ![cksapp](https://avatars.discourse-cdn.com/v4/letter/c/b9e5f3/32.png) [@cksapp](https://vaultwarden.discourse.group/u/cksapp)\
**Post date:** [April 14, 2022, 1:26am UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563/6 "2022-04-14T01:26:29Z")

</div>

I am assuming with using a duckdns subdomain, is this duckdns subdomain only used for the Vaultwarden service?  
Or do you know if this was bound to a specific port or subdir/sub-path?

---

<div class="post-metadata">

**Author:** ![buchy](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@buchy](https://vaultwarden.discourse.group/u/buchy)\
**Post date:** [April 14, 2022, 6:32am UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563/7 "2022-04-14T06:32:06Z")

</div>

Its only for the Vaultwarden.

---

<div class="post-metadata">

**Author:** ![jjlin](https://avatars.discourse-cdn.com/v4/letter/j/e19adc/32.png) [@jjlin](https://vaultwarden.discourse.group/u/jjlin)\
**Post date:** [April 14, 2022, 6:57am UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563/8 "2022-04-14T06:57:21Z")

</div>

Put the Bitwarden browser extension into developer mode ([Frequently asked questions - Chrome Developers](https://developer.chrome.com/docs/extensions/mv3/faq/#faq-dev-01)). A new `Inspect views` section should appear, with a clickable “background.html” link that opens up a DevTools view that shows the network log. Attempting to log in should now show what failed to fetch.

 ![image](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/8efedb6f4b6c0ce5dfb0680edc6536b8fdcc3a98.png)

---

<div class="post-metadata">

**Author:** ![buchy](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@buchy](https://vaultwarden.discourse.group/u/buchy)\
**Post date:** [April 14, 2022, 8:24am UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563/9 "2022-04-14T08:24:03Z")

</div>

Hi, i found this see below, and I didn’t know much about that 😕

 ![obrázok_2022-04-14_102324566](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/7ba5e74a9ed558bc5e1d4b1cbd87013eae2a3096.png)

---

<div class="post-metadata">

**Author:** ![buchy](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@buchy](https://vaultwarden.discourse.group/u/buchy)\
**Post date:** [April 14, 2022, 8:34am UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563/10 "2022-04-14T08:34:13Z")

</div>

![2022_04_14_10_31_04_DevTools_chrome_extension_ccnckbpmaceehanjmeomladnmlffdjgn_background.html_](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/29bbffa6b007ff30eccbe0762ee048f33c2ee527.jpeg)

---

<div class="post-metadata">

**Author:** ![buchy](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@buchy](https://vaultwarden.discourse.group/u/buchy)\
**Post date:** [April 14, 2022, 8:51am UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563/11 "2022-04-14T08:51:45Z")

</div>

![2022_04_14_10_48_21_DevTools_chrome_extension_ccnckbpmaceehanjmeomladnmlffdjgn_background.html_](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/3856a9a1bcf2b183fe2f4266f0f6aceda839eb43.jpeg)

---

<div class="post-metadata">

**Author:** ![jjlin](https://avatars.discourse-cdn.com/v4/letter/j/e19adc/32.png) [@jjlin](https://vaultwarden.discourse.group/u/jjlin)\
**Post date:** [April 14, 2022, 9:31am UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563/12 "2022-04-14T09:31:38Z")

</div>

You should look at the `Network` tab. Your prelogin call failed, but you didn’t show the full path.

You can also look at your Vaultwarden log for failed prelogin requests. You might be encountering

> <https://github.com/dani-garcia/vaultwarden/issues/2378>
>
> \<!--
> # ###
> NOTE: Please update to the latest version of vaultwarden be…fore 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
> Bitwarden CLI (version 1.22.0 - the latest on Arch Linux) login to the Vaultwarden server fails even with correct credentials
> 
> \### Deployment environment
> 
> \### Your environment (Generated via diagnostics page)
> \* Vaultwarden version: v1.24.0
> \* Web-vault version: v2.25.1
> \* Running within Docker: true (Base: Debian)
> \* Environment settings overridden: false
> \* Uses a reverse proxy: true
> \* IP Header check: true (X-Real-IP)
> \* Internet access: true
> \* Internet access via a proxy: false
> \* DNS Check: true
> \* Time Check: true
> \* Domain Configuration Check: false
> \* HTTPS Check: false
> \* Database type: MySQL
> \* Database version: 10.5.15-MariaDB-log
> \* Clients used: Bitwarden CLI version 1.22.0
> \* Reverse proxy and version: Nginx (latest from lscr.io/linuxserver/swag)
> \* Other relevant information: 
> 
> \### Config (Generated via diagnostics page)
> \<details\>\<summary\>Show Running Config\</summary\>
> 
> \*\*Environment settings which are overridden:\*\* 
> 
> \`\`\`json
> {
> "\_duo\_akey": null,
> "\_enable\_duo": false,
> "\_enable\_email\_2fa": true,
> "\_enable\_smtp": true,
> "\_enable\_yubico": true,
> "\_ip\_header\_enabled": true,
> "admin\_ratelimit\_max\_burst": 3,
> "admin\_ratelimit\_seconds": 300,
> "admin\_token": "\*\*\*",
> "allowed\_iframe\_ancestors": "",
> "attachments\_folder": "data/attachments",
> "authenticator\_disable\_time\_drift": false,
> "data\_folder": "data",
> "database\_max\_conns": 10,
> "database\_url": "\*\*\*\*\*://\*\*\*\*\*\*\*\*\*\*\*:\*\*\*\*\*\*\*\*\*\*\*\*\*@\*\*\*\*\*\*\*/\*\*\*\*\*\*\*\*\*\*\*",
> "db\_connection\_retries": 15,
> "disable\_2fa\_remember": false,
> "disable\_admin\_token": false,
> "disable\_icon\_download": false,
> "domain": "\*\*\*\*://\*\*\*\*\*\*\*\*\*",
> "domain\_origin": "\*\*\*\*://\*\*\*\*\*\*\*\*\*",
> "domain\_path": "",
> "domain\_set": false,
> "duo\_host": null,
> "duo\_ikey": null,
> "duo\_skey": null,
> "email\_attempts\_limit": 3,
> "email\_expiration\_time": 600,
> "email\_token\_size": 6,
> "emergency\_access\_allowed": true,
> "emergency\_notification\_reminder\_schedule": "0 5 \* \* \* \*",
> "emergency\_request\_timeout\_schedule": "0 5 \* \* \* \*",
> "enable\_db\_wal": true,
> "extended\_logging": true,
> "helo\_name": null,
> "hibp\_api\_key": null,
> "icon\_blacklist\_non\_global\_ips": true,
> "icon\_blacklist\_regex": null,
> "icon\_cache\_folder": "data/icon\_cache",
> "icon\_cache\_negttl": 259200,
> "icon\_cache\_ttl": 2592000,
> "icon\_download\_timeout": 10,
> "icon\_redirect\_code": 302,
> "icon\_service": "internal",
> "incomplete\_2fa\_schedule": "30 \* \* \* \* \*",
> "incomplete\_2fa\_time\_limit": 3,
> "invitation\_org\_name": "Vaultwarden",
> "invitations\_allowed": false,
> "ip\_header": "X-Real-IP",
> "job\_poll\_interval\_ms": 30000,
> "log\_file": null,
> "log\_level": "Info",
> "log\_timestamp\_format": "%Y-%m-%d %H:%M:%S.%3f",
> "login\_ratelimit\_max\_burst": 10,
> "login\_ratelimit\_seconds": 60,
> "org\_attachment\_limit": null,
> "org\_creation\_users": "",
> "password\_iterations": 100000,
> "reload\_templates": false,
> "require\_device\_email": false,
> "rsa\_key\_filename": "data/rsa\_key",
> "send\_purge\_schedule": "0 5 \* \* \* \*",
> "sends\_allowed": true,
> "sends\_folder": "data/sends",
> "show\_password\_hint": false,
> "signups\_allowed": false,
> "signups\_domains\_whitelist": "",
> "signups\_verify": false,
> "signups\_verify\_resend\_limit": 6,
> "signups\_verify\_resend\_time": 3600,
> "smtp\_accept\_invalid\_certs": false,
> "smtp\_accept\_invalid\_hostnames": false,
> "smtp\_auth\_mechanism": null,
> "smtp\_debug": false,
> "smtp\_explicit\_tls": false,
> "smtp\_from": "\*\*\*\*\*\*\*\*\*@\*\*\*.\*\*",
> "smtp\_from\_name": "Vaultwarden",
> "smtp\_host": "\*\*\*\*\*\*\*\*\*\*",
> "smtp\_password": null,
> "smtp\_port": 8025,
> "smtp\_ssl": false,
> "smtp\_timeout": 15,
> "smtp\_username": null,
> "templates\_folder": "data/templates",
> "trash\_auto\_delete\_days": null,
> "trash\_purge\_schedule": "0 5 0 \* \* \*",
> "use\_syslog": false,
> "user\_attachment\_limit": null,
> "web\_vault\_enabled": true,
> "web\_vault\_folder": "web-vault/",
> "websocket\_address": "0.0.0.0",
> "websocket\_enabled": true,
> "websocket\_port": 3012,
> "yubico\_client\_id": null,
> "yubico\_secret\_key": null,
> "yubico\_server": null
> }
> \`\`\`
> \</details\>
> 
> 
> 
> 
> \* vaultwarden version: 1.24.0
> 
> 
> \* Install method: Official docker image using \`docker-compose\`
> 
> \* Clients used: 
> Bitwarden CLI 1.22.0
> 
> \* Reverse proxy and version:
> Nginx (the latest version from lscr.io/linuxserver.io/swag)
> 
> \* MySQL/MariaDB or PostgreSQL version: MariaDB 10.5.15 (lscr.io/linuxserver/mariadb docker container)
> 
> \* Other relevant details:
> 
> \### 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? --\>
> \* Start the latest version of \`vaultwarden\` using \`docker-compose\`.
> \* Log in to an existing account in the web UI. Verify that it works.
> \* Install the Bitwarden CLI version \`1.22.0\` (the latest version on Arch Linux). Try logging in using the same credentials after running \`bw login\`.
> \* The login attempt fails and an error that says \`Username or password is incorrect. Try again\` is printed.
> 
> \### Expected behaviour
> The login should succeed with the same credentials that work for the web vault login.
> 
> \### Actual behaviour
> The login errors out.
> 
> \### Troubleshooting data
> Relevant log lines related to this issue from the Docker container logs.
> 
> The logs for the CLI login failure
> \`\`\`
> vaultwarden | \[2022-03-20 08:35:22.365\]\[request\]\[INFO\] POST /identity/accounts/prelogin
> vaultwarden | \[2022-03-20 08:35:22.365\]\[response\]\[INFO\] 404 Not Found
> vaultwarden | \[2022-03-20 08:35:22.862\]\[request\]\[INFO\] POST /identity/connect/token
> vaultwarden | \[2022-03-20 08:35:22.902\]\[vaultwarden::api::identity\]\[ERROR\] Username or password is incorrect. Try again. IP: \<A.B.C.D\>. Username: \<email address placeholder\>
> vaultwarden | \[2022-03-20 08:35:22.902\]\[response\]\[INFO\] POST /identity/connect/token (login) =\> 400 Bad Request
> 
> \`\`\`
> The logs for the web vault successful login with the same credentials.
> 
> \`\`\`
> vaultwarden | \[2022-03-20 08:36:57.604\]\[request\]\[INFO\] POST /api/accounts/prelogin
> vaultwarden | \[2022-03-20 08:36:57.606\]\[response\]\[INFO\] POST /api/accounts/prelogin (prelogin) =\> 200 OK
> vaultwarden | \[2022-03-20 08:36:57.795\]\[request\]\[INFO\] POST /identity/connect/token
> vaultwarden | \[2022-03-20 08:36:57.911\]\[vaultwarden::api::identity\]\[INFO\] User\<email placeholder\> logged in successfully. IP: \<A.B.C.D\>
> vaultwarden | \[2022-03-20 08:36:57.912\]\[response\]\[INFO\] POST /identity/connect/token (login) =\> 200 OK
> vaultwarden | \[2022-03-20 08:36:58.136\]\[request\]\[INFO\] POST /identity/connect/token
> vaultwarden | \[2022-03-20 08:36:58.136\]\[request\]\[INFO\] POST /identity/connect/token
> vaultwarden | \[2022-03-20 08:36:58.150\]\[response\]\[INFO\] POST /identity/connect/token (login) =\> 200 OK
> vaultwarden | \[2022-03-20 08:36:58.150\]\[response\]\[INFO\] POST /identity/connect/token (login) =\> 200 OK
> \`\`\`

though I don’t think that has been seen with the browser extension before.

---

<div class="post-metadata">

**Author:** ![buchy](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@buchy](https://vaultwarden.discourse.group/u/buchy)\
**Post date:** [April 14, 2022, 10:42am UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563/13 "2022-04-14T10:42:56Z")

</div>

you mean this **[https://dsm920.duckdns.org:2243/api/accounts/prelogin](https://dsm920.duckdns.org:2243/api/accounts/prelogin)**

i am not very familiar with this, and docker and all this stuff are all new for me ☹  
I probably have a long way to go … if I don’t give up  
I thought it would be quite simple as in the tutorials, but nothing can be easy for me 😐

 ![2022_04_14_12_39_46_DevTools_chrome_extension_ccnckbpmaceehanjmeomladnmlffdjgn_background.html_](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/3b28154b33a74e7f6a1d10e82f7a4532c1fa1b24.jpeg)

---

<div class="post-metadata">

**Author:** ![cksapp](https://avatars.discourse-cdn.com/v4/letter/c/b9e5f3/32.png) [@cksapp](https://vaultwarden.discourse.group/u/cksapp)\
**Post date:** [April 14, 2022, 11:59am UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563/14 "2022-04-14T11:59:18Z")

</div>

The link you provided is a DuckDNS link but with an optional non standard port `2243`, are you making sure you are entering the port in as well when you are putting in the entire DuckDNS URL.

Typically web services are bound to either port `80` http or `443` https and this is what is expected by most browsers and programs when going to some site.  
Other programs, i.e SSH port `22` will have different default standard ports.  
Ports can be changed but the program will have no way of knowing you have changed your port to something different than the default it is expecting unless you specify the correct port.

---

<div class="post-metadata">

**Author:** ![buchy](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@buchy](https://vaultwarden.discourse.group/u/buchy)\
**Post date:** [April 14, 2022, 12:43pm UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563/15 "2022-04-14T12:43:15Z")

</div>

i add the port to in the url, as by the android app where it works.  
example: [https://123.duckdns.org:1234](https://123.duckdns.org:1234)

---

<div class="post-metadata">

**Author:** ![buchy](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@buchy](https://vaultwarden.discourse.group/u/buchy)\
**Post date:** [April 19, 2022, 10:32am UTC](https://vaultwarden.discourse.group/t/bitwarden-vaultwarden-can-t-connect-on-windows-via-browser-plugin/1563/16 "2022-04-19T10:32:36Z")

</div>

Hi 🙂 so i have a solution for this issue i do not why but the Browser plugin of Bitwarden in windows doesnt like other ports as 443 (android app it doesn’t matter), even when the exact port on the server is set! soooo Port 443 is a must! 🙂

Problem solved. 🙂