-
-
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
SSL Error in production. #993
Comments
Just as a work-around, did you try it with "secure = false"? This prevents Nodemailer from forcing to open a TLS connection and it's using STARTTLS instead. I know that STARTTLS is less secure (man in the middle) - but maybe helps you to get it working until someone with more clue on Nodmailer can help you. |
The error message indicates that you are trying to open a TLS connection against cleartext port. If the same config works on local but not in production then most cases it is some kind of proxy configuration issue in your server. |
@andris9 you were right, I didn't check it firsthand, and was battling the issue where it shouldn't be. It was related to proxy on the server. Thanks! |
I get similar error. I'm sending invitation email to about 800 users who are porting from our old app to new app. Some emails are sent, whereas, for sending other emails, I get this error. { [Error: 139629565937472:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:331: ] code: 'ESOCKET', command: 'CONN' } I checked the email addresses. Several emails are sent successfully to gmail ids and several others fail for gmail. |
I am facing a similar issue.
Can someone guide me to fix this issue? |
Everything is working fine until I push it to production server.
Environment is the same:
NODE: v10.15.1
NODEMAILER: ^6.0.0
GMAIL: Oauth2
I get the error:
LOG:
I've tried almost all combinations of transporters I can think of and almost all of them work on local machine, BUT in production I get the result above... Below my "final one". Is there a way to to fix this issue?
The text was updated successfully, but these errors were encountered: