That is a shame, it looks like it is connecting and trying to send so it may not be an n8n issue. It is also possible that the request there is not from n8n when sending an invite email
For now I think the manual approach is going to be the way forward, I will check the internal ticket to see if there have been any updates.
As a temporary solution something like mailersend has a fairly good free tier that might get you by.
Thanks @Jon - I’ll keep nagging to see if we can get more info to pin this down.
For us, it is OK to work around as it only affects user invites. The Send Email node works fine.
Ultimately, our preference would probably be for shared access to administer all workflows so will keep an eye on potential future improvements to User Management (I see some comments on this across the forum).
A related issue I have found is when using Google’s SMTP Relay service like my company. Since the relay service is setup to authenticate via IP no username/password authentication is required. From my testing N8N requires values to be set for the username and password variables in order for the Invite button to work. However, since Google’s SMTP Relay can be used with username/password authentication the relay fails if I don’t enter valid info for the username/password. It would be nice if the Username and Password variables for the SMTP were marked as Optional instead of Required.
Hello @Jon,
I’m having the same issue as described.
I was able to send email on node “Send Email”. I used it to debug.
On that node I’m able to send the e-mail when i select the option: Ignore SSL Issues
Before I was getting the same issue on Send Email node and N8N SMTP configurations.
Do we have the same option as environment variables for SMTP setup, something like : “N8N_SMTP_IGNORESSLISSUES”?
For SMTP configurations I just have the host and port 25.
It works on Send Email node with “Ignore SSL Issues” option but not on on the environment variables. I don’t see Ignore SSL issues variable on documentation. Do we have something similar here?
We don’t have an option to ignore the SSL certs at the moment but… In 0.210.2 we have added an option to copy the invite link so it can be manually sent out.
It doesn’t solve the problem but maybe this will help.