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

Error while testing the Action #460

Open
akash2908 opened this issue Mar 19, 2019 · 5 comments
Open

Error while testing the Action #460

akash2908 opened this issue Mar 19, 2019 · 5 comments

Comments

@akash2908
Copy link

Whenever I test my copy of Action it says " Dr. archive isn't responding right now. Try again soon. "(Dr. archive is an invocation to my Action).
" Failed to parse Dialogflow response into AppResponse because of empty speech response. " and this is the error shown in ERROR tab of the Action Simulator.

Screenshot from 2019-03-19 13-45-06

It gives " POST /internet-archive-f7795/us-central1/assistant 502 Bad Gateway " this error in the terminal while I test the Action on the simulator.

How can I resolve this problem?
Thank you

@alphadose
Copy link

Cross check if your server is running on port 5000 and also if the ngrok url in your local and the one in the dialogflow webhook is the same

@yagyanshbhatia
Copy link
Contributor

@akash2908 note that everytime you use ngrok it generates a new link where your server is exposed. You have to update the dialogflow fulfillment everytime as @alphadose mentioned.

@akash2908
Copy link
Author

Thank you @alphadose and @yagyanshbhatia, I have checked my server it is running on port 5000 and I update the webhook link every time I restart the server but still I am facing the same problem.

@akash2908
Copy link
Author

@alphadose and @yagyanshbhatia
Please help me out I am still facing the same problem.
I tried updating the link many a time but it didn't work for me.
I am attaching the screenshots for the same.

Screenshot from 2019-03-25 10-43-48

Screenshot from 2019-03-25 10-44-29

Screenshot from 2019-03-25 10-45-15

@yagyanshbhatia
Copy link
Contributor

@akash2908 I was running into similar problems when I started, here are some things I tried
use npm start with sudo flag. (in the function directory ofc)
for the initial 1-2 times, "talk to my test app" returns error in the simulator for me too, but works after that(weird).

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

3 participants