Error in sending email from web application with node js

[Moreno]

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: ghisellinimorenogm.it sanfrainfesta,ghisellinimorenogm.it api.ghisellinimoreno.it

I ran this command: I tried to send an email from the web application.
I use nodejs version 22.14.0
Until recently port 465 was enabled for smtpe and it worked while now I use 587 and it gave me this error

It produced this output:

*of MySQL2, an error will be thrown if you pass an invalid configuration option to a Connection*
*0|Sif      | [Error: 8088FD79BD790000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:354:*
*0|Sif      | ] {*
*0|Sif      |   library: 'SSL routines',*
*0|Sif      |   reason: 'wrong version number',*
*0|Sif      |   code: 'ESOCKET',*
*0|Sif      |   command: 'CONN'*
*0|Sif      | }*
*0|Sif      | [Error: 8088FD79BD790000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:354:*
*0|Sif      | ] {*
*0|Sif      |   library: 'SSL routines',*
*0|Sif      |   reason: 'wrong version number',*
*0|Sif      |   code: 'ESOCKET',*
*0|Sif      |   command: 'CONN'*
*0|Sif      | }*

My web server is (include version): I created a VPS with ubuntu 22.04 on AWS

The operating system my web server runs on is (include version): ubuntu 22.04

My hosting provider, if applicable, is: AWS

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): I connect via ssh using Putty

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): I don't know how to get the certbot version

I apologize if I made any mistakes in filling it out. I don't know English and I use google translator.
I'm completely stuck.
I have to test the application for the non-profit organization I work with.
thanks.

Moreno

[Osiris]

I'm sorry, but how is this Let's Encrypt related?

Please note that this is not a generic community where you can go to for generic computer problems. We mainly help with issues regarding Let's Encrypt certificates or sometimes other free ACME CA certificates, but not really TLS/SSL problems in general.

[Moreno]

thank you Osiris for your kind attention
Before writing to you I searched online for answers based on the error code that occurred and I found some posts that identified the error as failure to renew the let's encrypt certificate.
Can you help me check if the certificate has expired and if I can force the renewal manually to exclude that the error is due to this problem.
Until yesterday evening I was able to send emails without problems and for me finding this problem of failure to send was a really big surprise. Thank you for your interest and for what you do.
You don't know how much trouble I have managing these problems, since I'm quite new and I don't know who to turn to when the application has problems.
Thanks
Moreno

Sorry for the terrible way of expressing myself, but I have to rely on google translator since I don't know much English.

[MikeMcQ]

@Moreno

Can you help me check if the certificate has expired and if I can force the renewal manually to exclude that the error is due to this problem.

If you used Certbot to get your certificates you can see the latest it got with

sudo certbot certificates

The Certbot version is shown with: sudo certbot --version

The error you show is not because of an expired certificate. It looks like a port that is not configured properly for TLS communications.

You would be better off asking about that on a forum for the mail system running on port 587

[Moreno]

hello MikeMcQ

thank you for your courtesy and speed of response.
I checked the certificates and they are correctly in place and working.
In the screenshot the situation.
Thanks for the advice on the port for smtp.
In fact before, when I was able to print I used port 465.
Then they advised me to use port 587 and from there I had problems. I found some posts where they said that the port to use for smtp was 587 and so I made this change.
Do you know if 465 or 587 is recommended?
Always with "secure" set to "yes"
Thanks
Moreno

[Osiris]

@Moreno

Thanks for the advice on the port for smtp.
In fact before, when I was able to print I used port 465.
Then they advised me to use port 587 and from there I had problems. I found some posts where they said that the port to use for smtp was 587 and so I made this change.
Do you know if 465 or 587 is recommended?
Always with "secure" set to "yes"

I'm still not convinced it's a Let's Encrypt issue.

E.g., it looks like your outgoing connection isn't working, from your Node.js to something else. To which SMTP server are the connections going? I.e.., which hostname?

Further more, port 587 ("submission") uses STARTTLS for TLS and port 465 uses implicit TLS, i.e., without STARTTLS. That could be the problem here. But I have no clue how Node.js handles that, so best to ask such a thing on a Node support channel.