mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-11 09:13:02 +03:00
Can't log into browser extension - invalid request url path #1194
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dominikheinz on GitHub.
Subject of the issue
Firstly, I can't pinpoint if this issue is related to the official bitwarden browser extension, or if its a problem that is caused because of the vaultwarden backend.
However, since this issue appeared in multiple browsers, and in different versions of the browser extension, I am guessing it might be related to the vaultwarden backend.
Essentially, I can not log into vaultwarden using the bitwarden browser extension anymore - password is obviously correct. Log directly via the web interface works just fine. Of course I have also set my set the server URL in the extension
https://something.something.com/. When trying to log in on the browser extension, I get an error popup: "Invalid request url path".I experienced this behaviour on chromium and on firefox. It used to work on a few days ago, but after reinstalling chromium, and using the same version of the browser extension, I run into this problem?? Again - this used to work just fine/
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
I am using nginx proxy manager, since the pi that is running vaultwarden is only exposed in my local network, so my URL maps to something like 192.168.178.xxx - but that never caused any issues.
Steps to reproduce
I am honestly not sure, install the browser extension and try to connect to your local vaultwarden instance.
Expected behaviour
Sign in should work normally.
Actual behaviour
@BlackDex commented on GitHub:
I see that the domain seems to be configured incorrectly:
Please double check that you have configured this as it should be.