# Chrome Extension Not Accepting Password **URL:** \ **Category:** Third Party Help\ **Created:** [February 4, 2023, 9:35pm UTC](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333 "2023-02-04T21:35:15Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![davo1979](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/davo1979/32/971_2.png) [@davo1979](https://vaultwarden.discourse.group/u/davo1979)\ **Post date:** [February 4, 2023, 9:35pm UTC](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333/1 "2023-02-04T21:35:15Z")
Hi, recently I wiped my windows pc and reinstalled chrome. I added Bitwarden chrome extension and entered my self hosted domain name which was accepted but when entering my username and password I get an error message however when I enter these details into the address bar using my domain name I get in no problem. I host Bitwarden on a raspberry Pi inside Portainer. I have tried to update to the :latest but the problem still persists. Thanks, Craig. ---
**Author:** ![cksapp](https://avatars.discourse-cdn.com/v4/letter/c/b9e5f3/32.png) [@cksapp](https://vaultwarden.discourse.group/u/cksapp)\ **Post date:** [February 5, 2023, 2:08pm UTC](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333/2 "2023-02-05T14:08:31Z")
Are you updating to latest with the BitwardenRS image, or the newer Vaultwarden one? ---
**Author:** ![CyberWarden](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/cyberwarden/32/980_2.png) [@CyberWarden](https://vaultwarden.discourse.group/u/CyberWarden)\ **Post date:** [February 11, 2023, 5:55pm UTC](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333/3 "2023-02-11T17:55:48Z")
Any feedback from you? ---
**Author:** ![lsiracer78](https://avatars.discourse-cdn.com/v4/letter/l/977dab/32.png) [@lsiracer78](https://vaultwarden.discourse.group/u/lsiracer78)\ **Post date:** [February 11, 2023, 8:46pm UTC](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333/4 "2023-02-11T20:46:54Z")
Hi, I am also having the same exact issue. I have been using Vaultwarden for a long time and had no issues that I noticed since last night. I am currently running the latest vaultwarden/server:latest. I checked my logs and showing version 1.24.0. A little background how the issue was found last night In my computer, I have multiple chrome profiles for different google acocunts. For simplicity, we will call this profiles as chrome\_profile\_1 = CP1 and chrome\_profile\_2 = CP2. CP1 has been logged in in Bitwarden Chrome Extension with the server URL from my synology. Everytime I need it, I just need to enter the master password from the Lock stage and it works. Last night, I was using CP2 and realized CP2 was never setup with the Bitwarden Extension. Therefore, I decided to setup and entered the same server URL from my synology as CP1 and enter my username and password. When I clicked login, it showed that the username and password is incorrect. I went to a browser and entered the same URL and credentials. From the browser stand-point, everything is working as expected. So then I switched to CP1 and entered my master password and logged in. I was able to login without any issues. Therefore, I decided to completely log out of CP1 Bitwarden Extension and re-eneter my username and password. At this point, I am having the same issue as CP2. I am now stuck and can’t login in any bitwarden chrome extension in both profiles and need help. I have 2-step authentication in my vaultwarden/bitwarden enabled. I am not sure if this issue on the chrome extension is due to not being able to verify the 2-step authentication since after entering my username and password, it would just immediately result in an error instead of displaying the OTP request. I hope the information above can help guide me through and resolve the issue. Thanks, Larry ---
**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:** [February 11, 2023, 8:56pm UTC](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333/5 "2023-02-11T20:56:31Z")
@lsiracer78 there have been newer version of vaultwarden (the [latest release is currently 1.27.0](https://github.com/dani-garcia/vaultwarden/releases/tag/1.27.0)). Regarding your login problems see this pinned issue: > > > \# New versions > > If you are currently unable to login with any client after you… either have the clients updated or Vaultwarden it self please check you are running the latest version of Vaultwarden! > > Bitwarden has released new client versions which are not compatible with Vaultwarden version bellow 1.27.0. > Since version 1.27.0 Vaultwarden supports these new clients and has many bugs fixed and features added. > > See the release notes here \[Release v1.27.0 (2022-12-24)\](https://github.com/dani-garcia/vaultwarden/discussions/3037). > > If you are running the \`testing\` tagged releases of Vaultwarden, the version should be \`1.26.0-10dadfca\`, which is exactly the same as the released \`1.27.0\`. > > Please \*\*do not report\*\* any client connection bugs or issues before you have fully updated your environment to the latest version. > To check which version you are running right now you can best login into the \*\*Admin Interface\*\*. > To access the \*\*Admin Interface\*\* you need to go to \`https://your.domain.tld/admin\` and after login click on the \`Diagnostics\` tab. > This will show you the current version you have running. > > If you can't access the admin interface you can also check the web-vault version on the web client. > It should look something like this. > !\[image\](https://user-images.githubusercontent.com/610450/210139662-1d44e1d5-433b-479c-bf51-3689cd8ca22e.png) > > An other way to check the version of Vaultwarden is via the cli, either via docker or container-less install. > > \`\`\`bash > \# If you have installed Vaultwarden via a package manager like pacman, deb or yum. > vaultwarden --version > > \# If you have it running via docker or podman > \# Replace vaultwarden-container-name with the actual name of your vaultwarden container, check \`docker ps\` > docker exec vaultwarden-container-name /vaultwarden --version > \`\`\` > > \# Other common issues > > There are some other common issues where people are reporting 2FA/MFA not working. > Most of the time this is either incorrect date/time, this can be checked in the \*\*Admin Interface\*\* at the \*\*Diagnostics\*\* page. > Or, the reverse proxy has some added security settings enabled which replace or adds the already present correct security headers, or prevent \`PUT\` or \`DELETE\` requests. > > This causes issues like unable to login, update ciphers, upload attachments and other strange issues. > Please also check the logs of your reverse proxy before posting any issue! From the version it sounds like you are still using the `bitwardenrs/server:latest` image. ---
**Author:** ![lsiracer78](https://avatars.discourse-cdn.com/v4/letter/l/977dab/32.png) [@lsiracer78](https://vaultwarden.discourse.group/u/lsiracer78)\ **Post date:** [February 11, 2023, 9:10pm UTC](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333/6 "2023-02-11T21:10:25Z")
Hi @stefan0xC, Thank you for your quick response. I was running bitwardenrs/server:latest but switch to vaultwarden/server:latest long time ago. However, I kept bitwardenrs in my docker but is no longer running. ![image](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/fba7ee908a5b9346bbb11519b30fda61ec63889c.png) Do you know if this is an issue? Larry ---
**Author:** ![lsiracer78](https://avatars.discourse-cdn.com/v4/letter/l/977dab/32.png) [@lsiracer78](https://vaultwarden.discourse.group/u/lsiracer78)\ **Post date:** [February 11, 2023, 11:00pm UTC](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333/7 "2023-02-11T23:00:10Z")
Hi @stefan0xC, Thanks again for your guidance on this. I pulled the new vaultwarden/server:latest image in my Synology docker, renamed the original container as my backup then duplicated that container to use the new image and it is working now. Again, appreciate your help and guidance on this. Thanks, Larry ---
**Author:** ![gerardv514](https://avatars.discourse-cdn.com/v4/letter/g/439d5e/32.png) [@gerardv514](https://vaultwarden.discourse.group/u/gerardv514)\ **Post date:** [February 12, 2023, 8:27pm UTC](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333/8 "2023-02-12T20:27:40Z")
> [@lsiracer78](#): > > I pulled the new vaultwarden/server:latest image in my Synology docker, renamed the original container as my backup then duplicated that container to use the new image and it is working now How did you get the duplicated container to use a new image? When I duplicate a container it uses the existing image. ---
**Author:** ![lsiracer78](https://avatars.discourse-cdn.com/v4/letter/l/977dab/32.png) [@lsiracer78](https://vaultwarden.discourse.group/u/lsiracer78)\ **Post date:** [February 12, 2023, 11:13pm UTC](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333/9 "2023-02-12T23:13:13Z")
Hi @gerardv514, From your synology docker, go to the Registry and search vaultwarden/server:latest and download it. This will download a new image. Then go Container and stop the current vaultwarden-server or whatever you named it (ie: vaultwarden-server1). Once it is stop right click on that container and edit. A window will popup and change the container name to something with -backup (ie: vaultwarden-server1-backup). Once you have this click apply and you will be back to your containers. Then right click it again on the current vaultwarden backup one you just renamed, select settings and then duplicate settings. A window will popup. Make sure to set this container name back to the original name you had before. This will use the new image that you just downloaded at the very beginning from the Registry. Something to note: although this copies everything from the original container, the port numbers are set to Auto. If you set your vaultwarden with a specific port number and using that port number in reverse proxy, you will need to update the new container to the original port number. To do this, go to the backup vaultwarden, and change the port there to something that has not been used. Then go to the new vaultwarden and set the port number to the original. This should work. The reason I do it this way is to make sure I have a backup of the original vaultwarden in case something goes wrong with the new one. If there are no issues with the new vaultwarden, then you can delete the old container if you want. Good luck. Larry ---
**Author:** ![gerardv514](https://avatars.discourse-cdn.com/v4/letter/g/439d5e/32.png) [@gerardv514](https://vaultwarden.discourse.group/u/gerardv514)\ **Post date:** [February 13, 2023, 12:06am UTC](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333/10 "2023-02-13T00:06:01Z")
Ah I see I already know how to get an updated image to the container. I must have read and looked at the screenshot too quick. I was under the impression you went from the bitwarden\_rsimage to Vaultwarden image by simply applying the new/updated Vaultwarden image to the previous bitwarden\_rscontainer. The only way I know of switching images is to have to build the container from scratch; I thought you knew of another way. I kind of wish the server version tag didn’t say latest but gave the actual version number. Just makes it easier to see what image version the container is and helps with rolling back or testing different image versions. ---
**Author:** ![lsiracer78](https://avatars.discourse-cdn.com/v4/letter/l/977dab/32.png) [@lsiracer78](https://vaultwarden.discourse.group/u/lsiracer78)\ **Post date:** [February 13, 2023, 12:38am UTC](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333/11 "2023-02-13T00:38:04Z")
@gerardv514 , Yeah, I had vaultwarden already… just needed to udpate it to the latest version. However, when I switched from bitwardenrs to vaultwarden, it was not too bad but yeah you will have to kinda build it from scratch. You can check some other users [here](https://vaultwarden.discourse.group/t/migrating-from-bitwarden-rs-to-vaultwarden-on-synology-nas/1301) who migrated from bitwardenrs to vaultwarden. Perhaps there maybe a simpler way. Larry ---
**Author:** ![davo1979](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/davo1979/32/971_2.png) [@davo1979](https://vaultwarden.discourse.group/u/davo1979)\ **Post date:** [July 20, 2023, 3:00pm UTC](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333/12 "2023-07-20T15:00:20Z")
Hi thanks for all the great replies. I have tried to pull the latest Valtwarden into portainer and the container starts but I get error message. Can anyone help with setting this up every step of the way in portainer? I would really appreciate it. I can’t see a guide on youtube and unfortunatley rely quite a lot on guides to get stuff installed. I have attatched my current diagnostics as to what I’m currently running using Bitwarden. ![Bitwarden Version](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/2X/b/b1ffc448c245c9f0926ba34d01b7f63b72881c9f.png) ---
**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:** [July 20, 2023, 3:16pm UTC](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333/13 "2023-07-20T15:16:49Z")
@davo1979 as explained [in the other thread](https://vaultwarden.discourse.group/t/bitwarden-running-on-portainer-browser-extensions-not-working/2803/2) you are using an outdated version. please update to the latest version > > > Hello all, > > The past few weeks there have been a lot of changes on both vaultw…arden server side and the official bitwarden clients. > > Because of all these changes done, most issues (not all) are probably because of not having the vaultwarden server updated to the latest version available which has these fixes in place. > > The current latest version is: \[!\[GitHub Release\](https://img.shields.io/github/release/dani-garcia/vaultwarden.svg)\](https://github.com/dani-garcia/vaultwarden/releases/latest) > Commits since latest release: !\[GitHub commits since tagged version\](https://img.shields.io/github/commits-since/dani-garcia/vaultwarden/latest/main) > > Please make sure you have either the \`latest\` version running or \`testing\` before reporting an issue. > Also, check the commits done since the \`latest\` release which are in \`testing\`, it could be that a bug you run into is already fixed, but they are not yet released as a new version !\[GitHub commits since tagged version\](https://img.shields.io/github/commits-since/dani-garcia/vaultwarden/latest/main). > > Also note that there have been some changes in the docker hub tags. Below you can find a bit more information about these docker hub tags. > > If after updating to the latest version and checking the commits done since the latest release of vaultwarden and you still encounter these same issue, please go ahead and post a new topic on the forum https://vaultwarden.discourse.group/ or here at the issues page. > > Thanks for all your support. > > > \# New docker multi database support for Debian and Alpine > \### Only one image: \`vaultwarden/server\` > It contains support for SQLite, MySQL and PostgreSQL all in one! Supports AMD64, ARMv6, ARMv7 and ARMv8 (Aarch64), and all architectures support all database backends!. > > \*\*Note\*\*: The old \`bitwarden\_rs\` are no longer available! > > \### Which tag to use: > \- \`vaultwarden/server:latest\`: Tracks the latest released version (i.e., tagged with a version number). Recommended for most users, and generally the most stable. > \- \`vaultwarden/server:testing\`: Tracks the latest commits to the source repository. Recommended for users who want early access to the newest features or enhancements. Generally pretty stable, but occasional issues are unavoidable. > \- \`vaultwarden/server:x.y.z\`: Represents a specific released version. Prefer to use latest to keep up-to-date. > > \#### Note about ARMv6 > > \- Docker seems to have some issues with architecture detection on ARMv6, so if you have trouble in that case, use these tags instead: \`vaultwarden/server:arm32v6\`, \`vaultwarden/server:testing-arm32v6\`, \`vaultwarden/server:x.y.z-arm32v6\` > > \#### Alpine base > > \- \`vaultwarden/server:alpine\`, \`vaultwarden/server:testing-alpine\`, \`vaultwarden/server:x.y.z-alpine\`: Functionally the same as the above images, but based on Alpine instead of Debian, which results in a smaller image. ---
**Author:** ![davo1979](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/davo1979/32/971_2.png) [@davo1979](https://vaultwarden.discourse.group/u/davo1979)\ **Post date:** [July 20, 2023, 7:14pm UTC](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333/14 "2023-07-20T19:14:13Z")
I thought Bitwarden was no more? This is the problem, I’m not sure how to either update the current Bitwarden to Vaultwarden or how to add Vaultwarden to Portainer, any help?