starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-25 17:25:57 +03:00
Code Issues 39 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #2823] 1.26.0 Unable to log into vaultwarden after update #1388

New issue
Closed
opened 2026-03-03 02:08:44 +03:00 by kerem · 13 comments
kerem commented 2026-03-03 02:08:44 +03:00
Owner
Copy link

Originally created by @chrispro-21 on GitHub (Oct 14, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2823

Subject of the issue

Unable to log in to vaultwarden after updating from 1.25.2 to 1.26.0. I went back to 1.25.2 as logging in still works, but I got a Username or Password is incorrect. Try again. IP: <my IP address>. Username: <email>.

Deployment environment

  • vaultwarden version: 1.26.0

  • Install method: docker

  • Clients used: web vault

  • Reverse proxy and version:

  • MySQL/MariaDB or PostgreSQL version:

  • Other relevant details: single account on server, caddy reverse proxy outside of docker network.

Steps to reproduce

Update from 1.25.2 to 1.26.0 on docker

Expected behavior

a successful login of an account

Actual behavior

Unable to login with error: Username or Password is incorrect. Try again. IP: <my IP address>. Username: <email>.

Troubleshooting data

/--------------------------------------------------------------------\
|                        Starting Vaultwarden                        |
|                           Version 1.26.0                           |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Send usage/configuration questions or feature requests to:         |
|   https://vaultwarden.discourse.group/                             |
| Report suspected bugs/issues in the software itself at:            |
|   https://github.com/dani-garcia/vaultwarden/issues/new            |
\--------------------------------------------------------------------/

[INFO] No .env file found.

[2022-10-14 21:49:22.983][start][INFO] Rocket has launched from http://0.0.0.0:80
[2022-10-14 21:49:30.811][request][INFO] POST /api/accounts/prelogin
[2022-10-14 21:49:30.812][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK
[2022-10-14 21:49:30.834][request][INFO] POST /identity/connect/token
[2022-10-14 21:49:30.834][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: x.x.x.x. Username: xxxxxxx@xxxxxx.com.
[2022-10-14 21:49:30.834][response][INFO] (login) POST /identity/connect/token => 400 Bad Request
[2022-10-14 21:51:40.838][request][INFO] POST /api/accounts/prelogin
[2022-10-14 21:51:40.840][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK
Originally created by @chrispro-21 on GitHub (Oct 14, 2022). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2823 <!-- # ### NOTE: Please update the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue <!-- Describe your issue here. --> Unable to log in to vaultwarden after updating from 1.25.2 to 1.26.0. I went back to 1.25.2 as logging in still works, but I got a `Username or Password is incorrect. Try again. IP: <my IP address>. Username: <email>.` ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: 1.26.0 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: docker * Clients used: web vault <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> * Reverse proxy and version: <!-- if applicable --> * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> * Other relevant details: single account on server, caddy reverse proxy outside of docker network. ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> Update from 1.25.2 to 1.26.0 on docker ### Expected behavior <!-- Tell us what you expected to happen --> a successful login of an account ### Actual behavior <!-- Tell us what actually happened --> Unable to login with error: `Username or Password is incorrect. Try again. IP: <my IP address>. Username: <email>.` ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data --> ``` /--------------------------------------------------------------------\ | Starting Vaultwarden | | Version 1.26.0 | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Send usage/configuration questions or feature requests to: | | https://vaultwarden.discourse.group/ | | Report suspected bugs/issues in the software itself at: | | https://github.com/dani-garcia/vaultwarden/issues/new | \--------------------------------------------------------------------/ [INFO] No .env file found. [2022-10-14 21:49:22.983][start][INFO] Rocket has launched from http://0.0.0.0:80 [2022-10-14 21:49:30.811][request][INFO] POST /api/accounts/prelogin [2022-10-14 21:49:30.812][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK [2022-10-14 21:49:30.834][request][INFO] POST /identity/connect/token [2022-10-14 21:49:30.834][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: x.x.x.x. Username: xxxxxxx@xxxxxx.com. [2022-10-14 21:49:30.834][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-10-14 21:51:40.838][request][INFO] POST /api/accounts/prelogin [2022-10-14 21:51:40.840][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK ```
kerem 2026-03-03 02:08:44 +03:00
kerem commented 2026-03-03 02:08:45 +03:00
Author
Owner
Copy link

@BlackDex commented on GitHub (Oct 14, 2022):

Which database are you using?
What do you see with both versions in the admin interface at the users section?

Also, could you provide the support string of at least the working version, and if possible also the non-working.

<!-- gh-comment-id:1279553957 --> @BlackDex commented on GitHub (Oct 14, 2022): Which database are you using? What do you see with both versions in the admin interface at the users section? Also, could you provide the support string of at least the working version, and if possible also the non-working.
kerem commented 2026-03-03 02:08:46 +03:00
Author
Owner
Copy link

@kb8cb40j1av39c02 commented on GitHub (Oct 15, 2022):

Experienced the same issue with a similar setup. Standard Vaultwarden installation with SQLite. My container got auto-updated by watchtower as do other containers.
I was able to fix the issue by rebooting my docker host. I also recall having to do that last time after Vaultwarden got updated.
Strange behaviour that isn't expexted.

<!-- gh-comment-id:1279619676 --> @kb8cb40j1av39c02 commented on GitHub (Oct 15, 2022): Experienced the same issue with a similar setup. Standard Vaultwarden installation with SQLite. My container got auto-updated by watchtower as do other containers. I was able to fix the issue by rebooting my docker host. I also recall having to do that last time after Vaultwarden got updated. Strange behaviour that isn't expexted.
kerem commented 2026-03-03 02:08:46 +03:00
Author
Owner
Copy link

@zaidi-01 commented on GitHub (Oct 15, 2022):

I'm having this issue as well on 1.26.0. The /identity/connect/token endpoint keeps throwing a 400 and I can't access my vault at all.

/--------------------------------------------------------------------\
|                        Starting Vaultwarden                        |
|                           Version 1.26.0                           |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Send usage/configuration questions or feature requests to:         |
|   https://vaultwarden.discourse.group/                             |
| Report suspected bugs/issues in the software itself at:            |
|   https://github.com/dani-garcia/vaultwarden/issues/new            |
\--------------------------------------------------------------------/
[INFO] No .env file found.
[DEPRECATED]: `SMTP_SSL` or `SMTP_EXPLICIT_TLS` is set. Please use `SMTP_SECURITY` instead.
[2022-10-15 05:55:53.688][start][INFO] Rocket has launched from http://0.0.0.0:80
[2022-10-15 05:57:20.939][request][INFO] POST /api/accounts/prelogin
[2022-10-15 05:57:20.948][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK
[2022-10-15 05:57:21.050][request][INFO] POST /identity/connect/token
[2022-10-15 05:57:21.153][error][ERROR] 2FA token not provided
[2022-10-15 05:57:21.153][response][INFO] (login) POST /identity/connect/token => 400 Bad Request
[2022-10-15 05:59:44.200][request][INFO] POST /api/accounts/prelogin
[2022-10-15 05:59:44.201][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK
[2022-10-15 05:59:44.272][request][INFO] POST /identity/connect/token
[2022-10-15 05:59:44.362][error][ERROR] 2FA token not provided
[2022-10-15 05:59:44.362][response][INFO] (login) POST /identity/connect/token => 400 Bad Request
<!-- gh-comment-id:1279670914 --> @zaidi-01 commented on GitHub (Oct 15, 2022): I'm having this issue as well on 1.26.0. The `/identity/connect/token` endpoint keeps throwing a 400 and I can't access my vault at all. ``` /--------------------------------------------------------------------\ | Starting Vaultwarden | | Version 1.26.0 | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Send usage/configuration questions or feature requests to: | | https://vaultwarden.discourse.group/ | | Report suspected bugs/issues in the software itself at: | | https://github.com/dani-garcia/vaultwarden/issues/new | \--------------------------------------------------------------------/ [INFO] No .env file found. [DEPRECATED]: `SMTP_SSL` or `SMTP_EXPLICIT_TLS` is set. Please use `SMTP_SECURITY` instead. [2022-10-15 05:55:53.688][start][INFO] Rocket has launched from http://0.0.0.0:80 [2022-10-15 05:57:20.939][request][INFO] POST /api/accounts/prelogin [2022-10-15 05:57:20.948][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK [2022-10-15 05:57:21.050][request][INFO] POST /identity/connect/token [2022-10-15 05:57:21.153][error][ERROR] 2FA token not provided [2022-10-15 05:57:21.153][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-10-15 05:59:44.200][request][INFO] POST /api/accounts/prelogin [2022-10-15 05:59:44.201][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK [2022-10-15 05:59:44.272][request][INFO] POST /identity/connect/token [2022-10-15 05:59:44.362][error][ERROR] 2FA token not provided [2022-10-15 05:59:44.362][response][INFO] (login) POST /identity/connect/token => 400 Bad Request ```
kerem commented 2026-03-03 02:08:46 +03:00
Author
Owner
Copy link

@BlackDex commented on GitHub (Oct 15, 2022):

I'm having this issue as well on 1.26.0. The /identity/connect/token endpoint keeps throwing a 400 and I can't access my vault at all.

/--------------------------------------------------------------------\
|                        Starting Vaultwarden                        |
|                           Version 1.26.0                           |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Send usage/configuration questions or feature requests to:         |
|   https://vaultwarden.discourse.group/                             |
| Report suspected bugs/issues in the software itself at:            |
|   https://github.com/dani-garcia/vaultwarden/issues/new            |
\--------------------------------------------------------------------/
[INFO] No .env file found.
[DEPRECATED]: `SMTP_SSL` or `SMTP_EXPLICIT_TLS` is set. Please use `SMTP_SECURITY` instead.
[2022-10-15 05:55:53.688][start][INFO] Rocket has launched from http://0.0.0.0:80
[2022-10-15 05:57:20.939][request][INFO] POST /api/accounts/prelogin
[2022-10-15 05:57:20.948][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK
[2022-10-15 05:57:21.050][request][INFO] POST /identity/connect/token
[2022-10-15 05:57:21.153][error][ERROR] 2FA token not provided
[2022-10-15 05:57:21.153][response][INFO] (login) POST /identity/connect/token => 400 Bad Request
[2022-10-15 05:59:44.200][request][INFO] POST /api/accounts/prelogin
[2022-10-15 05:59:44.201][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK
[2022-10-15 05:59:44.272][request][INFO] POST /identity/connect/token
[2022-10-15 05:59:44.362][error][ERROR] 2FA token not provided
[2022-10-15 05:59:44.362][response][INFO] (login) POST /identity/connect/token => 400 Bad Request

That isn't an error actually, it indicates you need to provide a 2fa/mfa token before you are allowed to continue to login.

<!-- gh-comment-id:1279685213 --> @BlackDex commented on GitHub (Oct 15, 2022): > I'm having this issue as well on 1.26.0. The `/identity/connect/token` endpoint keeps throwing a 400 and I can't access my vault at all. > > ``` > /--------------------------------------------------------------------\ > | Starting Vaultwarden | > | Version 1.26.0 | > |--------------------------------------------------------------------| > | This is an *unofficial* Bitwarden implementation, DO NOT use the | > | official channels to report bugs/features, regardless of client. | > | Send usage/configuration questions or feature requests to: | > | https://vaultwarden.discourse.group/ | > | Report suspected bugs/issues in the software itself at: | > | https://github.com/dani-garcia/vaultwarden/issues/new | > \--------------------------------------------------------------------/ > [INFO] No .env file found. > [DEPRECATED]: `SMTP_SSL` or `SMTP_EXPLICIT_TLS` is set. Please use `SMTP_SECURITY` instead. > [2022-10-15 05:55:53.688][start][INFO] Rocket has launched from http://0.0.0.0:80 > [2022-10-15 05:57:20.939][request][INFO] POST /api/accounts/prelogin > [2022-10-15 05:57:20.948][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK > [2022-10-15 05:57:21.050][request][INFO] POST /identity/connect/token > [2022-10-15 05:57:21.153][error][ERROR] 2FA token not provided > [2022-10-15 05:57:21.153][response][INFO] (login) POST /identity/connect/token => 400 Bad Request > [2022-10-15 05:59:44.200][request][INFO] POST /api/accounts/prelogin > [2022-10-15 05:59:44.201][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK > [2022-10-15 05:59:44.272][request][INFO] POST /identity/connect/token > [2022-10-15 05:59:44.362][error][ERROR] 2FA token not provided > [2022-10-15 05:59:44.362][response][INFO] (login) POST /identity/connect/token => 400 Bad Request > ``` That isn't an error actually, it indicates you need to provide a 2fa/mfa token before you are allowed to continue to login.
kerem commented 2026-03-03 02:08:46 +03:00
Author
Owner
Copy link

@BlackDex commented on GitHub (Oct 15, 2022):

Experienced the same issue with a similar setup. Standard Vaultwarden installation with SQLite. My container got auto-updated by watchtower as do other containers. I was able to fix the issue by rebooting my docker host. I also recall having to do that last time after Vaultwarden got updated. Strange behaviour that isn't expexted.

Needing to reboot your host is not something which can be solved by a container. I have the same kind of setup with watchtower and using the testing tagged images. I haven't experienced any issues.
In your case i would suggest to check you dockerd/host logs to see what went wrong. Could be firewalling, kernel libraries which were updated, other applications which were updated,

I really doubt it is the fault of a container. But only logs could help to try and determine it.

<!-- gh-comment-id:1279686027 --> @BlackDex commented on GitHub (Oct 15, 2022): > Experienced the same issue with a similar setup. Standard Vaultwarden installation with SQLite. My container got auto-updated by watchtower as do other containers. I was able to fix the issue by rebooting my docker host. I also recall having to do that last time after Vaultwarden got updated. Strange behaviour that isn't expexted. Needing to reboot your host is not something which can be solved by a container. I have the same kind of setup with watchtower and using the testing tagged images. I haven't experienced any issues. In your case i would suggest to check you dockerd/host logs to see what went wrong. Could be firewalling, kernel libraries which were updated, other applications which were updated, I really doubt it is the fault of a container. But only logs could help to try and determine it.
kerem commented 2026-03-03 02:08:46 +03:00
Author
Owner
Copy link

@kb8cb40j1av39c02 commented on GitHub (Oct 15, 2022):

@BlackDex from my mobile phone I was only able to just quickly restart the host and not the container itself. I'm not sure if just rebooting the container would have fixed the issue too.

<!-- gh-comment-id:1279705941 --> @kb8cb40j1av39c02 commented on GitHub (Oct 15, 2022): @BlackDex from my mobile phone I was only able to just quickly restart the host and not the container itself. I'm not sure if just rebooting the container would have fixed the issue too.
kerem commented 2026-03-03 02:08:46 +03:00
Author
Owner
Copy link

@Bloodpack commented on GitHub (Oct 15, 2022):

Same Problem here after update to 1.26.0

reboot container and host system does NOT fix the problem here

/--------------------------------------------------------------------\
|                        Starting Vaultwarden                        |
|                           Version 1.26.0                           |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Send usage/configuration questions or feature requests to:         |
|   https://vaultwarden.discourse.group/                             |
| Report suspected bugs/issues in the software itself at:            |
|   https://github.com/dani-garcia/vaultwarden/issues/new            |
\--------------------------------------------------------------------/
[INFO] No .env file found.
[2022-10-15 13:37:58.954][start][INFO] Rocket has launched from http://0.0.0.0:80
[2022-10-15 13:38:17.275][request][INFO] POST /api/accounts/prelogin
[2022-10-15 13:38:17.275][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK
[2022-10-15 13:38:17.349][request][INFO] POST /identity/connect/token
[2022-10-15 13:38:17.350][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: XXX.XXXX.XXX.X. Username: myemail@email.provider.
[2022-10-15 13:38:17.350][response][INFO] (login) POST /identity/connect/token => 400 Bad Request
[2022-10-15 13:39:59.582][request][INFO] POST /api/accounts/prelogin
[2022-10-15 13:39:59.583][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK
[2022-10-15 13:39:59.652][request][INFO] POST /identity/connect/token
[2022-10-15 13:39:59.653][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: XXX.XXXX.XXX.X. Username: myemail@email.provider.
[2022-10-15 13:39:59.653][response][INFO] (login) POST /identity/connect/token => 400 Bad Request
[2022-10-15 13:40:25.908][request][INFO] POST /api/accounts/prelogin
[2022-10-15 13:40:25.908][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK
[2022-10-15 13:40:25.986][request][INFO] POST /identity/connect/token
[2022-10-15 13:40:25.987][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: XXX.XXXX.XXX.X. Username: myemail@email.provider.
[2022-10-15 13:40:25.987][response][INFO] (login) POST /identity/connect/token => 400 Bad Request
[2022-10-15 13:41:41.202][request][INFO] POST /identity/connect/token
[2022-10-15 13:41:41.211][response][INFO] (login) POST /identity/connect/token => 400 Bad Request
[2022-10-15 13:42:10.237][request][INFO] POST /identity/connect/token
[2022-10-15 13:42:10.237][response][INFO] (login) POST /identity/connect/token => 400 Bad Request
<!-- gh-comment-id:1279749152 --> @Bloodpack commented on GitHub (Oct 15, 2022): Same Problem here after update to 1.26.0 reboot container and host system does NOT fix the problem here ```bash /--------------------------------------------------------------------\ | Starting Vaultwarden | | Version 1.26.0 | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Send usage/configuration questions or feature requests to: | | https://vaultwarden.discourse.group/ | | Report suspected bugs/issues in the software itself at: | | https://github.com/dani-garcia/vaultwarden/issues/new | \--------------------------------------------------------------------/ [INFO] No .env file found. [2022-10-15 13:37:58.954][start][INFO] Rocket has launched from http://0.0.0.0:80 [2022-10-15 13:38:17.275][request][INFO] POST /api/accounts/prelogin [2022-10-15 13:38:17.275][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK [2022-10-15 13:38:17.349][request][INFO] POST /identity/connect/token [2022-10-15 13:38:17.350][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: XXX.XXXX.XXX.X. Username: myemail@email.provider. [2022-10-15 13:38:17.350][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-10-15 13:39:59.582][request][INFO] POST /api/accounts/prelogin [2022-10-15 13:39:59.583][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK [2022-10-15 13:39:59.652][request][INFO] POST /identity/connect/token [2022-10-15 13:39:59.653][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: XXX.XXXX.XXX.X. Username: myemail@email.provider. [2022-10-15 13:39:59.653][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-10-15 13:40:25.908][request][INFO] POST /api/accounts/prelogin [2022-10-15 13:40:25.908][response][INFO] (prelogin) POST /api/accounts/prelogin => 200 OK [2022-10-15 13:40:25.986][request][INFO] POST /identity/connect/token [2022-10-15 13:40:25.987][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: XXX.XXXX.XXX.X. Username: myemail@email.provider. [2022-10-15 13:40:25.987][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-10-15 13:41:41.202][request][INFO] POST /identity/connect/token [2022-10-15 13:41:41.211][response][INFO] (login) POST /identity/connect/token => 400 Bad Request [2022-10-15 13:42:10.237][request][INFO] POST /identity/connect/token [2022-10-15 13:42:10.237][response][INFO] (login) POST /identity/connect/token => 400 Bad Request ```
kerem commented 2026-03-03 02:08:46 +03:00
Author
Owner
Copy link

@BlackDex commented on GitHub (Oct 15, 2022):

Which web-vault version are you using?
Which reverse proxy, some reverse proxies block some stuff or could be wrongly configured.
All i can say is that it works just fine for a long time now, since the code-base of 1.26.0 has been out for a while already under testing.

Also, it says login incorrect, so please double check via the /admin interface if all the correct users are there or not.
Also, post the Support String which you can generate via the admin interface under the Diagnostics page.

<!-- gh-comment-id:1279750694 --> @BlackDex commented on GitHub (Oct 15, 2022): Which web-vault version are you using? Which reverse proxy, some reverse proxies block some stuff or could be wrongly configured. All i can say is that it works just fine for a long time now, since the code-base of 1.26.0 has been out for a while already under testing. Also, it says login incorrect, so please double check via the `/admin` interface if all the correct users are there or not. Also, post the `Support String` which you can generate via the admin interface under the `Diagnostics` page.
kerem commented 2026-03-03 02:08:46 +03:00
Author
Owner
Copy link

@Bloodpack commented on GitHub (Oct 15, 2022):

@BlackDex

thank you for the reply

i solved my problem.....

i deleted the vaultwarden container and installed it again and now it works (don´t ask me why, i don´t know)
updating from 1.25.2 did break it....

i am using pfsense HA-Proxy, but i used it for a long time with no problems

<!-- gh-comment-id:1279776307 --> @Bloodpack commented on GitHub (Oct 15, 2022): @BlackDex thank you for the reply i solved my problem..... i deleted the vaultwarden container and installed it again and now it works (don´t ask me why, i don´t know) updating from 1.25.2 did break it.... i am using pfsense HA-Proxy, but i used it for a long time with no problems
kerem commented 2026-03-03 02:08:46 +03:00
Author
Owner
Copy link

@chrispro-21 commented on GitHub (Oct 15, 2022):

I'll try a reinstall next and report back.

<!-- gh-comment-id:1279812836 --> @chrispro-21 commented on GitHub (Oct 15, 2022): I'll try a reinstall next and report back.
kerem commented 2026-03-03 02:08:46 +03:00
Author
Owner
Copy link

@chrispro-21 commented on GitHub (Oct 15, 2022):

The reinstall appeared to work after exporting my vaults to json and deleting the /vw-data/ and recreating it.

Thank you!

<!-- gh-comment-id:1279819770 --> @chrispro-21 commented on GitHub (Oct 15, 2022): The reinstall appeared to work after exporting my vaults to json and deleting the /vw-data/ and recreating it. Thank you!
kerem commented 2026-03-03 02:08:46 +03:00
Author
Owner
Copy link

@BlackDex commented on GitHub (Oct 15, 2022):

Strange though.
Almost looks like it didn't used the old database and created a new one without overwriting the old.

Glad you still have all the data and it works now.

<!-- gh-comment-id:1279820529 --> @BlackDex commented on GitHub (Oct 15, 2022): Strange though. Almost looks like it didn't used the old database and created a new one without overwriting the old. Glad you still have all the data and it works now.
kerem commented 2026-03-03 02:08:46 +03:00
Author
Owner
Copy link

@Bloodpack commented on GitHub (Oct 15, 2022):

@chrispro-21
I did not have to delete my persistent data folders and it worked

<!-- gh-comment-id:1279820565 --> @Bloodpack commented on GitHub (Oct 15, 2022): @chrispro-21 I did not have to delete my persistent data folders and it worked
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
revert-7033-patch-1
cached-config-operations
test_dylint
1.35.7
1.35.6
1.35.5
1.35.4
1.35.3
1.35.2
1.35.1
1.35.0
1.34.3
1.34.2
1.34.1
1.34.0
1.33.2
1.33.1
1.33.0
1.32.7
1.32.6
1.32.5
1.32.4
1.32.3
1.32.2
1.32.1
1.32.0
1.31.0
1.30.5
1.30.4
1.30.3
1.30.2
1.30.1
1.30.0
1.29.2
1.29.1
1.29.0
1.28.1
1.28.0
1.27.0
1.26.0
1.25.2
1.25.1
1.25.0
1.24.0
1.23.1
1.23.0
1.22.2
1.22.1
1.22.0
1.21.0
1.20.0
1.19.0
1.18.0
1.17.0
1.16.3
1.16.2
1.16.1
1.16.0
1.15.1
1.15.0
1.14.2
1.14.1
1.14
1.13.1
1.13.0
1.12.0
1.11.0
1.10.0
1.9.1
1.9.0
1.8.0
1.7.0
1.6.1
1.6.0
1.5.0
1.4.0
1.3.0
1.2.0
1.1.0
1.0.0
0.13.0
0.12.0
0.11.0
0.10.0
0.9.0
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 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
question
troubleshooting
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vaultwarden#1388
No description provided.