-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Error: 7288:error:1408F10B:SSL routines:ssl3_get_record:wrong version #1074
Comments
You are either trying to use TLS on a non-TLS port or the openssl version you use is not compatible with the server. |
I have exactly the same issue. |
@funkenstrahlen I changed approach to use an email address from Gmail. |
Oh god I have the same problem, somebody help me! |
\ws\deps\openssl\openssl\ssl\record |
@renanbastos93 What you have changed? I am facing same issue |
I had used an email private example |
I was using business gmail, even though I changed to personal Gmail, Its not working for me. :( |
You need to change the permission of the email for can using |
@renanbastos93 Thanks for help. |
anytime, see ya |
i have exact same issue occuring when i'm using the nodemailer and send mail to mailtrap and then this issue is happening and even mail is not to send to mail trap...... |
Heys guys, do you have some update about this issue? I'm using Umbler (Brazilian hosting and email provider) as Email provider, for sending emails from my private, corp email from Nodemailer, and I'm getting this same error right now. EDIT: By using Outlook on PC, I'm able to receive and send emails, so I think it isn't a problem with the provider. |
I configured my transporter like this: export const transporter = nodemailer.createTransport({
host: Config.EMAIL_HOST,
port: Config.EMAIL_PORT,
auth: {
user: Config.EMAIL_USER,
pass: Config.EMAIL_PASSWORD,
},
secureConnection: false,
}); With that is working. |
Can you help me?
[Error: 7288:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:c:\ws\deps\openssl\openssl\ssl\record\ssl3_record.c:332:
] {
library: 'SSL routines',
function: 'ssl3_get_record',
reason: 'wrong version number',
code: 'ESOCKET',
command: 'CONN'
}
The text was updated successfully, but these errors were encountered: