mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
Browser extensions stopped working #1226
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 @dmirtillo on GitHub (Mar 1, 2022).
Subject of the issue
The browser extensions for Firefox and Google chrome suddendly stopped working. I've tried:
Deployment environment
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED, ADMIN_TOKEN, YUBICO_CLIENT_ID, YUBICO_SECRET_KEY, YUBICO_SERVER, SMTP_HOST, SMTP_FROM, SMTP_FROM_NAME, SMTP_USERNAME, SMTP_PASSWORD, SMTP_TIMEOUT
Install method: Docker
Clients used: browser extension (firefox, chrome), web vault, Mac OS App
Reverse proxy and version: nginx, swag from linuxserver.io => https://github.com/linuxserver/reverse-proxy-confs/blob/master/vaultwarden.subfolder.conf.sample
MySQL/MariaDB or PostgreSQL version: MariaDB
Other relevant details:
Steps to reproduce
Logging in through the browser extensions, after configuring the on-premise Server URL in the extension settings
Expected behaviour
I'm supposed to log in. This works as expected through the Mac OS app and the web-vault
Actual behaviour
The browser extension says there is an unexpected error.
The vaultwarden docker logs show the info below
Troubleshooting data
vaultwarden | POST /bw/accounts/prelogin application/json; charset=utf-8:
vaultwarden | => Error: No matching routes for POST /bw/accounts/prelogin application/json; charset=utf-8.
vaultwarden | => Warning: Responding with 404 Not Found catcher.
vaultwarden | => Response succeeded.
vaultwarden | POST /bw/connect/token application/x-www-form-urlencoded; charset=utf-8:
vaultwarden | => Error: No matching routes for POST /bw/connect/token application/x-www-form-urlencoded; charset=utf-8.
vaultwarden | => Warning: Responding with 404 Not Found catcher.
vaultwarden | => Response succeeded.
@BlackDex commented on GitHub (Mar 1, 2022):
The nginx config you provided shows
/vaultwarden/and the error shows/bw/i guess there is a configuration issue here 😉Besides that, it works for me on a fresh profile of Firefox and newly installed Bitwarden Extension.
@dmirtillo commented on GitHub (Mar 1, 2022):
Sorry, i shared the template and not the actual configuration, which has the correct domain_path set
Here's the reverse-proxy configuration:
I've tried also uninstalling the extension and reinstalling it on both browser, but still no joy.
Do you know if there's anything else I might want to try in order to connect the extensions back to the server?
They were working fine prior to the extension update that has been pushed.
Are those two paths new?
I'm talking about
/bw/accounts/preloginand/bw/connect/token@BlackDex commented on GitHub (Mar 1, 2022):
Those are there already, and working.
So nothing has changed there.
Also, you use regex/match for location, that can have strange effects.
I suggest to take a look at my example for nginx with sub-path here: https://github.com/dani-garcia/vaultwarden/wiki/Proxy-examples (Though i might have some optimizations for that now i see it, but that should at least work).
@dmirtillo commented on GitHub (Mar 1, 2022):
Thanks for the tips and patience! I managed to solve the issue i was having.
For anyone else stumbling upon similar issue, I solved it by only inputting the
Server URLvariable inside theSELF-HOSTED ENVIRONMENTsection of the browser extension configuration. I cleared out any URL in theCUSTOM ENVIRONMENTsection.Seems like the other values were working in the previous browser extension version, and the
CUSTOM ENVIRONMENTnow causes some kind of issue.@BlackDex you can close this issue if you don't feel the need to investigate further
@BlackDex commented on GitHub (Mar 1, 2022):
Ah, those extra options are indeed not needed at all 😄