Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Direct Line App Service Extension Websocket error 500 #3627

Closed
chung-ting opened this issue Dec 7, 2020 · 4 comments
Closed

Direct Line App Service Extension Websocket error 500 #3627

chung-ting opened this issue Dec 7, 2020 · 4 comments
Assignees
Labels
Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete. question Further information is requested. Stack Overflow candidate
Milestone

Comments

@chung-ting
Copy link

Describe the bug

I implemented the Direct Line App Service Extension(Node.js version) according to the official website suggestion, but I encountered some problems during the implementation. (https://github.com/microsoft/BotFramework-WebChat/tree/master/samples/01.getting-started/i.protocol-direct-line-app-service-extension)

I successfully got the token, but encountered a websocket error when establishing a connection

Error message from Chrome[F12]:
webchat-minimal.js:2 WebSocket connection to 'wss://chatbot-nodejs-bot-channel.azurewebsites.net/.bot/v3/directline/conversations/connect?token=undefined' failed: Error during WebSocket handshake: Unexpected response code: 500

[Bug]

@chung-ting chung-ting added Bot Services Required for internal Azure reporting. Do not delete. Do not change color. bug Indicates an unexpected problem or an unintended behavior. customer-reported Required for internal Azure reporting. Do not delete. labels Dec 7, 2020
@corinagum corinagum added the support Internal request for assistance from the Support Team label Dec 7, 2020
@corinagum corinagum self-assigned this Dec 8, 2020
@corinagum
Copy link
Contributor

corinagum commented Dec 8, 2020

Issue was due to WebSockets being disabled in the bot's web.config with a slight hiccup afterwards due to 'always on' not being set on the bot, causing it to need a nudge to wake up.

Due to the above, I am changing this from Bug to Question.

  • Remove Support label / change to Question
  • Add this topic to FAQ
  • Mock Bot token feedback TBDiscussed here

@corinagum corinagum added question Further information is requested. Stack Overflow candidate customer-replied-to Required for internal reporting. Do not delete. and removed bug Indicates an unexpected problem or an unintended behavior. support Internal request for assistance from the Support Team labels Dec 8, 2020
@taicchoumsft
Copy link
Member

@corinagum any updates on this?

@corinagum corinagum added this to the R12 milestone Dec 18, 2020
@corinagum
Copy link
Contributor

@taicchoumsft thanks for the ping. I messaged the reporting developer via Teams for a response, since I can't seem to find his GitHub handle. Also added this to the R12 milestone so the action item doesn't fall through the cracks.

@corinagum
Copy link
Contributor

corinagum commented Dec 18, 2020

I spoke with @DDEfromOR, and all feedback is planned to be addressed in #2343. Closing this issue and adding to FAQ now.

@corinagum corinagum mentioned this issue Dec 18, 2020
37 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete. question Further information is requested. Stack Overflow candidate
Projects
None yet
Development

No branches or pull requests

3 participants