mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
Cannot read property 'importKey' of null #490
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 @diablozzq on GitHub (Nov 16, 2019).
I'm trying to install bitwardenrs and am getting a "Cannot read property 'importKey' of null" on the Javascript console in Chrome. This happens when I try to login or create a user account. I can log into the admin interface.
I've tried this on my Raspberry Pi on Raspbian Buster using the docker with bitwardenrs/server:raspberry, Virtual Box with Ubuntu 18.04 with docker and bitwardenrs/server:latest and also bitwardenrs/server:1.11.0.
Is this a bug? Did I not follow the instructions? I tried 4+ times now and can't seem to figure this out.
@diablozzq commented on GitHub (Nov 16, 2019):
To add some more info, here is the command I was using to install it.
On the Raspberry Pi 4 using the latest Rasbian release:
docker pull bitwardenrs/server:raspberry
docker run -d --name bitwarden -e ADMIN_TOKEN=test -e LOG_FILE=/data/bitwarden.log -e SIGNUPS_ALLOWED=true -v /bw-data/:/data/ -p 80:80 bitwardenrs/server:raspberry
On Ubuntu 18.04:
docker pull bitwardenrs/server:latest
docker run -d --name bitwarden -e ADMIN_TOKEN=test -e LOG_FILE=/data/bitwarden.log -e SIGNUPS_ALLOWED=true -v /bw-data/:/data/ -p 80:80 bitwardenrs/server:latest
@diablozzq commented on GitHub (Nov 16, 2019):
Once installed, I used Chrome to browse to the default page. From there, that's when I was getting that error. I was unable to ever create an account.
I have not tried another bitwarden client
@diablozzq commented on GitHub (Nov 16, 2019):
Just tried the desktop client and I was able to login. Must be a javascript client problem?
@dani-garcia commented on GitHub (Nov 16, 2019):
Chrome disallows the use of some crypto APIs that the web page uses when the content is served over HTTP and not HTTPS, the possible solutions are to either enable HTTPS or to use Firefox.
Last time this was mentioned, it's only the account creation that uses these APIs, so as long as you register in another browser Chrome should work.
@diablozzq commented on GitHub (Nov 19, 2019):
Thanks. This was correct. HTTPS fixed it.