Installation via proxy about appium-chromedriver HOT 5 CLOSED

What is the output of

npm config get proxy
npm config get https-proxy

from appium-chromedriver.

I have the same problem behind our corporate firewall. Regular npm install works fine, but downloading the chromedriver from chromedriver.storage.googleapis.com fails.

I have tried setting the proxy via
npm config set proxy http://proxy.company.lan:3128
npm config set https-proxy http://proxy.company.lan:3128

or with the install command
npm install appium-chromedriver https-proxy=http://proxy.company.lan:3128 --proxy=http://proxy.company.lan:3128

and in the ~/.npmrc, but nothing works, still get the same error:

info Chromedriver Install Installing Chromedriver version '2.21' for platform 'linux' and architecture '64'
info Chromedriver Install Opening temp file to write chromedriver_linux64 to...
info Chromedriver Install Downloading http://chromedriver.storage.googleapis.com/2.21/chromedriver_linux64.zip...
RequestError: Error: getaddrinfo ENOTFOUND chromedriver.storage.googleapis.com chromedriver.storage.googleapis.com:80
at new RequestError (/home/espenaf/node_modules/request-promise/lib/errors.js:11:15)
at Request.RP$callback as _callback
at self.callback (/home/espenaf/svn/node_modules/request/request.js:200:22)
at emitOne (events.js:77:13)
at Request.emit (events.js:169:7)
at Request.onRequestError (/home/espenaf/node_modules/request/request.js:831:8)
at emitOne (events.js:77:13)
at ClientRequest.emit (events.js:169:7)
at Socket.socketErrorListener (_http_client.js:258:9)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at connectErrorNT (net.js:998:8)
at nextTickCallbackWith2Args (node.js:441:9)
at process._tickCallback (node.js:355:17)
npm ERR! Linux 4.4.0-21-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/local/bin/npm" "install" "appium-chromedriver"
npm ERR! node v4.2.6
npm ERR! npm v3.8.7

from appium-chromedriver.

I'm facing the same issue. Any ideas? npm install -g appium under corp proxy fails chromedriver downloading.

from appium-chromedriver.

I have looked into the code and found that the request-premise library the project used will use proxy only if there is an explicit declared in the code or there is a environment system variable in the os. I have added these 2 env vars as following and it resolves the issue.
http_proxy
https_proxy
Moreover, I've noticed that the library doesn't take proxy and https-proxy set in npm config into account.

from appium-chromedriver.

Issue currently tracked under main appium repo.
appium/appium#7296

from appium-chromedriver.