mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-03-01 11:19:52 +03:00
Web Vault login failure: this.subtle is null #679
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 @fredrikekre on GitHub (Apr 9, 2020).
Subject of the issue
Today I could not log in to the web vault, when posting the credentials I get the following pop-up and log in fails:
I can still interact with the server with the bitwarden CLI and using the Firefox plugin. I have not tried restarting yet so in case you want some more debuginfo the problem is still reproducing here.
Your environment
bitwardenrs/server@sha256:043e294847130f08ae9eb355caf00855b013b851c66628c8fba25a5c21819942)3.27.2 2019-02-25 16:06:06 bd49a8271d650fa89e446b42e513b595a717b9212c91dd384aab871fc1d0alt1Steps to reproduce
Not sure how to reproduce, the server has been up for ~1 week now without any problems at all, this just started showing up today.
Relevant logs
Server log from sending credentials:
@fredrikekre commented on GitHub (Apr 9, 2020):
Ah, looks like https://bitwardenrs.discourse.group/t/error-with-latest-firefox-upgrade-ver75/66. That is annoying for just running a local server...
Sorry for the noise, but at least this issue may help others find the solution.
@Link009 commented on GitHub (May 6, 2020):
Hi
I have the same issue. bitwarden_rs hosted in Docker on a Synology NAS. How do I solve this other than "enable HTTPS" ? This seems so easy to say but I am not fully aware of what I have to do..
Thanks
@ardunn commented on GitHub (May 7, 2020):
I'm having this issue as well, seemingly works on no mainstream browser. Worked until recently. I'm running a local server...
@dani-garcia commented on GitHub (May 7, 2020):
All the major browsers have blocked the use of their encryption APIs on anything that they consider insecure, Chrome has been doing it for years now and Firefox has started doing it in the latest version.
That means effectively that the only way to use bitwarden_rs now is using HTTPS, that said you can use self signed certificates if you don't have a domain name, but you'll get a browser warning each time.
@fredrikekre commented on GitHub (May 7, 2020):
At least in Firefox you can add it permanent, so it will just warn on first use.
@Link009 commented on GitHub (May 7, 2020):
Is there any chance that the issue can be solved BW side ? I read a few tutorials and I can't say, for me, are the easier ways to solve the problem.
@dani-garcia commented on GitHub (May 7, 2020):
Well we could generate a self signed certificate, but that's really easy to do anyway, so I don't see the point.
To generate them you can use the openssl cli like this:
You could also use something like mkcert or even https://www.selfsignedcertificate.com/
Then to enable it change the config like the wiki mentions: https://github.com/dani-garcia/bitwarden_rs/wiki/Enabling-HTTPS
@ardunn commented on GitHub (May 8, 2020):
That's not working for me, even after following the bitwarden_rs Enabling HTTPS guide I get the following log error:
This is after setting the generated files to have read permissions for everyone...
@ardunn commented on GitHub (May 10, 2020):
@dani-garcia do I need to change something else? My docker run command is:
@jjlin commented on GitHub (May 10, 2020):
@ardunn The
ROCKET_TLScerts/key paths need to be from the perspective of the container, soROCKET_TLS='{certs="/ssl/certs.pem",key="/ssl/key.pem"}'.@ardunn commented on GitHub (May 10, 2020):
Thanks! That seemed to get the service up working, but when I try to access it via browser, I get no connection/connection refused. It was working previously with same config (minus SSL), any ideas on how to troubleshoot?
@Link009 commented on GitHub (May 10, 2020):
I (hope) successfully generated my cert.pem and key.pem files (stored in volume1). When I tried to add the variable ROCKET_TLS to docker as environment variable, I could not set up and run bitwarden docker image.
Using the command
docker run -d --name bitwarden -e ROCKET_TLS='{certs="/volume1/cert.pem",key="/volume1/key.pem"}' -v /ssl/keys/:/ssl/ -v /bw-data/:/data/ -p 443:80 bitwardenrs/server:latestgives me the following error:
docker: Error response from daemon: Conflict. The container name "/bitwarden" is already in use by container "e24c1c364fffbb49001a726d3f705d3c6bc2ea1c6302822ae662218467ca4669". You have to remove (or rename) that container to be able to reuse that name.@jjlin commented on GitHub (May 11, 2020):
Please move these questions to https://bitwardenrs.discourse.group/ for further assistance; they aren't relevant to the original topic, and aren't issues in the software.
@Link009 commented on GitHub (May 30, 2020):
I made a tutorial on this for people who don't know how to handle the error: https://lucians.dev/solve-bitwardenrs-this-subtle-is-null-error
@Timshel commented on GitHub (Jan 29, 2024):
For those just wanting to bypass it when debugging locally:
There is a setting in Firefox to add domains (ref) :
dom.securecontext.allowlist: it probably does not exists, create it as a string and add your host.This way you can bind your external ip to test mobile applications and still test in FF.