# Chrome Extension Not Accepting Password

**URL:** <https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333>\
**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:** 1\
**Showing post:** 13

<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:** [July 20, 2023, 3:16pm UTC](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333/13 "2023-07-20T15:16:49Z")

</div>

@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

> <https://github.com/dani-garcia/vaultwarden/issues/1180>
>
> 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.

---

_[View the full topic](https://vaultwarden.discourse.group/t/chrome-extension-not-accepting-password/2333)._
