I have deployed a bot on Azure and its deployed to the web channel. I am using it through a website. It was also working through the web link a few hours back and now it does not. I didn't change the code or any settings in the services.
I am using node.js code and QnA maker services. Individual services are up and running.
Can someone help me what shall I tweak to access the bot from the web link again?
Thanks,
Vivek Jain
Related
I am building a Teams App which uses a search based messaging extension. As far as I understand, I need a bot for this, because the bot is basically posting the adaptive card created from the data on my external webapp to the chat.
Is it possible to create or host a bot somewhere else than in Azure? I do not have an Azure subscription. If so, how would I go about using a different Bot for my Teams App?
Thanks for helping in advance!
Teams bots rely on the underlying Microsoft Bot Framework - the same engine for building any kinds of bots in the Microsoft ecosystem (e.g. slack or web or facebook bots). The only way to register those bots in MS Bot Framework is, yes, via the Azure portal. However, you don't need to HOST your bot in Azure - the physical web endpoint can live anywhere that's publicly httpS addressable (e.g. AWS), as long as the registration for the bot is in Azure.
yes, you can create the Bot framework locally and run it using Visual Studio.
To debug Bot locally in teams you need to use a tunneling service like ngrok.
To install ngrok run the following command.
ngrok http <port> -host-header=localhost:<port>
Here is document related Bot framework running locally and the installation steps for ngrok.
I am trying to load my QnA maker in addition to my QnA chat bot from Azure into Bot Framework Emulator.
I have been able to load my chat bot in successfully with it returning a response. I have entered the knowledge base data it required inside the Azure chat bot settings as well and the Visual Studio code (C#). But when I enter text into the chat bot inside of the bot framework emulator it replies with: Please set QnAKnowledgebaseId, QnAAuthKey and QnAEndpointHostName (if applicable) in App Settings. Learn how to get them at https://aka.ms/qnaabssetup.
Screen shot of what is displayed when I make contact with my chatbot inside of the bot framework emulator
Any help with resolving this issue would be greatly appreciated!
QnA Maker is generally available from May 2018. New architecture is built on Azure, where the runtime is now deployed on Azure App.
Now, if you are using new QnA Maker GA, it requires three parameters to get connect with Azure Bot Web App Bot. KnowledgebaseID, AuthKey & Host Name.
Host name is nothing but Web App URL deployed whiled creating QnA Maker service,
appname.azurewebsites.net/qnamaker
You have to provide this in Application Settings in Azure portal or alternatively in Constructor code part.
Thanks!
I just created web app bot manually in azure and its working fine. I need to create web app bot programmatically using node.js. Please suggest any idea. Thanks in advance.
Programmatic bot creation is not an option right now, but this is a high priority for the Bot Framework team and will be available soon. Please watch the Bot Framework blog for announcements. http://blog.botframework.com
I am working on Microsoft Bot Framework, I am created the bot through Azure Bot Service in Azure Portal. When I am running my bot application in local emulator its working fine after that published into Azure Bot service.
Here my issue is whenever to test my application in in Azure Portal at Test In Web Chat option the test window will showing like this below.
Added the same bot to Skype channel there also I am not getting any response.
How can I resolve the problem?
Please check your MicrosoftAppID and MicrosoftAppPassword are correctly mentioned in both your BotApplication as well as in Azure Bot Service. Also do check if the same is deployed properly and the MessagingEndpoint is correctly mentioned.
If this was just an issue with the channel your Test in WebChat could have worked properly.
From my experience, it is happen to me with the same situation. I think you select publish as Website. You should select publish as Deployment Script.
I have a bot that I've created by merging LUIS and QnA together in a single project using Microsoft Bot Builder.
I published the bot to an EC2 instance from visual studio and I'm using the Bot Framework Emulator for testing and it works perfectly. (MUST use ngrok for tunneling).
Now I want to deploy the bot on Skype. I logged into the Bot Framework Portal and I registered my bot. Now comes the configuration part.
I'm not quite sure what to set as the HTTP endpoint here.
I found this in the Bot Framework documentation:
Complete the Configuration section of the form.
Provide your bot's HTTPS messaging endpoint. This is the endpoint
where your bot will receive HTTP POST messages from Bot Connector. If
you built your bot by using the Bot Builder SDK, the endpoint should
end with /api/messages.
If you have already deployed your bot to the cloud, specify the endpoint generated from that deployment.
If you have not yet deployed your bot to the cloud, leave the endpoint blank for now. You will return to the Bot Framework Portal
later and specify the endpoint after you've deployed your bot.
When I published from Visual Studio, from the Azure App Service Activity windows, I found this line:
Start Web Deploy Publish the Application/package to https://ec2-00-000-000-00.compute-1.amazonaws.com:PORT/msdeploy.axd?site=bots ...
I used that address for the Messaging Endpoint in the configuration and I published my app. However when I'm testing it on Skype, i'm not receiving any messages from the bot.
I don't know what the problem is exactly, does this have something to do with ngrok? Or am I missing a step here, is there something else I should be doing to deploy the bot on Skype? Maybe something to do with the appid/password that I need to use ... i really don't know
Would really appreciate an explanation of how this works exactly. I don't really understand how the whole deployment procedure works exactly, feels like i'm swimming in murky waters.
Your endpoint is going to be the root of your deployed web application instance, plus the route that your bot is listening on.
For example, one of my bots is deployed to the free version of Azure Web Sites. The URL for a site such as this is https://APPLICATION_NAME.azurewebsites.net and the route that the bot listens on is the default /api/messages. This makes the endpoint https://APPLICATION_NAME.azurewebsites.net/api/messages.
If you connect directly to your app's endpoint, you should at least get a JSON dump with an error message. To make sure your site is getting deployed, drop an HTML file into the root of EC2 and see if you can access this.