Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[email] Error: 7036:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:c:\ws\deps\openssl\openssl\ssl\record\ssl3_record.c:332: #18291

Closed
ahmed-abess opened this issue May 11, 2022 · 3 comments
Labels
resolved: answered The issue contained a question which has been answered triaged: question The issue contains a question

Comments

@ahmed-abess
Copy link

ahmed-abess commented May 11, 2022

Hello
when i try to send reset password request with directus i get this message
[email] Error: 7036:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:c:\ws\deps\openssl\openssl\ssl\record\ssl3_record.c:332:
note: i use directus 9 under windows 11

@ahmed-abess ahmed-abess added the issue: question The issue was opened to ask a question label May 11, 2022
@mattcaswell mattcaswell added triaged: question The issue contains a question and removed issue: question The issue was opened to ask a question labels May 11, 2022
@mattcaswell
Copy link
Member

This can happen for a number of reasons. Ultimately they all come down to OpenSSL receiving a record from the peer that has an incorrect protocol version number in it. Most likely is that the peer has aborted the handshake early for some reason and sent an alert back and used a protocol version number different to what we were expecting. It can also sometimes occur if the peer starts sending something which isn't TLS, or if data has got corrupted somewhere. A wireshark trace of the handshake might indicate which of the above is the problem. You can also try and replicate the problem by connecting to the server using s_client which might give us more information.

@ahmed-abess
Copy link
Author

thx
i solve it , in fact it was a problem of EMAIL_SMTP_PORT , it was 465 not 587

@SonuAccel
Copy link

Error sending email: Error: connect ETIMEDOUT 40.99.71.210:465
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16) {
errno: -4039,
code: 'ESOCKET',
syscall: 'connect',
address: '40.99.71.210',
port: 465,
command: 'CONN'
} - previously i was using 567 it was giving the same error now i used 465 its throwing this error now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolved: answered The issue contained a question which has been answered triaged: question The issue contains a question
Projects
None yet
Development

No branches or pull requests

4 participants