node-wit
node-wit copied to clipboard
Usage behind a proxy
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!
Can you please provide more details about your issue? At which step are you blocked?
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 [email protected]:
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 https://github.com/wit-ai/node-wit/issues/18#issuecomment-212454267
Can you show the full output of the error?
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.
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
Do I need to send some information about the proxy when creating the client?
Thanks?
This is most likely a problem with your proxy setup. Which platform (win/mac/linux) are you using?
windows 7
2016-04-26 15:39 GMT+02:00 Robin Janssens [email protected]:
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 https://github.com/wit-ai/node-wit/issues/18#issuecomment-214747783
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
+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
It looks like node-fetch
doesn't handle proxies out of the box.
@muddydixon is working on it: https://github.com/wit-ai/node-wit/pull/39
In the meantime, can you try pulling his fork and confirm it solves your issue?
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?
Yes, don’t remember exactly how but it was solved long ago.
El dv, 25 maig 2018 a les 10:29 Roberto Lo Giacco [email protected] va escriure:
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?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/wit-ai/node-wit/issues/18#issuecomment-391981239, or mute the thread https://github.com/notifications/unsubscribe-auth/ARdWewARDcSuJs1LZtm2sUGyTJ6myuhgks5t18DRgaJpZM4ILw31 .
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
I'll surface this back with the team to see if we can prioritize it.