Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connecting to CloudFlare API through corporate proxy #45

Open
cyberfox1 opened this issue Sep 4, 2019 · 2 comments
Open

Connecting to CloudFlare API through corporate proxy #45

cyberfox1 opened this issue Sep 4, 2019 · 2 comments

Comments

@cyberfox1
Copy link

I have set all the usual HTTP_PROXY etc but it does not work. Is there a way?

@cyberfox1
Copy link
Author

` Serverless: Packaging service...
Serverless: Excluding development dependencies...

Fetch Error --------------------------------------------

FetchError: request to https://api.cloudflare.com/client/v4/zones/c00f33815cde7500057aa26ef52c7a3b/workers/settings failed, reason: getaddrinfo ENOTFOUND api.cloudflare.com api.cloudflare.com:443
at ClientRequest. (/home/mnt/mapot/dev/repos/squirrel.git/node_modules/cloudflare-workers-toolkit/node_modules/node-fetch/lib/index.js:1455:11)
at emitOne (events.js:116:13)
at ClientRequest.emit (events.js:211:7)
at TLSSocket.socketErrorListener (_http_client.js:387:9)
at emitOne (events.js:116:13)
at TLSSocket.emit (events.js:211:7)
at emitErrorNT (internal/streams/destroy.js:64:8)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickDomainCallback (internal/process/next_tick.js:218:9)
`

@cyberfox1
Copy link
Author

Seems this module is not making proper use of node-fetch:

fetch('https://www.google.com',{ agent:new HttpsProxyAgent('http://127.0.0.1:8580')}).then(function(res){
...
})

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant