Unable to publish bot with error of 404 (it can't find something?) #9763
Comments
pra-navi
added
Needs-triage
|
i have tried both a windows app service and a linux app service as the hostname and the messaging endpoint of the azure bot and i get the same problem |
|
@pra-navi - I'll be taking a look at this and will let you know what I find. I probably won't have a response until next week, fyi. However, here are a few things you can try:
Let me know if any of these unblock you. |
|
@stevkan
|
|
@stevkan 2024-08-02T06:55:11.3463689Z [onTurnError] unhandled error DialogContextError: user.data is not a list or array. when i check the logs on my Web App portal > Log Stream, i get the above everytime I try to send a message. Not sure what is causing the error considering I am using the same files that work within the Bot Framework Composer. |
|
@stevkan |
|
When I restart the chat, it is supposed to send an Activity Greeting: server listening on port 8080 |
|
@stevkan what is the expected output that i should see on Log Stream (on verbose mode on Azure Web App portal) after 1) starting the web chat, 2) sending my first message |
|
not sure what I changed (i only added and then removed npm install from the configurations on azure portal) but now for every restart it creates, starts and stops a container then it just records no trace no matter what message i send (still no response from bot and not sure how to debug to find out what the bot is reading and if it is even calling the api that i have connected to it in the bot framework composer) 2024-08-02T12:50:25 Welcome, you are now connected to log-streaming service.Starting Log Tail -n 10 of existing logs ----/home/LogFiles/kudu/trace/appnamebo_kudu_0fe155a77e-6701f2b9-7095-4b82-b808-2123beb01e34.txt (https://appname.scm.germanywestcentral-01.azurewebsites.net/api/vfs/LogFiles/kudu/trace/appnamebo_kudu_0fe155a77e-6701f2b9-7095-4b82-b808-2123beb01e34.txt) (no matter what message i send) |
|
When I run the Availability & Performance on the Azure Bot: Process Full List - This shows the list of all the processes running in your Linux instances. No process data is found because your app has not spun up or has not been running during this time period. { |
|
@stevkan When I run the Availability & Performance on the Azure Bot: Process Full List
|
|
@pra-navi - Thank you for your patience. Unfortunately, I am having a system issue of my own that is preventing me from even attempting to repro this. I spent a good portion of last week attempting to fix it with no success. Because of this I will be transferring this issue to my colleague, @dmvtech, who will continue in assisting you. He has some ideas of his own that I'll let him speak to. In the meantime, thank you for all of your detailed posts above. I have a comment about this post of yours:
I know that in the service apps configuration it shows a drop down with a short list of available Node versions to choose from. However, you aren't actually restricted to only those versions. You can set the WEBSITE_NODE_DEFAULT_VERSION environment variable to any valid version you want. Don't quote me on this, but I believe the lowest it supports is 8 or 10. So, to test if changing the Node version to 14, simply enter That having been said, I know you are testing other deployment/publishing options in the hope of getting the bot to work. You may need to test the above under the different scenarios you have tried, should you go this route, in order to rule out what might be working and what isn't. |
|
Hi @pra-navi Can you please try publishing the bot from outside of Composer? There should be a zip file of the bot application in the folder that Composer created. You can use this zip with the AZ cli tool to deploy it to the App Service. Please see more info here: If that works, then we can revisit what may be happening in Composer. If that fails, then there is something wrong with either the zip file or the App Service (or something in the Azure system, account problem, etc). |
|
@dmvtech I actually published my bot through Github, so I got the zip file of my bot application and then pushed it onto github then on my azure web app i linked it to that github repo (I followed this: https://stackoverflow.com/a/77899558/19991670) |
|
@dmvtech Sorry for the trouble and thank you for your help but do you perhaps have any updates?? |
When you publish from Github, does the bot work/run at that point? Or does it still fail to run successfully? |
|
@dmvtech The bot is pushed to microsoft teams so I can view the bot there but I am not receiving any response from the bot. Not sure if it is reading or doing anything with my messages. Not sure where the workflow has stopped because the exact same logic works on the bot composer but now the microsoft teams bot does not respond. |
|
Hey @pra-navi, if you're experiencing issues deploying and running your bot on Azure, particularly with errors like "404 Not Found" or "bot not responding," you might want to check out the Recall.ai API. It’s a simple 3rd party API that lets you use meeting bots to get raw audio/video/metadata from meetings without you needing to spend months to build, scale and maintain these bots. Here are the API docs: https://docs.recall.ai |
|
@tedlatte I am confused, I do not want a bot for meetings (so I don't understand how Recall API is going to work), I want a bot to talk to with responses based on my messages to the bot. I have already implemented this logic on Bot Composer and it works within the Emulator and the Composer but it does not work when I have deployed it. It might be because the way I deployed it was unconventional but I have explain through this thread and the linked stackoverflow thread how I implemented it. I need some help to understand why my logic is not coming through on the deployment aspect and what went wrong, how to troubleshoot it, etc. Because right now in my Microsoft Teams, I am just getting silence no matter what I send to the bot (no error messages, nothing) - not even sure how to check the logs to see if the bot is receiving any messages on Azure side. |
|
Are you able to test it through Teams using tunneling to a local running bot? |
Describe the bug
I am trying to deploy my bot using 'Import Resources'.
When JSON of existing resources is:
{ "name": "abc", "environment": "dev", "tenantId": "abc", "hostname": "abc", "runtimeIdentifier": "win-x64", "resourceGroup": "abc", "botName": "abc", "subscriptionId": "abc", "region": "westeurope", "appServiceOperatingSystem": "linux", "scmHostDomain": "azurewebsites.net", "luisResource": "", "settings": { "applicationInsights": { "InstrumentationKey": "", "connectionString": "" }, "cosmosDb": { "cosmosDBEndpoint": "", "authKey": "", "databaseId": "", "containerId": "" }, "blobStorage": { "connectionString": "", "container": "" }, "luis": { "authoringKey": "", "authoringEndpoint": "", "endpointKey": "", "endpoint": "", "region": "" }, "qna": { "subscriptionKey": "", "endpoint": "" }, "MicrosoftAppId": "abc", "MicrosoftAppPassword": "abc" } }I get the following error message:
If i change scmHostDomain to 'scm.azurewebsites.net' or ''
then the error changes to:
Version
I am using v2.1.2. I did not code this I am just using the interface.
Browser
OS
Expected behavior
I just needed it to publish the bot, I have pressed publish and it gives me this error message
Screenshots
Given above
Additional context
I am using Windows but I have set up the Microsoft Azure to use linux. I have also set up Microsoft Azure to be nodejs because when i first created this bot on botframework composer i had two options of nodejs or .NET and i chose nodejs.
The text was updated successfully, but these errors were encountered: