Error: connect ENETUNREACH on node-red-node-email

bakman2 · 14 October 2022 07:27

Could it be related to this ?

Allow internal network interfaces in host resolution

opened 12:46PM - 05 Jul 22 UTC

closed 12:14PM - 06 Jul 22 UTC

BACKGROUND: - sometimes, virtualized servers or environments, make use of com…mon network interfaces (i.e. FreeBSD jails), provided by the hosting system. - it is common, to use a cloned loopback interface of the parent system for relaying traffic in and out to the child systems - In those cases the child has an interface, that, if you are running node.js on that child and use `os.networkInterfaces()`, is is marked as "internal" (which is correct, but for the child its the only interface to the external world and as such is "external") - We need to have an option to tell nodemailer, that it can also make use of internal interfaces. IS - using nodemailer in the described setup, the following error is thrown: ``` Can not use IPv(4|6) addresses with current network => lib/shared/index.js, 210 ``` SHOULD - a configuration should allow to avoid testing, if os network interfaces are internal ```javascript const mailConfig = { pool: true, host: 'my.funyy.mailhost.com', secure: true, allowInternalNetworkInterfaces: true, auth: { user: process.env['SMTP_USER'], pass: process.env['SMTP_PWD'] }, } ``` - This option should then be considered in function `isFamilySupported(family)` in `lib/shared/index.js` ```javascript const isFamilySupported = family => { const familySupported = // crux that replaces Object.values(networkInterfaces) as Object.values is not supported in nodejs v6 Object.keys(networkInterfaces) .map(key => networkInterfaces[key]) // crux that replaces .flat() as it is not supported in older Node versions (v10 and older) .reduce((acc, val) => acc.concat(val), []) .filter(i => !i.internal) // this should optionally be not filtered .filter(i => i.family === 'IPv' + family || i.family === family).length > 0; return familySupported; };

Switchblade2 · 14 October 2022 11:49

It worked fine for 12 hours and then stop after an reboot (updated mosquito service)
I know have the (related?) "Error: Can not use IPv4 addresses with current network".

Update with Full error message:
Error: Can not use IPv4 addresses with current network at GetAddrInfoReqWrap.callback (/home/pi/.node-red/node_modules/node-red-node-email/node_modules/nodemailer/lib/shared/index.js:203:35) at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:132:8)

jbudd · 14 October 2022 11:54

I think it's the same problem.
What does node -v show?

Switchblade2 · 14 October 2022 12:02

I'm on v16.18.0

dceejay · 14 October 2022 12:41

I notice there are some "fixes" to the nodemailer lib package mentioning DNS... I have updated the email node to 1.18.0 to pull in the latest... Can someone see if that helps ?

jbudd · 14 October 2022 15:24

An update:

I found out how to roll back to nodejs 16.7.0

wget https://deb.nodesource.com/node_16.x/pool/main/n/nodejs/nodejs_16.17.0-deb-1nodesource1_arm64.deb
sudo apt install -f ./nodejs_16.17.0-deb-1nodesource1_arm64.deb

nodejs changed from 16.17.1 to 16.17.0 and the gmail problem disappeared.
However, today, reverting to 16.17.1 using either apt upgrade or the Node-red install script, the problem doesn't come back.
This is different to yesterday when I rolled back to nodejs14.
And I have repeated yesterday's test several times. The problem does not want to come back.

node-red-node-email is still 1.17.0

Switchblade2 · 15 October 2022 06:08

I managed to get it working by shifting from wifi to ethernet cable, and then back to wifi only as well as deactivating IPv6 from the GUI wifi icon. So far stable.

node-red-node-email is stilll on 1.17.0

Colin · 15 October 2022 06:21

It would be helpful if you could make it fail again and then upgrade the email node to see if that finally fixes it

jbudd · 15 October 2022 07:34

If only it was that simple!

mike7 · 21 October 2022 19:31

Hi, I'm totally new to this forum.
I've got the same problem as described and have updated the node. The problem still persists. I'm running v16.17.0

Switchblade2 · 25 October 2022 07:18

I was offline due to a cut fibre cable for 2 weeks (definitely blocks all emails).
When the internet connection was working again the mail node work for approx 1h sending several mails but then stopped with the "Error: Can not use IPv4 addresses with current network".

Upgrading node-red-node-email to 1.18.1 did not fix it.

I got it working again connecting via both wifi & ethernet cable, with IPv6 deactivated.
I'll try to run on only ethernet cable and see how that works ...

Colin · 16 December 2022 16:05

I get this quite regularly recently. It seems to be triggered by switching between wifi and wired ethernet, though I am not sure exactly what to do to make it happen. As far as I can see everything other than the email node continues as normal.
A node red restart fixes it. If anyone can suggest anything to look at to help diagnose exactly what is going on then I can try it next time it happens.

Standard install running on Ubuntu
Node red 3.0.2
nodejs 16.18.1
node-red-node-email 1.18.2

system · 14 February 2023 16:05

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Sending email : "Error can not use ipv4 addresses with current network" General	53	1958	29 April 2023
Email send-"Error: Connection timeout" General	6	694	5 September 2021
Node-red-node-email not sending email on double nat network General	9	461	17 October 2022
Email will not send General	3	2037	28 September 2020
I don't arrive to send an email with node email General	39	2829	1 September 2021

Error: connect ENETUNREACH on node-red-node-email

Related topics