vercel: Unable to deploy because of proxy

Hello, I am behind a Proxy, I can access npm registry by putting http_proxy and https_proxy environment variables, but I can’t deploy using now. It throws me the following error:

> now --token 123567778998876767

> Deploying ~\Desktop\scrapaor
> Error! Unexpected error. Please try later. (request to https://api.zeit.co/now/create failed, reason: getaddrinfo EAI_AGAIN api.zeit.co:443)

Is there a solution for this?

About this issue

  • Original URL
  • State: open
  • Created 7 years ago
  • Reactions: 17
  • Comments: 37 (9 by maintainers)

Commits related to this issue

Most upvoted comments

I’ve seen more and more very useful apps built without the ability to use a proxy lately.

Implementing this in nearly every language is a trivial affair.

This trend is disturbing.

I have same problem. 1 year, solve this issues please

Agreed, I think we should support the http_proxy /cc @leo

Bump. Nearly three and a half years and still no solution for this?

I wrote a module that wraps Now CLI to add proxy support: https://www.npmjs.com/package/proxify-now

Tested on WIN 10 64bit.

With that commit, is this issue now solved? It has been quite a while since there was any activity here.

just to pile on one more person who wants proxy support, here I am! Please implement proxy support. It’ll be three years soon, and you had a lot of time to do it right.

I really don’t get why this is not a priority for you, because many corporate users (= paying users) are behind a proxy and will probably use anything instead of Zeit. At least in my team’s case, we used a different service instead of Zeit because of this very issue.

i thing the best solution is global-tunnel-ng it works transparetly

@thiagoarrais npm has recently switched away from request in favor of make-fetch-happen, which also supports http_proxy.

@leo , I saw it was deployed v5.3.2 of now-cli. Still without luck trying to deploy behind a proxy. I have a Premium account and this feature is important to me. Do you have any plans to support proxy envs soon?

but why can I download packages from npm and even install meteor packages just by exporting http_proxy? I think proxy support is on your side. You can implement it right?