# Unable to log in with browser extension **URL:** \ **Category:** Uncategorized\ **Created:** [January 13, 2023, 2:21pm UTC](https://vaultwarden.discourse.group/t/unable-to-log-in-with-browser-extension/2223 "2023-01-13T14:21:17Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![briceparmentier](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/briceparmentier/32/142_2.png) [@briceparmentier](https://vaultwarden.discourse.group/u/briceparmentier)\ **Post date:** [January 13, 2023, 2:21pm UTC](https://vaultwarden.discourse.group/t/unable-to-log-in-with-browser-extension/2223/1 "2023-01-13T14:21:17Z")
Hi there, Since 2 days now I’m not able to log in anymore using the Chrome browser extension. Everything is fine using the mobile app or the web page directly, all my data is fine and still present, using the same credentials. But I’m being said that username or password are incorrect using the browser extension (whatever the browser, tried Chrome, Brave, Firefox) at version 2023.1.0. Here is the log on the docker image of my self-hosted vaultwarden: ```auto [2023-01-13 14:07:23.530][request][INFO] POST /identity/accounts/prelogin [2023-01-13 14:07:23.530][response][INFO] 404 Not Found [2023-01-13 14:07:23.546][request][INFO] POST /identity/connect/token [2023-01-13 14:07:23.842][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: aaa.bbb.ccc.ddd. Username: XXXXXXX. [2023-01-13 14:07:23.842][response][INFO] POST /identity/connect/token (login) => 400 Bad Request ``` It seems it was still working on Firefox with an old version of the browser extension before it gets upgraded to latest. Is there any new feature or interface change of the original product that has not been ported yet to vaultwarden? I’m running self-hosted vaultwarden in a docker and I have a reverse proxy running on another machine. Is there something to change on this side maybe ? Thanks! Brice ---
**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:** [January 13, 2023, 2:33pm UTC](https://vaultwarden.discourse.group/t/unable-to-log-in-with-browser-extension/2223/2 "2023-01-13T14:33:30Z")
Make sure you’ve updated vaultwarden to version 1.27.0 > > > \# 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! ---
**Author:** ![briceparmentier](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/briceparmentier/32/142_2.png) [@briceparmentier](https://vaultwarden.discourse.group/u/briceparmentier)\ **Post date:** [January 13, 2023, 2:49pm UTC](https://vaultwarden.discourse.group/t/unable-to-log-in-with-browser-extension/2223/3 "2023-01-13T14:49:14Z")
Damn it! I found this topic while searching the internet for a solution of my problem. I then ran what I thougt would be an update of the docker image, and I saw it was then running Bitwarden 2.25.0, so I guessed it was up-to-date. My apologies, I will have a better check at this an really update the docker image. Sorry for the unecessary topic… Brice ---
**Author:** ![briceparmentier](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/briceparmentier/32/142_2.png) [@briceparmentier](https://vaultwarden.discourse.group/u/briceparmentier)\ **Post date:** [January 13, 2023, 2:54pm UTC](https://vaultwarden.discourse.group/t/unable-to-log-in-with-browser-extension/2223/4 "2023-01-13T14:54:41Z")
Works fine with a real upgrade of the image 🙃