starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-05 00:29:40 +03:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

"Username or password is incorrect." after upgrade from 1.1.0 #819

New Issue
Closed
opened 2026-02-04 22:49:11 +03:00 by OVERLORD · 13 comments
OVERLORD commented 2026-02-04 22:49:11 +03:00
Owner
Copy Link

Originally created by @themightychris on GitHub (Sep 30, 2020).

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). 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?
OVERLORD added the questionbetter for forum labels 2026-02-04 22:49:11 +03:00
OVERLORD commented 2026-02-04 22:49:18 +03:00
Author
Owner
Copy Link

@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?
OVERLORD commented 2026-02-04 22:49:22 +03:00
Author
Owner
Copy Link

@themightychris commented on GitHub (Oct 1, 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 (Oct 1, 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!
OVERLORD commented 2026-02-04 22:49:25 +03:00
Author
Owner
Copy Link

@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.
OVERLORD commented 2026-02-04 22:49:29 +03:00
Author
Owner
Copy Link

@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?
OVERLORD commented 2026-02-04 22:49:33 +03:00
Author
Owner
Copy Link

@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.
OVERLORD commented 2026-02-04 22:49:36 +03:00
Author
Owner
Copy Link

@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?
OVERLORD commented 2026-02-04 22:49:43 +03:00
Author
Owner
Copy Link

@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?
OVERLORD commented 2026-02-04 22:49:47 +03:00
Author
Owner
Copy Link

@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.
OVERLORD commented 2026-02-04 22:49:49 +03:00
Author
Owner
Copy Link

@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.
OVERLORD commented 2026-02-04 22:49:52 +03:00
Author
Owner
Copy Link

@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?
OVERLORD commented 2026-02-04 22:49:59 +03:00
Author
Owner
Copy Link

@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!
OVERLORD commented 2026-02-04 22:50:04 +03:00
Author
Owner
Copy Link

@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?
OVERLORD commented 2026-02-04 22:50:11 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Dec 12, 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 12, 2020): Closing this ticket die to inactivity. Also issue seems to be resolved by other user which has the same issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
troubleshooting
wontfix
No Label better for forum question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#819
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?