Proxy enabled?

[jenavarro]

I am getting different errors upon tool usage, depending on if I am connected through a proxy or not.

a. When connecting directly to internet I get this error 100% of the time:
[Error: Extraction error, err = tunneling socket could not be established, cause=getaddrinfo ENOTFOUND]

b. When connecting through a proxy I get this error 100% of the time:
[Error: Extraction error, err = OAuth error; err = connect ETIMEDOUT]

[rayshan]

Hi,

a. I'm not sure about this, we use it daily connecting directly and it works well. I googled tunneling socket could not be established, cause=getaddrinfo ENOTFOUND and it appears that this error is still related to proxy. Can you ensure you're absolutely not behind a proxy? Maybe try a different machine, or a VM on Digital Ocean.

b. There's currently no proxy support, however it's available: googleapis/google-api-nodejs-client#64. I'll add this in the next release.

[jenavarro]

You are right. even though I was disconnected from the corporate network, and IE, Chrome and FF did connect fine without attempting connecting to the proxy, node was still detecting the https_proxy environment variable and attempting to connect through the proxy.
Do you know if there is a workaround I could use until this enhancement is in place?
Thanks a lot for taking time for this, this tool is excellent!

[rayshan]

You're welcome. Just released 0.3, can you give it a try? I don't have a good way of testing proxy support, just passing it on to googleapis.

[jenavarro]

Wow, this was fast! thanks again for the quick turnaround on this request.
I tried 0.3, and sadly sofar I cannot make it work. I get this every time:
[Error: Extraction error, err = OAuth error; err = undefined]

I tried the following scenarios (after upgrading to 0.3):
a. with no proxy parameter in options (as in 0.2)
b. adding a valid proxy (e.g. proxy: 'http://server:port')
c. adding an invalid proxy (e.g. proxy: 'http://blablabla' )

I will continue testing since I am now connected through a VPN to the corporate network. thanks!

[rayshan]

a. is what we always use and integration tests pass as you can see: https://travis-ci.org/rayshan/ga-extractor
b. do you know of a free proxy I can use to help you test?
c. tests fail with Error: Extraction error, err = tunneling socket could not be established, cause=getaddrinfo ENOTFOUND

Another way for you to test is to try https://github.com/google/google-api-nodejs-client directly, I'm not doing anything besides passing the proxy string, if it's failing it may be an issue with that module.

[jenavarro]

I still see this behavior, 100% of the times I get the error mentioned above.
Don't know how you could replicate the proxy scenario, e.g. you could use this library to create a standalone proxy with a few lines of code (havn't tried it): https://github.com/nodejitsu/node-http-proxy

Also, one interesting piece of information is: when I am not using a proxy, pointing to an invalid .pem file or providing an incorrect proxy, I will get the "file not found" error, or the ENOTFOUND error respectively, which are correct.

But repeating the same scenarios from a network behind a proxy, I never get those two errors, it always fail with same "[Error: Extraction error, err = OAuth error; err = undefined]" messaeg, maybe it fails before reaching the validation for .pem or proxy exists. I will keep researching