I have developed a bot that works perfectly on my local machine and accessible through all channels via ngrok.
However, the Bot doesn’t work on its deployed Azure url which is https://mybot.azurewebsites.com/api/messages A test with the webchat or bot emulator returns an error 500 without further information on exact cause of the issue. How would I debug so that I can find out more information on what's causing the breakdown?
Related
I have a bot, built using the Bot Framework V4 in Java with Spring Boot, that is hosted on an Azure Web App and using the Azure Bot Service.
When connecting with the Bot Framework Emulator using ngrok it works just fine but when I try to use the Web Chat channel in the bot service I get this error
There was an error sending this message to your bot: HTTP status code Unauthorized
When trying to open it in Teams using the Teams channel it also doesn't work.
I have left the MicrosoftAppId and MicrosoftAppPassword empty and have my messaging endpoint set as https://<name>.azurewebsites.net/api/messages.
Is there any way I can use web chat?
When testing with a locally running bot (with using local url), you don't need to specify MicrosoftAppId/MicrosoftAppPassword within Emulator. But when the bot is deployed to Azure (OR testing when running locally but through with ngrok), you need to configure them in either the Web App configuration or in the application.properties file.
I have developed a bot on node.js as a teams app using the yo teams generator. The bot is hosted and deployed on an azure app service web app. The bot was working fine all the while, but started throwing http 500 internal server errors in the past couple of weeks.
I am not sure what has changed, but I am trying to fix this issue but not finding any leads and useful information from appInsights or the trace logs. All I see is the below exception being thrown in appInsights:
"POST to the bot's endpoint failed with HTTP status 500"
The bot works perfectly fine locally, when debugging through ngrok. Please let me know how I can fix this or where I can look for useful logs to help resolve this.
I was able to resolve this with MS on a support ticket. Looks like the fix is to update the configuration setting to reflect the latest version of node from 12.13 to 16.13.0 in the app service config section.
We are facing issue in Azure chatbot, LUIS is not responding in Test in Web Chat on Azure. Chatbot is working fine Emulator and integration with direct line. My client is testing always from Azure so it is some critical issue for us. We are using Standard LUIS runtime subscription. It would be great if someone can help us. I did below trouble shooting steps.
Subscription key for standard plan and verify keys , it is correct.
Re-deployed
See application Insights error code is 400 only when i run it from Azure Test in Web Chat
I opened MS support ticket for this issue and find same issue was running at support team side as well. There were no code and configuration change after some time it suddenly start functioning.
Thanks
I am following this guide to develop chatbot:
https://learn.microsoft.com/en-us/azure/bot-service/bot-builder-howto-v4-luis?view=azure-bot-service-4.0&tabs=csharp#test-the-bot
When I tried to test the bot with Bot Framework Emulator, I am unable to get a response.
[15:17:43]Emulator listening on http://[::]:60595
[15:17:43]ngrok not configured (only needed when connecting to remotely hosted bots)
[15:17:43]Connecting to bots hosted remotely
[15:17:43]Edit ngrok settings
[15:17:43]-> conversationUpdate
[15:17:44]POST500directline/conversations/<conversationId>/activities
[15:17:51]-> messagehi
[15:17:51]POST500directline/conversations/<conversationId>/activities
Is this have to do with my company security blocking ngrok?
My Echo bot works fine, but seems like I am having issue with the LUIS function. Is there a way to make it work and link it to MS teams?
Help needed
I am using
Ver 4.1.0 Bot emulator
When I tried to use the production endpoint in the bot framework emulator. I have configured the endpoints in the bot file as below with information from the azure. But I am unable to the access it via the Emulator and also it does not connect in the "Test in Webchat" in Azure after deployment via Git to Azure. It works fine locally
It returns the following error
In the channels I see the following error triggered.
I analyzed the issue using Fiddler Trace. I think the tokens are being generated.
But the Emulator is not picking it. As seen in the below screenshot both of the fiddler and emulator refers to the same conversation ID.
what might be the issue that is triggering token failure?
I think the bot service is down at the moment.