# Diagnosing ssl errors with sending emails?

**URL:** <https://vaultwarden.discourse.group/t/diagnosing-ssl-errors-with-sending-emails/1188>\
**Category:** Help\
**Created:** [October 12, 2021, 3:37pm UTC](https://vaultwarden.discourse.group/t/diagnosing-ssl-errors-with-sending-emails/1188 "2021-10-12T15:37:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nktech1135](https://avatars.discourse-cdn.com/v4/letter/n/82dd89/32.png) [@nktech1135](https://vaultwarden.discourse.group/u/nktech1135)\
**Post date:** [October 12, 2021, 3:37pm UTC](https://vaultwarden.discourse.group/t/diagnosing-ssl-errors-with-sending-emails/1188/1 "2021-10-12T15:37:55Z")

</div>

Hello.  
Recently our instance of vaultwarden has started giving ssl errors like the following when trying to send an email.

```auto
Oct 12 11:34:07 clarion1.compass.lan passageway[27719]: [2021-10-12 11:34:07.778][request][INFO] POST /api/accounts/password-hint
Oct 12 11:34:07 clarion1.compass.lan passageway[27719]: [2021-10-12 11:34:07.986][bitwarden_rs::mail][ERROR] SMTP IO error: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:s3_clnt.c:1264: (certificate has expired)
Oct 12 11:34:07 clarion1.compass.lan passageway[27719]: [2021-10-12 11:34:07.988][response][INFO] POST /api/accounts/password-hint (password_hint) => 400 Bad Request

```

How can i see the smtp log to check the cert? Mail settings haven’t changed recently and the certs are valid per openssl s\_client  
Would it matter if this version wasn’t up to date? For example, could the recent let’sencrypt cert expiration have affected the internals somehow? The certs in nginx are being issued via the new still valid let’sencrypt root CA.

Thanks.

---

<div class="post-metadata">

**Author:** ![BlackDex](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/blackdex/32/8_2.png) [@BlackDex](https://vaultwarden.discourse.group/u/BlackDex)\
**Post date:** [October 12, 2021, 9:46pm UTC](https://vaultwarden.discourse.group/t/diagnosing-ssl-errors-with-sending-emails/1188/2 "2021-10-12T21:46:35Z")

</div>

If the cert still uses the DST root cert, then it could be causing this issue.

You could use a linux CLI tool like [GitHub - drwetter/testssl.sh: Testing TLS/SSL encryption anywhere on any port](https://github.com/drwetter/testssl.sh)

Or use this site [SSL Checker](https://www.sslshopper.com/ssl-checker.html) which support port numbers.