Is there something to change on this side maybe ? I’m running self-hosted vaultwarden in a docker and I have a reverse proxy running on another machine. Is there any new feature or interface change of the original product that has not been ported yet to vaultwarden? It seems it was still working on Firefox with an old version of the browser extension before it gets upgraded to latest. POST /identity/connect/token (login) => 400 Bad Request Here is the log on the docker image of my self-hosted vaultwarden: POST /identity/accounts/prelogin Since 2 days now I’m not able to log in anymore using the Chrome browser extension.Įverything is fine using the mobile app or the web page directly, all my data is fine and still present, using the same credentials.īut 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |