tunneling socket could not be established

[jamesmoriarty]

Just recording this for any lost souls.

Error: tunneling socket could not be established, cause=connect EINVAL 0.0.31.144:80 - Local (0.0.0.0:0)

The following might work for something like curl but doesn't for request/ tunnel-agent:

http_proxy=127.0.0.1:3128 curl http://google.com

You need to add the protocol:

http_proxy=http://127.0.0.1:3128 curl http://google.com

So in summary:

http_proxy=<host>:<port> would become http_proxy=<protocol>://<host>:<port>

[shawn-tangsc]

i have the same problem .!

[Zim-b7]

any luck in solving this issue?

[ParthPatwalaTA]

Solved error but here is one note for Ubuntu users.

This will only work in the current terminal. if you run following command and then use it other terminals then it won't work. This works for me so i'vent search for global access.

Steps:

$ env | grep -i proxy
$ export http_proxy=
$ export https_proxy=

After running these commands you will see this kind of output

https_proxy=
http_proxy=
socks_proxy=
ftp_proxy=

If you see this then you're good to go.

[CherryDT]

Got the same thing but with slightly different IP:

RequestError: Error: tunneling socket could not be established, cause=connect ECONNREFUSED 0.0.34.184:80

Recording this here for Google since I didn't find anything at first.

I think where this comes from is that, as @jamesmoriarty pointed out, it expects a protocol, and hence localhost:8888 (in my case - from Fiddler) is read as protocol localhost and IP 8888 is (due to the widely used, yet inofficial, way of parsing IP addresses since 4.2BSD inet_aton) read as 0.0.34.184 (since 34*256+184=8888).

[chenqping]

Error: tunneling socket could not be established, cause=connect EINVAL 0.0.31.144:80 - Local (0.0.0.0:0)

Just recording this for any lost souls.

http_proxy=<host>:<port> worked with curl. request / tunnel-agent requires the protocol.

So http_proxy=proxy-host:8080 became http_proxy=http://proxy-host:8080.

Good it worked for me!

[nsigel]

I think where this comes from is that, as @jamesmoriarty pointed out, it expects a protocol, and hence localhost:8888 (in my case - from Fiddler) is read as protocol localhost and IP 8888 is (due to the widely used, yet inofficial, way of parsing IP addresses since 4.2BSD inet_aton) read as 0.0.34.184 (since 34*256+184=8888).

@chenqping Would you mind elaborating a bit? I'm having this issue with trying to use fiddler and tunnel but I'm not sure if I understand what you mean

[CherryDT]

Include the protocol (http://).

[nsigel]

I'm still getting Error: tunneling socket could not be established, cause=connect ECONNREFUSED 127.0.0.1:80 when using

      httpsAgent: tunnel.httpsOverHttp({
        host: "http://127.0.0.1",
        port: 8888,
      }),
      proxy: false,

[CherryDT]

Remove the port and make it part of the host: `http://127.0.0.1:8888` [Sent from my mobile - please excuse typos]

…

________________________________ From: noah <notifications@github.com> Sent: Sunday, January 3, 2021 22:08 To: request/tunnel-agent Cc: David Trapp; Comment Subject: Re: [request/tunnel-agent] tunneling socket could not be established (#39) I'm still getting Error: tunneling socket could not be established, cause=connect ECONNREFUSED 127.0.0.1:80 when using httpsAgent: tunnel.httpsOverHttp({ host: "http://127.0.0.1", port: 8888, }), proxy: false, — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[chris-kt]

Error: tunneling socket could not be established, cause=connect EINVAL 0.0.31.144:80 - Local (0.0.0.0:0)

Just recording this for any lost souls.

http_proxy=<host>:<port> worked with curl. request / tunnel-agent requires the protocol.

So http_proxy=proxy-host:8080 became http_proxy=http://proxy-host:8080.

Bless you, kind sir

[wang1212]

It seems that the problem still exists when the protocol of the proxy address is socks5.