mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-25 17:25:57 +03:00
[GH-ISSUE #967] SMTP SSL Error "Could not encrypt connection" #687
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#687
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @davidus05 on GitHub (Apr 15, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/967
SMTP SSL Error "Could not encrypt connection"
Some days ago I generated a new SSL certificate with Let's Encrypt for our exchange server. I use it to connect via SMTP to send mails from bitwarden_rs. Now I wanted to log in to the vault on the Android app, but this doesn't work, because: "Could not send login notification email. Please contact your administrator.
Then I saw that sending emails in general does not work anymore.
Your environment
Steps to reproduce
Expected behaviour
I should get an email.
Actual behaviour
Sending an email did not work.
Relevant logs
[2020-04-15 20:32:12][request][INFO] POST /admin/test/smtp/
[2020-04-15 20:32:12][lettre::smtp][INFO] connection established to *******:587
[2020-04-15 20:32:12][error][ERROR] LetreErr.
[CAUSE] Client(
"Could not encrypt connection, aborting",
)
How to solve this problem or is there a way to ignore the certificate like in Bitwarden orig: (https://github.com/bitwarden/server/issues/451)
@BlackDex commented on GitHub (Jun 4, 2020):
Do you use a self generated SSL Certificate?
What happens if you try executing:
That should report with a certificate, but i doubt that it will on port 587, since that is by default a submission port which normally uses starttls instead of ssl.
For example, GMail uses SSL and that works using:
@davidus05 commented on GitHub (Jun 7, 2020):
Hey, thanks for your reply!
The first command gives following output:
The second command:
@MichZipp commented on GitHub (Aug 26, 2020):
@davidus05 I currently have the same issue, did you solve it in the meantime?
@BlackDex commented on GitHub (Sep 22, 2020):
@davidus05 & @MichZipp could you both try again with the latest testing image from docker? There are several items changed regarding emails maybe they fixed your issues.
@MichZipp commented on GitHub (Sep 22, 2020):
@BlackDex Issue is fixed, thanks a lot!
@siddjellali commented on GitHub (Mar 19, 2021):
Hi,
It seems the same issue appears again... Anyone Else has the issue ?