How to resolve request to https://localhost:3978/api/messages failed, reason: net::ERR_SSL_PROTOCOL_ERROR in bot emulator?
net::ERR_SSL_PROTOCOL_ERROR in bot emulator
As I suggested in comment, to connect a bot running on local host, you can specify message endpoint in the emulator with http://localhost:3978/api/messages.
Besides, if you build your bot application using Bot Builder SDK for .NET in Visual Studio, to enable SSL and access site via https, you can set SSL Enabled option to True in project Properties window.
Test result:
Related
I create a new Teams application in Visual Studio 2022 (17.4.4). When I try the "Prepare Teams App Dependencies", I get a failure from AppStudioPlugin with the message "API call to Developer Portal failed: Error, connect EACCES 52.113.194.132:443, API name: create-app, ..."
I am behind a proxy, and I see a drop in the firewall logs to 52.113.194.132:443, so it's not going to the proxy.
When I open a browser on that machine, I can go to the developer portal (https://dev.teams.microsoft.com/) without a problem, so the proxy does allow this.
When I open port 443 in the firewall, everything works.
My question is: How do I get it to work via the proxy ?
I did already try to add the proxy to the visual studio config, but also that did not make a difference.
17.4 VS Teams Toolkit uses a language server to handle data between VS and Teams Dev portal. You can try to add this language server to your proxy and test it.
Language server location: ~\appdata\local\microsoft\visualstudio\{VS_version}\extensions\Microsoft\teams toolkit\{Teams_toolkit_version}\server.exe
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.
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?
I have hosted a simple BOT Chat on my IIS server, with URL being http://localhost:3978. But when i access http://localhost/3978/api/messages. It throws error "HTTP Error 404.0 - Not Found". so when i am giving these as my end point in emulator , it s unable to connect and same message is displayed. Please anyone can help me on this
You can't conect because you need conect to http://localhost:3978/api/messages not http://localhost/3978/api/messages, if is failed and you are deploy in a IIS server, conect to http://localhost/api/messages
If you're hosting in IIS you want to enter either
http://localhost/api/messages OR http://localhost/YourIISAppName/api/messages in the bot emulator. You can only use http://localhost:3879/api/messages if your code is running in visual studio and is set to run on PORT 3879 (which you can change in the properties of your bot application in VS). Also, make sure IIS is configured to accept POST requests.