OperationalError: connect ENETUNREACH 2606:4700:3031::6818:6e0a:443 - Local (:::0)

DNS & Network
#1

Hi, I have nodejs app on my centos7 server witch is a ipv4 server.
I am making http calls to another api server (Its not mine)
Sometimes in the logs I am getting this error OperationalError: connect ENETUNREACH 2606:4700:3031::6818:6e0a:443 - Local (:::0)

This ip 2606:4700:3031::6818:6e0a is owned by clouadflare. So what can I do to fix this? shouldn’t cloadflare take care of this automatically? Or is the target site is setup to be used as ipv6 only??

#2

It appears you are trying to connect to IPv6 addresses, which will obviously fail if you dont have IPv6 configured.

You need to change your code, respectively resolution logic, here.

#3

I am connecting to a url not directly to an IP address, and this is the cloudflare’s ip not my destination IP

https://call2.tgju.org/ajax.json
this is the url that I am trying to call, and this does not happen all the time , just sometimes !!!

#4

And there obviously is an IP address behind a URL. The hostname you mentioned resolves that very IP address. As I said you need to make sure you are not connecting via IPv6, if your system doesnt support it. However that is not exactly a Cloudflare issue.

#5 
 ping call2.tgju.org
PING call2.tgju.org (104.24.110.10) 56(84) bytes of data.
64 bytes from 104.24.110.10 (104.24.110.10): icmp_seq=1 ttl=57 time=1.37 ms
64 bytes from 104.24.110.10 (104.24.110.10): icmp_seq=2 ttl=57 time=1.25 ms
64 bytes from 104.24.110.10 (104.24.110.10): icmp_seq=3 ttl=57 time=1.19 ms
64 bytes from 104.24.110.10 (104.24.110.10): icmp_seq=4 ttl=57 time=1.56 ms
^C
--- call2.tgju.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 5910ms
rtt min/avg/max/mdev = 1.195/1.345/1.562/0.140 ms
#6 
nslookup call2.tgju.org
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
Name:    call2.tgju.org
Addresses:  2606:4700:3031::6818:6e0a
	  2606:4700:3037::6818:6f0a
	  104.24.110.10
	  104.24.111.10

Plus, the error message already says it all.

#7

When you put your website behind cloadflare, you have to change the dns to cloadflare’s dns. That is what you are seeing !!! that is the cloadflare’s IP, nslookup is showing you the cloadflares IP not the destination IP

#8

Then connect to the actual IP address instead. I am not sure what your point is.

#9

I think I have found a solution, but have to test it …

#10

:zipper_mouth_face: :face_with_raised_eyebrow: :flushed:

#11

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