Originally created by @Dvalin21 on GitHub (Feb 21, 2023).
Fresh install of 1.27 and will not allow me to login
Installed the latest version 1.27 and started getting similar issue that was reported in 1.26
Once installed I attempt to log into the server and it says password or username incorrect.
I verified the username and password and its correct. I tried restarting the containers. Same issue.
Tried deleting all files and reinstalling containers. Same issue.
This was installed via docker compose on Synology Nas
[2023-02-20 21:51:26.132][vaultwarden][INFO] Private key created correctly.
[2023-02-20 21:51:26.132][vaultwarden][INFO] Public key created correctly.
[2023-02-20 21:51:26.134][vaultwarden::util][WARN] Can't connect to database, retrying: DieselCon.
[CAUSE] BadConnection(
"FATAL: could not open file "global/pg_filenode.map": No such file or directory\n",
)
[2023-02-20 21:51:27.136][vaultwarden::util][WARN] Can't connect to database, retrying: DieselCon.
[CAUSE] BadConnection(
"could not connect to server: Connection refused\n\tIs the server running on host "vaultwarden-db" (x.x.x.x) and accepting\n\tTCP/IP connections on port 5432?\n",
)
[2023-02-20 21:51:28.138][vaultwarden::util][WARN] Can't connect to database, retrying: DieselCon.
[CAUSE] BadConnection(
"could not connect to server: Connection refused\n\tIs the server running on host "vaultwarden-db" (x.x.x.x) and accepting\n\tTCP/IP connections on port 5432?\n",
)
[2023-02-20 21:53:36.408][vaultwarden::util][WARN] Can't connect to database, retrying: DieselCon.
[CAUSE] BadConnection(
"could not connect to server: Connection timed out\n\tIs the server running on host "vaultwarden-db" (x.x.x.x) and accepting\n\tTCP/IP connections on port 5432?\n",
)
[2023-02-20 21:53:55.299][start][INFO] Rocket has launched from http://0.0.0.0:4020
[2023-02-20 21:55:03.266][request][INFO] GET /api/devices/knowndevice/ email address
[2023-02-20 21:55:03.267][response][INFO] (get_known_device) GET /api/devices/knowndevice// => 200 OK
[2023-02-20 21:55:06.424][request][INFO] POST /identity/accounts/prelogin
[2023-02-20 21:55:06.424][response][INFO] (prelogin) POST /identity/accounts/prelogin => 200 OK
[2023-02-20 21:55:06.511][request][INFO] POST /identity/connect/token
[2023-02-20 21:55:06.512][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: ip address. Username: email address
[2023-02-20 21:55:06.512][response][INFO] (login) POST /identity/connect/token => 400 Bad Request
Originally created by @Dvalin21 on GitHub (Feb 21, 2023).
<!--
# ###
NOTE: Please update to 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
# ###
-->
Fresh install of 1.27 and will not allow me to login
Installed the latest version 1.27 and started getting similar issue that was reported in 1.26
Once installed I attempt to log into the server and it says password or username incorrect.
I verified the username and password and its correct. I tried restarting the containers. Same issue.
Tried deleting all files and reinstalling containers. Same issue.
This was installed via docker compose on Synology Nas
Here's the docker-compose I used
version: "3.9"
services:
db:
image: postgres
container_name: Vaultwarden-DB
hostname: vaultwarden-db
mem_limit: 512m
cpu_shares: 768
security_opt:
- no-new-privileges:true
user: 1026:100
healthcheck:
test: ["CMD", "pg_isready", "-q", "-d", "vaultwarden", "-U", "vaultwardenuser"]
timeout: 45s
interval: 10s
retries: 10
volumes:
- /volume1/docker/vaultwarden/db:/var/lib/postgresql/data:rw
environment:
POSTGRES_DB: vaultwarden
POSTGRES_USER:
POSTGRES_PASSWORD:
restart: on-failure:5
vaultwarden:
image: vaultwarden/server:latest
container_name: Vaultwarden
hostname: vaultwarden
mem_limit: 256m
mem_reservation: 96m
cpu_shares: 1024
security_opt:
- no-new-privileges:true
user: 1026:100
ports:
- 4080:4020
volumes:
- /volume1/docker/vaultwarden/data:/data:rw
environment:
ROCKET_PORT: 4020
DATABASE_URL: postgresql://user:pass@vaultwarden-db:5432/vaultwarden
ADMIN_TOKEN: masterpass
DISABLE_ADMIN_TOKEN: false
DOMAIN: https://domain.com
SMTP_HOST: smtp.gmail.com
SMTP_FROM: email address
SMTP_PORT: 587
SMTP_SECURITY: starttls
SMTP_USERNAME: email address
SMTP_PASSWORD: password
restart: on-failure:5
depends_on:
db:
condition: service_started
From Portainer Logs
/--------------------------------------------------------------------\
| Starting Vaultwarden |
| Version 1.27.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.
[2023-02-20 21:47:37.437][start][INFO] Rocket has launched from http://0.0.0.0:4020
[2023-02-20 21:49:03.808][request][INFO] GET /api/devices/knowndevice/email address/
[2023-02-20 21:49:03.810][response][INFO] (get_known_device) GET /api/devices/knowndevice/<email>/<uuid> => 200 OK
[2023-02-20 21:49:56.457][request][INFO] POST /identity/accounts/prelogin
[2023-02-20 21:49:56.457][response][INFO] (prelogin) POST /identity/accounts/prelogin => 200 OK
[2023-02-20 21:49:56.552][request][INFO] POST /identity/connect/token
[2023-02-20 21:49:56.553][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: xxx.xxx.xxx.xxx. Username: xxxx@xxxx.com.
[2023-02-20 21:49:56.553][response][INFO] (login) POST /identity/connect/token => 400 Bad Request
[2023-02-20 21:51:17.978][rocket::server][WARN] Received SIGTERM. Requesting shutdown.
[2023-02-20 21:51:17.978][vaultwarden][INFO] Vaultwarden process exited!
/--------------------------------------------------------------------\
| Starting Vaultwarden |
| Version 1.27.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.
[2023-02-20 21:51:26.132][vaultwarden][INFO] Private key created correctly.
[2023-02-20 21:51:26.132][vaultwarden][INFO] Public key created correctly.
[2023-02-20 21:51:26.134][vaultwarden::util][WARN] Can't connect to database, retrying: DieselCon.
[CAUSE] BadConnection(
"FATAL: could not open file \"global/pg_filenode.map\": No such file or directory\n",
)
[2023-02-20 21:51:27.136][vaultwarden::util][WARN] Can't connect to database, retrying: DieselCon.
[CAUSE] BadConnection(
"could not connect to server: Connection refused\n\tIs the server running on host \"vaultwarden-db\" (x.x.x.x) and accepting\n\tTCP/IP connections on port 5432?\n",
)
[2023-02-20 21:51:28.138][vaultwarden::util][WARN] Can't connect to database, retrying: DieselCon.
[CAUSE] BadConnection(
"could not connect to server: Connection refused\n\tIs the server running on host \"vaultwarden-db\" (x.x.x.x) and accepting\n\tTCP/IP connections on port 5432?\n",
)
[2023-02-20 21:53:36.408][vaultwarden::util][WARN] Can't connect to database, retrying: DieselCon.
[CAUSE] BadConnection(
"could not connect to server: Connection timed out\n\tIs the server running on host \"vaultwarden-db\" (x.x.x.x) and accepting\n\tTCP/IP connections on port 5432?\n",
)
[2023-02-20 21:53:55.299][start][INFO] Rocket has launched from http://0.0.0.0:4020
[2023-02-20 21:55:03.266][request][INFO] GET /api/devices/knowndevice/ email address
[2023-02-20 21:55:03.267][response][INFO] (get_known_device) GET /api/devices/knowndevice/<email>/<uuid> => 200 OK
[2023-02-20 21:55:06.424][request][INFO] POST /identity/accounts/prelogin
[2023-02-20 21:55:06.424][response][INFO] (prelogin) POST /identity/accounts/prelogin => 200 OK
[2023-02-20 21:55:06.511][request][INFO] POST /identity/connect/token
[2023-02-20 21:55:06.512][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: ip address. Username: email address
[2023-02-20 21:55:06.512][response][INFO] (login) POST /identity/connect/token => 400 Bad Request
<!--
-->
### 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.
=========================================================================================
-->
* vaultwarden version: 1.27
<!-- How the server was installed: Docker image, OS package, built from source, etc. -->
* Install method: Synology NAS in docker compose
* MySQL/MariaDB or PostgreSQL version: PostgreSQL
* Other relevant details:
### 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? -->
Installed it
I used the instructions from Marius Hosting
https://mariushosting.com/synology-install-vaultwarden-with-portainer/
### Expected behaviour
<!-- Tell us what you expected to happen --> To be able to login
### Actual behaviour
<!-- Tell us what actually happened --> kept getting invalid password
### Troubleshooting data
<!-- Share any log files, screenshots, or other relevant troubleshooting data --> (stated in description)
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 @Dvalin21 on GitHub (Feb 21, 2023).
Fresh install of 1.27 and will not allow me to login
Installed the latest version 1.27 and started getting similar issue that was reported in 1.26
Once installed I attempt to log into the server and it says password or username incorrect.
I verified the username and password and its correct. I tried restarting the containers. Same issue.
Tried deleting all files and reinstalling containers. Same issue.
This was installed via docker compose on Synology Nas
Here's the docker-compose I used
version: "3.9"
services:
db:
image: postgres
container_name: Vaultwarden-DB
hostname: vaultwarden-db
mem_limit: 512m
cpu_shares: 768
security_opt:
- no-new-privileges:true
user: 1026:100
healthcheck:
test: ["CMD", "pg_isready", "-q", "-d", "vaultwarden", "-U", "vaultwardenuser"]
timeout: 45s
interval: 10s
retries: 10
volumes:
- /volume1/docker/vaultwarden/db:/var/lib/postgresql/data:rw
environment:
POSTGRES_DB: vaultwarden
POSTGRES_USER:
POSTGRES_PASSWORD:
restart: on-failure:5
vaultwarden:
image: vaultwarden/server:latest
container_name: Vaultwarden
hostname: vaultwarden
mem_limit: 256m
mem_reservation: 96m
cpu_shares: 1024
security_opt:
- no-new-privileges:true
user: 1026:100
ports:
- 4080:4020
volumes:
- /volume1/docker/vaultwarden/data:/data:rw
environment:
ROCKET_PORT: 4020
DATABASE_URL: postgresql://user:pass@vaultwarden-db:5432/vaultwarden
ADMIN_TOKEN: masterpass
DISABLE_ADMIN_TOKEN: false
DOMAIN: https://domain.com
SMTP_HOST: smtp.gmail.com
SMTP_FROM: email address
SMTP_PORT: 587
SMTP_SECURITY: starttls
SMTP_USERNAME: email address
SMTP_PASSWORD: password
restart: on-failure:5
depends_on:
db:
condition: service_started
From Portainer Logs
/--------------------------------------------------------------------
| Starting Vaultwarden |
Deployment environment
Install method: Synology NAS in docker compose
MySQL/MariaDB or PostgreSQL version: PostgreSQL
Other relevant details:
Steps to reproduce
Installed it
I used the instructions from Marius Hosting
https://mariushosting.com/synology-install-vaultwarden-with-portainer/
Expected behaviour
To be able to loginActual behaviour
kept getting invalid passwordTroubleshooting data
(stated in description)