Secure SMTP notification triggers SSL error #77

New issue

Closed

opened 2026-02-28 01:33:58 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 01:33:58 -05:00

Owner

Originally created by @ctrlbrk42 on GitHub (Aug 2, 2021).

Describe the bug
Error after setting up secure SMTP notification:

0|uptime-k | ] {
0|uptime-k |   library: 'SSL routines',
0|uptime-k |   function: 'ssl3_get_record',
0|uptime-k |   reason: 'wrong version number',
0|uptime-k |   code: 'ESOCKET',
0|uptime-k |   command: 'CONN'
0|uptime-k | }
0|uptime-k | [Error: 140492299540416:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
0|uptime-k | ] {
0|uptime-k |   library: 'SSL routines',
0|uptime-k |   function: 'ssl3_get_record',
0|uptime-k |   reason: 'wrong version number',
0|uptime-k |   code: 'ESOCKET',
0|uptime-k |   command: 'CONN'
0|uptime-k | }

To Reproduce
Steps to reproduce the behavior:

Add new SMTP notification
Using port 587
Checked "secure" option
Click "test"

Uptime Kuma Version: 1.0.7
Using Docker?: No
OS: Debian 11 bullseye

11:19 PM [kuma]~ root # npm -v
7.20.3
11:19 PM [kuma]~ root # pm2 -v
5.1.0
11:19 PM [kuma]~ root # node -v
v16.6.0

Originally created by @ctrlbrk42 on GitHub (Aug 2, 2021). **Describe the bug** Error after setting up secure SMTP notification: ``` 0|uptime-k | ] { 0|uptime-k | library: 'SSL routines', 0|uptime-k | function: 'ssl3_get_record', 0|uptime-k | reason: 'wrong version number', 0|uptime-k | code: 'ESOCKET', 0|uptime-k | command: 'CONN' 0|uptime-k | } 0|uptime-k | [Error: 140492299540416:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332: 0|uptime-k | ] { 0|uptime-k | library: 'SSL routines', 0|uptime-k | function: 'ssl3_get_record', 0|uptime-k | reason: 'wrong version number', 0|uptime-k | code: 'ESOCKET', 0|uptime-k | command: 'CONN' 0|uptime-k | } ``` **To Reproduce** Steps to reproduce the behavior: 1. Add new SMTP notification 2. Using port 587 3. Checked "secure" option 4. Click "test" - Uptime Kuma Version: 1.0.7 - Using Docker?: No - OS: Debian 11 bullseye ``` 11:19 PM [kuma]~ root # npm -v 7.20.3 11:19 PM [kuma]~ root # pm2 -v 5.1.0 11:19 PM [kuma]~ root # node -v v16.6.0 ``` ![image](https://user-images.githubusercontent.com/1001097/127803706-410823ad-13f6-4300-b305-c39a3e276fcb.png)

deekerman

2026-02-28 01:33:58 -05:00

closed this issue
added the
bug
label

deekerman commented

2026-02-28 01:34:05 -05:00

Author

Owner

@louislam commented on GitHub (Aug 2, 2021):

According to Nodemailer's suggestion, you should uncheck the "Secure" for 587 port.

https://stackoverflow.com/questions/66317125/node-js-nodemailer-error-wrong-version-number-invalid-greeting

@louislam commented on GitHub (Aug 2, 2021): According to Nodemailer's suggestion, you should uncheck the "Secure" for 587 port. Related issue: https://github.com/nodemailer/nodemailer/issues/165 https://stackoverflow.com/questions/66317125/node-js-nodemailer-error-wrong-version-number-invalid-greeting

deekerman commented

2026-02-28 01:34:05 -05:00

Author

Owner

@ctrlbrk42 commented on GitHub (Aug 2, 2021):

Thanks @louislam, I can confirm that did the trick. I do assume it's using TLS automatically w/o "secure" being checked, because my SMTP server requires it and the Test worked.

@ctrlbrk42 commented on GitHub (Aug 2, 2021): Thanks @louislam, I can confirm that did the trick. I do assume it's using TLS automatically w/o "secure" being checked, because my SMTP server requires it and the Test worked.

deekerman referenced this issue

2026-02-28 03:01:34 -05:00

Looping Crash After Deleting Monitor #2627