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

Usage behind a proxy #18

Open
polhedel opened this issue Apr 20, 2016 · 14 comments
Open

Usage behind a proxy #18

polhedel opened this issue Apr 20, 2016 · 14 comments

Comments

@polhedel
Copy link

polhedel commented Apr 20, 2016

I don't get the quickstart to work. Could it be because I'm working behind a proxy? How to configure it?

Thank you very much!

@ar7hur
Copy link

ar7hur commented Apr 20, 2016

Can you please provide more details about your issue? At which step are you blocked?

@polhedel
Copy link
Author

I'm trying to make the quickstart.js work and I don't get any answer, I
just get the ETIMEDOUT error. I'm working with nodejs, I've installed your
module from github

2016-04-20 16:45 GMT+02:00 Alex Lebrun notifications@github.com:

Can you please provide more details about your issue? At which step are
you blocked?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#18 (comment)

@patapizza
Copy link
Member

Can you show the full output of the error?

@obinsc
Copy link

obinsc commented Apr 22, 2016

when i run messenger.js i get error "404 not found"

i checked template.js runs fine. Also i tested messenger webhook through other app that works fine.

@polhedel
Copy link
Author

The quickstart.js works fine when I'm not executing it behind a proxy, but when I run it behind the proxy I don't get any response just:
[error] [converse] Error:Error: connect ETIMEDOUT :
[error] Error: connect ETIMEDOUT :

Do I need to send some information about the proxy when creating the client?

Thanks?

@robinj
Copy link

robinj commented Apr 26, 2016

This is most likely a problem with your proxy setup. Which platform (win/mac/linux) are you using?

@polhedel
Copy link
Author

windows 7

2016-04-26 15:39 GMT+02:00 Robin Janssens notifications@github.com:

This is most likely a problem with your proxy setup. Which platform
(win/mac/linux) are you using?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#18 (comment)

@fishyimm
Copy link

i trying to run quickstart.js and i think it's got block from proxy, How do i get through proxy .

here is the error message :

[error] [converse] Error: FetchError: request to https://api.wit.ai/converse?ses
sion_id=2bc3a4e0-0de6-11e6-9c00-b3ed41493d31&q=what's%20the%20weather%3F failed,
reason: getaddrinfo ENOTFOUND api.wit.ai api.wit.ai:443
[error] FetchError: request to https://api.wit.ai/converse?session_id=2bc3a4e0-0
de6-11e6-9c00-b3ed41493d31&q=what's%20the%20weather%3F failed, reason: getaddrin
fo ENOTFOUND api.wit.ai api.wit.ai:443

thank you

@sicter
Copy link

sicter commented Jun 8, 2016

+1, in China working behind a proxy seems to be the same issue

EDIT: Considering I also cannot access: https://api.wit.ai/github_authorize_url in browser to log in on the website. It seems that all requests to api.wit.ai are blocked when using a proxy. In which case this issue is probably not specific to node-wit

@patapizza
Copy link
Member

It looks like node-fetch doesn't handle proxies out of the box.
@muddydixon is working on it: #39

In the meantime, can you try pulling his fork and confirm it solves your issue?

@rlogiacco
Copy link

Apologies to revive this, but has this been solved in another way or are we still waiting for this fix to be pushed into the master repo?

@polhedel
Copy link
Author

polhedel commented May 25, 2018 via email

@rlogiacco
Copy link

Argh.... I'm not able to find a solution... If anybody has it, I believe it would be great if it gets added here for future reference.
Currently scanning the source code to check if I get any hint

@patapizza
Copy link
Member

I'll surface this back with the team to see if we can prioritize it.

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

8 participants