Originally created by @pageb018 on GitHub (Aug 29, 2018).
Doing a test backup and restore. I copy the entire bw-data folder onto a new host. Run a docker-compose up on new host, I get the login page but when trying to authenticate I receive a "Cannot read property 'importKey' of null" error.
Not sure how to proceed, the logs do not seem to show an error.
Originally created by @pageb018 on GitHub (Aug 29, 2018).
Doing a test backup and restore. I copy the entire bw-data folder onto a new host. Run a docker-compose up on new host, I get the login page but when trying to authenticate I receive a "Cannot read property 'importKey' of null" error.
Not sure how to proceed, the logs do not seem to show an error.
bitwarden | POST /api/accounts/prelogin application/json; charset=utf-8:
bitwarden | => Matched: POST /api/accounts/prelogin
bitwarden | => Outcome: Success
bitwarden | => Response succeeded.
bitwarden | POST /api/accounts/prelogin application/json; charset=utf-8:
bitwarden | => Matched: POST /api/accounts/prelogin
bitwarden | => Outcome: Success
bitwarden | => Response succeeded.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @pageb018 on GitHub (Aug 29, 2018).
Doing a test backup and restore. I copy the entire bw-data folder onto a new host. Run a docker-compose up on new host, I get the login page but when trying to authenticate I receive a "Cannot read property 'importKey' of null" error.
Not sure how to proceed, the logs do not seem to show an error.
bitwarden | POST /api/accounts/prelogin application/json; charset=utf-8:
bitwarden | => Matched: POST /api/accounts/prelogin
bitwarden | => Outcome: Success
bitwarden | => Response succeeded.
bitwarden | POST /api/accounts/prelogin application/json; charset=utf-8:
bitwarden | => Matched: POST /api/accounts/prelogin
bitwarden | => Outcome: Success
bitwarden | => Response succeeded.
@mprasil commented on GitHub (Aug 29, 2018):
Please see #153, this seems to be issue with the chrome browser when you're not using https.