Originally created by @ph0 on GitHub (May 8, 2022).
I am fully updated.
This happened before.
I click login and it tells me a login notification email failed without letting me login.
I can login to admin with the admin token from my config.json. I force resync of clients and that did nothing.
This is the second time this has happened. Last time 14 hours passed and it suddenly started working again with no explanation as to why. I have rebooted my server. Same result.
Your environment (Generated via diagnostics page)
Vaultwarden version: v1.24.0
Web-vault version: v2.25.1
Running within Docker: true (Base: Debian)
Environment settings overridden: true
Uses a reverse proxy: true
IP Header check: true (X-Real-IP)
Internet access: true
Internet access via a proxy: false
DNS Check: true
Time Check: true
Domain Configuration Check: false
HTTPS Check: true
Database type: SQLite
Database version: 3.35.4
Clients used:
Reverse proxy and version:
Other relevant information:
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED, ADMIN_TOKEN
You have require_device_email enabled which prevents a login if sending a new device email failed. I would check your smtp settings or smtp server.
14 hours seems like a strange number, but could be some mail server timeout setting or whatever.
@BlackDex commented on GitHub (May 8, 2022):
You have `require_device_email` enabled which prevents a login if sending a new device email failed. I would check your smtp settings or smtp server.
14 hours seems like a strange number, but could be some mail server timeout setting or whatever.
Can you explain further? I have used the same email/pass from the same device for more than 1 year now with no issues. Also, I can login and check nothing because my passwords are stored in Vaultwarden.
@ph0 commented on GitHub (May 8, 2022):
Can you explain further? I have used the same email/pass from the same device for more than 1 year now with no issues. Also, I can login and check nothing because my passwords are stored in Vaultwarden.
I sent a test email from admin SMTP settings and got this error: "Error sending SMTP test email
SMTP Connection error: error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:332:"
@ph0 commented on GitHub (May 8, 2022):
I sent a test email from admin SMTP settings and got this error: "Error sending SMTP test email
SMTP Connection error: error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:332:"
Well either something is not configured correctly for sending emails.
Or the mail server you are using has issues, like a bad certificate, or something. But that is just guessing.
The only thing i know for sure is that Vaultwarden can't send a mail, and that is causing you to not be able to login.
Disabled require_device_email and try again.
This at least isn't a Vaultwarden issues it self.
@BlackDex commented on GitHub (May 8, 2022):
Well either something is not configured correctly for sending emails.
Or the mail server you are using has issues, like a bad certificate, or something. But that is just guessing.
The only thing i know for sure is that Vaultwarden can't send a mail, and that is causing you to not be able to login.
Disabled `require_device_email` and try again.
This at least isn't a Vaultwarden issues it self.
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 @ph0 on GitHub (May 8, 2022).
I am fully updated.
This happened before.
I click login and it tells me a login notification email failed without letting me login.
I can login to admin with the admin token from my config.json. I force resync of clients and that did nothing.
This is the second time this has happened. Last time 14 hours passed and it suddenly started working again with no explanation as to why. I have rebooted my server. Same result.
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED, ADMIN_TOKEN
@BlackDex commented on GitHub (May 8, 2022):
You have
require_device_emailenabled which prevents a login if sending a new device email failed. I would check your smtp settings or smtp server.14 hours seems like a strange number, but could be some mail server timeout setting or whatever.
@ph0 commented on GitHub (May 8, 2022):
Can you explain further? I have used the same email/pass from the same device for more than 1 year now with no issues. Also, I can login and check nothing because my passwords are stored in Vaultwarden.
@ph0 commented on GitHub (May 8, 2022):
I sent a test email from admin SMTP settings and got this error: "Error sending SMTP test email
SMTP Connection error: error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:332:"
@ph0 commented on GitHub (May 8, 2022):
I must note my login was working until the moment I cleared my browser history and cache.
@BlackDex commented on GitHub (May 8, 2022):
Well either something is not configured correctly for sending emails.
Or the mail server you are using has issues, like a bad certificate, or something. But that is just guessing.
The only thing i know for sure is that Vaultwarden can't send a mail, and that is causing you to not be able to login.
Disabled
require_device_emailand try again.This at least isn't a Vaultwarden issues it self.