-
Notifications
You must be signed in to change notification settings - Fork 484
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
Comments
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 2016-04-20 16:45 GMT+02:00 Alex Lebrun notifications@github.com:
|
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: 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 notifications@github.com:
|
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 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 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 <notifications@github.com>
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
<#18 (comment)>, 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. |
I'll surface this back with the team to see if we can prioritize it. |
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!
The text was updated successfully, but these errors were encountered: