The send email node stopped working on all my workflow, i didn’t change anything. It take very long time to process and then output a “Client network socket disconnected before secure TLS connection was established”. Error code: ESOCKET
Im using n8n with docker and a nginx reverse proxy.
I tried using with 3 email that are in ms exchange.
Tried with host like smtp.office365.com or outlook.office365.com
Using n8n Version 1.121.3, the email account are licensed, 2 factor auth exempted, all mail application authorized.
Do you have any idea of why is it not working here ?
It may be a nginx or a docker issue here but can’t figure out.
This looks like a TLS/network issue, not the email accounts. Since it’s affecting all workflows, it’s likely related to Docker networking or the Nginx reverse proxy (timeouts or blocked SMTP port 587). Also worth checking that the container can reach Office365 SMTP with STARTTLS enabled.
If you want, I can help you quickly diagnose and fix this just let me know.
From what i have figured out, i can reach office365 smtp w/ '“openssl s_client -connect smtp.office365.com:587 -starttls smtp” but when i try this on my docker container it doesn’t return me any certificate:
After that i tried the same command with “-tls1_2” option at the end and it returned me a certificate.
I added “- NODE_OPTIONS=–dns-result-order=ipv4first --tls-max-v1.2” in my docker compose file and it then worked in my workflow.
Still can’t understand why TLSv1.3 SMTP is not taken by my container. Hoping that TLS1.2 doesn’t break my others workflows
