# IPv6 ENETUNREACH

**URL:** <https://discourse.nodered.org/t/ipv6-enetunreach/64716>\
**Category:** General\
**Tags:** http-request\
**Created:** [5 July 2022 12:29 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716 "2022-07-05T12:29:59Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![sahaine](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sahaine/32/64173_2.png) [@sahaine](https://discourse.nodered.org/u/sahaine)\
**Post date:** [5 July 2022 12:29 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/1 "2022-07-05T12:29:59Z")

</div>

We have a Node-Red install on Debian and 4G network which only support ipv6. Whenever making requests we receive an error;

RequestError: connect ENETUNREACH 142.250.200.4:80 - Local (0.0.0.0:0) : [http://www.google.com](http://www.google.com)

Any Ideas?

Thanks in advance

Steve

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [5 July 2022 12:58 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/2 "2022-07-05T12:58:51Z")

</div>

Exactly how are you making requests? How is the node doing the requests configured?

Is it a Docker install of node red or a normal install?

What happens if you run `ping6 www.google.com`

---

<div class="post-metadata">

**Author:** ![sahaine](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sahaine/32/64173_2.png) [@sahaine](https://discourse.nodered.org/u/sahaine)\
**Post date:** [5 July 2022 13:07 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/3 "2022-07-05T13:07:52Z")

</div>

Its a very simple flow that does a http get from google:

```auto
[{"id":"d29d5d42.9bda6","type":"inject","z":"75ccc5ad.1762bc","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":570,"y":360,"wires":[["c0c99e28.a39e5"]]},{"id":"c0c99e28.a39e5","type":"http request","z":"75ccc5ad.1762bc","name":"","method":"GET","ret":"txt","paytoqs":"ignore","url":"www.google.com","tls":"","persist":false,"proxy":"","authType":"","x":740,"y":360,"wires":[["cfccedbb.6082a"]]},{"id":"cfccedbb.6082a","type":"debug","z":"75ccc5ad.1762bc","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":910,"y":360,"wires":[]}]

```

The device is installed with Debian and Node-RED is not containerized.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/e/ceceed9cc598ebed3a98b7edc11a5414467577fe.png)

[Admin edit] Added triple backticks around flow to make it importable

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [5 July 2022 13:20 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/4 "2022-07-05T13:20:04Z")

</div>

OK, I think I will have to pass on this one then. I think it needs input from someone who knows more about the inner workings of node-red and nodejs.

---

<div class="post-metadata">

**Author:** ![sahaine](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sahaine/32/64173_2.png) [@sahaine](https://discourse.nodered.org/u/sahaine)\
**Post date:** [5 July 2022 13:21 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/5 "2022-07-05T13:21:21Z")

</div>

Ok Colin, Thanks for looking at it, to help more, here is the error object returned from the http request:

{"message":"Error: connect ENETUNREACH 216.58.212.228:80 - Local (0.0.0.0:0)","source":{"id":"c0c99e28.a39e5","type":"http request","count":1},"stack":"Error: connect ENETUNREACH 216.58.212.228:80 - Local (0.0.0.0:0)\n at internalConnect (net.js:882:16)\n at defaultTriggerAsyncIdScope (internal/async\_hooks.js:294:19)\n at GetAddrInfoReqWrap.emitLookup [as callback] (net.js:1029:9)\n at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:61:10)"}

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [5 July 2022 13:25 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/6 "2022-07-05T13:25:24Z")

</div>

What happens if you run  
`wget http://www.google.com`

---

<div class="post-metadata">

**Author:** ![sahaine](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sahaine/32/64173_2.png) [@sahaine](https://discourse.nodered.org/u/sahaine)\
**Post date:** [5 July 2022 13:26 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/7 "2022-07-05T13:26:42Z")

</div>

> [@Colin](#):
>
> wget [http://www.google.com](http://www.google.com)

It works outside Node-Red.....

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/1/51928fda88b22938432a988f811be0cbd837d173.png)

But as you can see it's using an IPv6 address which I think is where my problem lies?? I'm not sure the http request node is resolving the IPv6 address. I think it's resolving IPv4 which is unreachable on the network I have.

That's my guess anyway?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [5 July 2022 14:04 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/8 "2022-07-05T14:04:12Z")

</div>

I think you are probably right. Possibly something needs to be tweaked in the interface between node-red and the underlying nodejs modules that do the request.

Are you using the current release of node-red? Which version of nodejs?  
Use `node -v` to find the nodejs version.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [5 July 2022 14:16 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/9 "2022-07-05T14:16:33Z")

</div>

What happens if you request direct to the IPv6 address

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/1/a1213ad9df4fd9d2567c341cceed2535d02bd3e6.png)

I get this...

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/b/8/b82d9a2bbc885bbd6fef526ff4fa61f4cde6d1a8.png)

---

<div class="post-metadata">

**Author:** ![sahaine](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sahaine/32/64173_2.png) [@sahaine](https://discourse.nodered.org/u/sahaine)\
**Post date:** [5 July 2022 14:20 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/10 "2022-07-05T14:20:45Z")

</div>

> [@Colin](#):
>
> node -v

No, unfortunately, its part of a base image build provided by Siemens nodejs v10.23.1, I did try to upgrade but it caused some compatibility issues with some of the other flows and did not fix it. I will go down that route if we can prove it works but so far I have not been able to prove it works even with the latest version of nodejs and Node-Red.

---

<div class="post-metadata">

**Author:** ![sahaine](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sahaine/32/64173_2.png) [@sahaine](https://discourse.nodered.org/u/sahaine)\
**Post date:** [5 July 2022 14:21 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/11 "2022-07-05T14:21:36Z")

</div>

I think that you have specified an IPv4 Address there?

---

<div class="post-metadata">

**Author:** ![sahaine](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sahaine/32/64173_2.png) [@sahaine](https://discourse.nodered.org/u/sahaine)\
**Post date:** [5 July 2022 14:23 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/12 "2022-07-05T14:23:46Z")

</div>

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/b/ab0a3fd89c7cc69ad0ae709be58bfa2bf0701b23.png)

same result

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/f/5f58e2d86917ce20ebf539d0e24d7157ceccd41f.png)

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [5 July 2022 14:29 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/13 "2022-07-05T14:29:03Z")

</div>

I meant use googles IPV6

You can get that via `ping6 ipv6.google.com`

---

<div class="post-metadata">

**Author:** ![sahaine](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sahaine/32/64173_2.png) [@sahaine](https://discourse.nodered.org/u/sahaine)\
**Post date:** [5 July 2022 14:32 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/14 "2022-07-05T14:32:49Z")

</div>

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/9/5/95c56c56cfc234ec5124a7f6080a84ff1218bcc2.png)  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/c/3c3b1bfe9fab284505aa0829f1f493c801cf9340.png)

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/a/da0b00ed4c13cb9e2be6f2ca433a0e6f92f22ae1.png)

intrestingly mqtt woks via the ipv6 address

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [5 July 2022 14:33 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/15 "2022-07-05T14:33:58Z")

</div>

And what versions are you using?

> [@Colin](#):
>
> Are you using the current release of node-red? Which version of nodejs?  
> Use `node -v` to find the nodejs version.

EDIT

never mind - i see you are on a siemens device - cant help any further I'm afraid.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [5 July 2022 14:44 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/16 "2022-07-05T14:44:56Z")

</div>

> [@sahaine](#):
>
> nodejs v10.23.1

Are you able to perform a test on an up to date system on the network to prove that that is the problem?

---

<div class="post-metadata">

**Author:** ![sahaine](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sahaine/32/64173_2.png) [@sahaine](https://discourse.nodered.org/u/sahaine)\
**Post date:** [5 July 2022 15:34 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/17 "2022-07-05T15:34:00Z")

</div>

Ok so I've done the upgrade and it appears to now work 🙂 \> I've now got hours of trying to work out my compatibility issues.... thanks for the support Guys!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [19 July 2022 15:34 UTC](https://discourse.nodered.org/t/ipv6-enetunreach/64716/18 "2022-07-19T15:34:52Z")

</div>

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