[GH-ISSUE #1165] "Username or password is incorrect." after upgrade from 1.1.0

kerem commented

2026-03-03 02:03:34 +03:00

Owner

Originally created by @themightychris on GitHub (Sep 30, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1165

I have a ~2 year old instance running I believe 1.1.0 from mprasil/bitwarden:latest

I tried dropping bitwardenrs/server:latest into my docker-compose.yml and doing docker-compose pull && docker-compose up -d and that seems to work, but the system ends up in a state where all existing logins result in "Username or password is incorrect."

Migrations appear to run during startup:

Attaching to bitwarden_web_1
web_1  | /--------------------------------------------------------------------\
web_1  | |                       Starting Bitwarden_RS                        |
web_1  | |                           Version 1.16.3                           |
web_1  | |--------------------------------------------------------------------|
web_1  | | This is an *unofficial* Bitwarden implementation, DO NOT use the   |
web_1  | | official channels to report bugs/features, regardless of client.   |
web_1  | | Send usage/configuration questions or feature requests to:         |
web_1  | |   https://bitwardenrs.discourse.group/                             |
web_1  | | Report suspected bugs/issues in the software itself at:            |
web_1  | |   https://github.com/dani-garcia/bitwarden_rs/issues/new           |
web_1  | \--------------------------------------------------------------------/
web_1  | 
web_1  | Running migration 20180919144557
web_1  | Running migration 20181127152651
web_1  | Running migration 20190526216651
web_1  | Running migration 20191010083032
web_1  | Running migration 20191117011009
web_1  | Running migration 20200313205045
web_1  | Running migration 20200409235005
web_1  | Running migration 20200701214531
web_1  | [2020-09-30 15:42:42.581][start][INFO] Rocket has launched from http://0.0.0.0:80

Reverting to the old image and restoring the /data directory gets things working again, but I'd like to figure out how to upgrade this instance and the database along with it. Are there any special steps I might be missing for this big version jump outside the automatic migrations?

Originally created by @themightychris on GitHub (Sep 30, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1165 I have a ~2 year old instance running I believe 1.1.0 from `mprasil/bitwarden:latest` I tried dropping `bitwardenrs/server:latest` into my `docker-compose.yml` and doing `docker-compose pull && docker-compose up -d` and that seems to work, but the system ends up in a state where all existing logins result in "Username or password is incorrect." Migrations appear to run during startup: ``` Attaching to bitwarden_web_1 web_1 | /--------------------------------------------------------------------\ web_1 | | Starting Bitwarden_RS | web_1 | | Version 1.16.3 | web_1 | |--------------------------------------------------------------------| web_1 | | This is an *unofficial* Bitwarden implementation, DO NOT use the | web_1 | | official channels to report bugs/features, regardless of client. | web_1 | | Send usage/configuration questions or feature requests to: | web_1 | | https://bitwardenrs.discourse.group/ | web_1 | | Report suspected bugs/issues in the software itself at: | web_1 | | https://github.com/dani-garcia/bitwarden_rs/issues/new | web_1 | \--------------------------------------------------------------------/ web_1 | web_1 | Running migration 20180919144557 web_1 | Running migration 20181127152651 web_1 | Running migration 20190526216651 web_1 | Running migration 20191010083032 web_1 | Running migration 20191117011009 web_1 | Running migration 20200313205045 web_1 | Running migration 20200409235005 web_1 | Running migration 20200701214531 web_1 | [2020-09-30 15:42:42.581][start][INFO] Rocket has launched from http://0.0.0.0:80 ``` Reverting to the old image and restoring the `/data` directory gets things working again, but I'd like to figure out how to upgrade this instance and the database along with it. Are there any special steps I might be missing for this big version jump outside the automatic migrations?

kerem

2026-03-03 02:03:34 +03:00

closed this issue
added the
question

better for forum
labels

kerem commented

2026-03-03 02:03:35 +03:00

Author

Owner

@BlackDex commented on GitHub (Sep 30, 2020):

What is the error you get? Either browser or bitwarden log, or both when you try to login?

@BlackDex commented on GitHub (Sep 30, 2020): What is the error you get? Either browser or bitwarden log, or both when you try to login?

kerem commented

2026-03-03 02:03:35 +03:00

Author

Owner

@themightychris commented on GitHub (Sep 30, 2020):

@BlackDex the quote in the issue title is pasted verbatim from the container log, and I believe is the same wording I saw in the browser. If it didn't match exactly it was a clean "username/password wrong" error. Here's the container log from up on new version to failed login:

web_1  | /--------------------------------------------------------------------\
web_1  | |                       Starting Bitwarden_RS                        |
web_1  | |                           Version 1.16.3                           |
web_1  | |--------------------------------------------------------------------|
web_1  | | This is an *unofficial* Bitwarden implementation, DO NOT use the   |
web_1  | | official channels to report bugs/features, regardless of client.   |
web_1  | | Send usage/configuration questions or feature requests to:         |
web_1  | |   https://bitwardenrs.discourse.group/                             |
web_1  | | Report suspected bugs/issues in the software itself at:            |
web_1  | |   https://github.com/dani-garcia/bitwarden_rs/issues/new           |
web_1  | \--------------------------------------------------------------------/
web_1  | 
web_1  | Running migration 20180919144557
web_1  | Running migration 20181127152651
web_1  | Running migration 20190526216651
web_1  | Running migration 20191010083032
web_1  | Running migration 20191117011009
web_1  | Running migration 20200313205045
web_1  | Running migration 20200409235005
web_1  | Running migration 20200701214531
web_1  | [2020-09-30 15:42:42.581][start][INFO] Rocket has launched from http://0.0.0.0:80
web_1  | [2020-09-30 15:42:56.680][request][INFO] GET /api/accounts/revision-date
web_1  | [2020-09-30 15:42:56.680][auth][ERROR] Unauthorized Error: Invalid claim
web_1  | [2020-09-30 15:42:56.680][response][INFO] GET /api/accounts/revision-date (revision_date) => 401 Unauthorized
web_1  | [2020-09-30 15:43:04.714][request][INFO] POST /api/accounts/prelogin
web_1  | [2020-09-30 15:43:04.714][response][INFO] POST /api/accounts/prelogin (prelogin) => 200 OK
web_1  | [2020-09-30 15:43:04.783][request][INFO] POST /identity/connect/token
web_1  | [2020-09-30 15:43:04.894][error][ERROR] Username or password is incorrect. Try again. IP: 172.18.0.1. Username: me@example.org.
web_1  | [2020-09-30 15:43:04.894][response][INFO] POST /identity/connect/token (login) => 400 Bad Request
web_1  | [2020-09-30 15:43:22.871][request][INFO] POST /api/accounts/prelogin
web_1  | [2020-09-30 15:43:22.871][response][INFO] POST /api/accounts/prelogin (prelogin) => 200 OK
web_1  | [2020-09-30 15:43:22.930][request][INFO] POST /identity/connect/token
web_1  | [2020-09-30 15:43:23.041][error][ERROR] Username or password is incorrect. Try again. IP: 172.18.0.1. Username: me@example.org.
web_1  | [2020-09-30 15:43:23.041][response][INFO] POST /identity/connect/token (login) => 400 Bad Request

I'd have to break it again with an upgrade to confirm, given some tips on what to run / look for I could try again and collect more info to report back before reverting. thanks!

@themightychris commented on GitHub (Sep 30, 2020): @BlackDex the quote in the issue title is pasted verbatim from the container log, and I believe is the same wording I saw in the browser. If it didn't match exactly it was a clean "username/password wrong" error. Here's the container log from `up` on new version to failed login: ```console web_1 | /--------------------------------------------------------------------\ web_1 | | Starting Bitwarden_RS | web_1 | | Version 1.16.3 | web_1 | |--------------------------------------------------------------------| web_1 | | This is an *unofficial* Bitwarden implementation, DO NOT use the | web_1 | | official channels to report bugs/features, regardless of client. | web_1 | | Send usage/configuration questions or feature requests to: | web_1 | | https://bitwardenrs.discourse.group/ | web_1 | | Report suspected bugs/issues in the software itself at: | web_1 | | https://github.com/dani-garcia/bitwarden_rs/issues/new | web_1 | \--------------------------------------------------------------------/ web_1 | web_1 | Running migration 20180919144557 web_1 | Running migration 20181127152651 web_1 | Running migration 20190526216651 web_1 | Running migration 20191010083032 web_1 | Running migration 20191117011009 web_1 | Running migration 20200313205045 web_1 | Running migration 20200409235005 web_1 | Running migration 20200701214531 web_1 | [2020-09-30 15:42:42.581][start][INFO] Rocket has launched from http://0.0.0.0:80 web_1 | [2020-09-30 15:42:56.680][request][INFO] GET /api/accounts/revision-date web_1 | [2020-09-30 15:42:56.680][auth][ERROR] Unauthorized Error: Invalid claim web_1 | [2020-09-30 15:42:56.680][response][INFO] GET /api/accounts/revision-date (revision_date) => 401 Unauthorized web_1 | [2020-09-30 15:43:04.714][request][INFO] POST /api/accounts/prelogin web_1 | [2020-09-30 15:43:04.714][response][INFO] POST /api/accounts/prelogin (prelogin) => 200 OK web_1 | [2020-09-30 15:43:04.783][request][INFO] POST /identity/connect/token web_1 | [2020-09-30 15:43:04.894][error][ERROR] Username or password is incorrect. Try again. IP: 172.18.0.1. Username: me@example.org. web_1 | [2020-09-30 15:43:04.894][response][INFO] POST /identity/connect/token (login) => 400 Bad Request web_1 | [2020-09-30 15:43:22.871][request][INFO] POST /api/accounts/prelogin web_1 | [2020-09-30 15:43:22.871][response][INFO] POST /api/accounts/prelogin (prelogin) => 200 OK web_1 | [2020-09-30 15:43:22.930][request][INFO] POST /identity/connect/token web_1 | [2020-09-30 15:43:23.041][error][ERROR] Username or password is incorrect. Try again. IP: 172.18.0.1. Username: me@example.org. web_1 | [2020-09-30 15:43:23.041][response][INFO] POST /identity/connect/token (login) => 400 Bad Request ``` I'd have to break it again with an upgrade to confirm, given some tips on what to run / look for I could try again and collect more info to report back before reverting. thanks!

kerem commented

2026-03-03 02:03:35 +03:00

Author

Owner

@BlackDex commented on GitHub (Oct 1, 2020):

i would have to try and do the same my self to figure out what could be the case here.
Rather busy the past few day's so don't know if i have the time.

@BlackDex commented on GitHub (Oct 1, 2020): i would have to try and do the same my self to figure out what could be the case here. Rather busy the past few day's so don't know if i have the time.

kerem commented

2026-03-03 02:03:36 +03:00

Author

Owner

@themightychris commented on GitHub (Oct 7, 2020):

What are the odds that migrating to mysql or postgres before migrating could help my situation or make debugging easier?

@themightychris commented on GitHub (Oct 7, 2020): What are the odds that migrating to mysql or postgres before migrating could help my situation or make debugging easier?

kerem commented

2026-03-03 02:03:36 +03:00

Author

Owner

@BlackDex commented on GitHub (Oct 7, 2020):

i actually have no clue.
The problem is that you probably can't get a version that old with mysql any more.
Since mprasil's docker hub repo is empty now. That makes it hard for me to test also.

I Would have to try and build a that old version and test it.

@BlackDex commented on GitHub (Oct 7, 2020): i actually have no clue. The problem is that you probably can't get a version that old with mysql any more. Since mprasil's docker hub repo is empty now. That makes it hard for me to test also. I Would have to try and build a that old version and test it.

kerem commented

2026-03-03 02:03:36 +03:00

Author

Owner

@themightychris commented on GitHub (Oct 7, 2020):

@BlackDex if I set up a VM with a clone of my current database+image and a test user added, would you be interested in having a look?

@themightychris commented on GitHub (Oct 7, 2020): @BlackDex if I set up a VM with a clone of my current database+image and a test user added, would you be interested in having a look?

kerem commented

2026-03-03 02:03:36 +03:00

Author

Owner

@BlackDex commented on GitHub (Oct 7, 2020):

Do you have many users or orgs?

@BlackDex commented on GitHub (Oct 7, 2020): Do you have many users or orgs?

kerem commented

2026-03-03 02:03:36 +03:00

Author

Owner

@BlackDex commented on GitHub (Oct 7, 2020):

@themightychris What i would need is probably a before and after sqlite database to spot the differences there with indeed a test user which would have access to the before database, and not to the after one.

Then those credentials and both databases would be enough for me.

@BlackDex commented on GitHub (Oct 7, 2020): @themightychris What i would need is probably a before and after sqlite database to spot the differences there with indeed a test user which would have access to the before database, and not to the after one. Then those credentials and both databases would be enough for me.

kerem commented

2026-03-03 02:03:36 +03:00

Author

Owner

@BlackDex commented on GitHub (Oct 8, 2020):

@themightychris Actually, if you have the old database with a working user for me, that would be enough also.
Since i can just start my dev instances here with that, and it will do the migration.

@BlackDex commented on GitHub (Oct 8, 2020): @themightychris Actually, if you have the old database with a working user for me, that would be enough also. Since i can just start my dev instances here with that, and it will do the migration.

kerem commented

2026-03-03 02:03:36 +03:00

Author

Owner

@BlackDex commented on GitHub (Oct 11, 2020):

@themightychris on the Matrix Chat there was someone which had similar issues and also uses docker-compose.
He did the following, and that resolved his issue.

docker-compose stop bitwarden
docker-compose pull
docker-compose up -d
docker-compose restart bitwarden

Could you try the same steps and see if that resolves your issue as well?

@BlackDex commented on GitHub (Oct 11, 2020): @themightychris on the Matrix Chat there was someone which had similar issues and also uses docker-compose. He did the following, and that resolved his issue. ``` docker-compose stop bitwarden docker-compose pull docker-compose up -d docker-compose restart bitwarden ``` Could you try the same steps and see if that resolves your issue as well?

kerem commented

2026-03-03 02:03:36 +03:00

Author

Owner

@potvinp commented on GitHub (Oct 15, 2020):

@themightychris on the Matrix Chat there was someone which had similar issues and also uses docker-compose.
He did the following, and that resolved his issue.
docker-compose stop bitwarden
docker-compose pull
docker-compose up -d
docker-compose restart bitwarden
Could you try the same steps and see if that resolves your issue as well?

Good morning,

I was having the same issue as @themightychris, and after running the commands you mentioned I no longer receive the error and everything appears to be running without issues. Thanks!

@potvinp commented on GitHub (Oct 15, 2020): > @themightychris on the Matrix Chat there was someone which had similar issues and also uses docker-compose. > He did the following, and that resolved his issue. > > ``` > docker-compose stop bitwarden > docker-compose pull > docker-compose up -d > docker-compose restart bitwarden > ``` > > Could you try the same steps and see if that resolves your issue as well? Good morning, I was having the same issue as @themightychris, and after running the commands you mentioned I no longer receive the error and everything appears to be running without issues. Thanks!

kerem commented

2026-03-03 02:03:36 +03:00

Author

Owner

@BlackDex commented on GitHub (Nov 18, 2020):

@themightychris Were you able to solve the issue?

@BlackDex commented on GitHub (Nov 18, 2020): @themightychris Were you able to solve the issue?

kerem commented

2026-03-03 02:03:36 +03:00

Author

Owner

@BlackDex commented on GitHub (Dec 11, 2020):

Closing this ticket die to inactivity.
Also issue seems to be resolved by other user which has the same issue.

@BlackDex commented on GitHub (Dec 11, 2020): Closing this ticket die to inactivity. Also issue seems to be resolved by other user which has the same issue.

Rows
Columns

[GH-ISSUE #1165] "Username or password is incorrect." after upgrade from 1.1.0 #820