None of my desktop/laptops can login with master-password on bitwarden-plugins in CHrome/Firefox.If I revert my server-settings to use https:/ / AND edit my /etc/hosts file again to use the external IP for it once more, it STILL works.Įven more interesting is that it suddenly works (again) for all OTHER devices that had been having issues logging in via their browser-plugins. :5151 to prevent there being any reverse-proxy handling in between at all.īut, here’s where it gets weird.
This leads to the same behaviour: Web works but Plugins and app do not.īut, going one step further, I changed the login-url from https:/ / to HTTP:/ com name directly to the INTERNAL IP so that there’s (less) DSM stuff in the way. My first steps were to edit /etc/hosts to point the warden. This whole setup has run very well for a long while now and only just started producing issues for me yesterday. In DSM I have LetsEncrypt certificates and ReverseProxy exposing the whole thing on warden. I have docker running on Synology DSM with the latest Vaultwarden container. I just registered, and Discourse is telling me i can only include two URL’s as a new user… so my URL’s are somewhat weirdly formatted for that reason. (i’ll explain why it is interesting in a bit) (login) POST /identity/connect/token => 400 Bad Request The docker-container log lists: Username or password is incorrect. The plugin reports username/pass is wrong. The issue is that web-logins work fine, but App/Plugin logins do not. Have vaultwarden/server:latest running after reading the NOTE on github/here about running the latest version. (and… it seems I have it working again, too… in a superweird way) I just registered on this discourse because i’m having the exact same problem all of a sudden.
0 kommentar(er)
