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.
Related
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 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.
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?
GET, PUT, DELETE request work fine, but everytime i make a POST request I get an 500 status code. I have no idea where to start debuggin or what to look for. My api is depolyed on Microsoft Azure.
Any tips on what to look for or how to solve this issue would be much appriciated. I know a 500 status code, could be pretty much anything, but i find it really wierd that POST is the only request that dosn't work.
I have no idea where to start debuggin or what to look for. My api is depolyed on Microsoft Azure.
Please make sure your API application could run fine locally before you deploy it to Azure. Besides, http 500 error indicates the server encountered an unexpected condition, if you deploy your app to Azure app service, you could remote debugging web apps to troubleshoot the issue. If you publish it as cloud service Web role, you could try to use Azure compute emulator to debug your cloud service on a local machine.
Deploying botbuilder on azure is fine.
But when invoked from botframework I get the internal server error.
Log files show this error in the stack trace of application log.
builder.ChatConnector is not a constructor.
Anything to be done to solve this?
Redeoploying the application to a new azure site did the trick.