Upgrade to WebSocket is required.
See original GitHub issueDescribe the bug
Created a sample bot that works locally and then I deployed to newly crated resource. When browsing to the endpoint https://XXXXX.azurewebsites.net/api/messages e get “Upgrade to WebSocket is required.”
“Test in Web Chat” is also not working.
Similar issue to this one.
Version
Browser
- Electron distribution
- Chrome
- Safari
- Firefox
- Edge
OS
- macOS
- Windows
- Ubuntu
To Reproduce
Steps to reproduce the behavior:
- Go to ‘…’
- Click on ‘…’
- Scroll down to ‘…’
- See error
Expected behavior
Screenshots
Additional context
Issue Analytics
- State:
- Created 3 years ago
- Comments:12
Top Results From Across the Web
Web Bot does not work: Upgrade to WebSocket is required.
When I want to run Core Bot with Messaging Endpoint, I get the next message: Upgrade to WebSocket is required. It does not...
Read more >Protocol upgrade mechanism - HTTP - MDN Web Docs - Mozilla
Provides information to the server which is needed in order to confirm that the client is entitled to request an upgrade to WebSocket....
Read more >Upgrade to WebSocket is required. Error when browse to ...
I have created a LivePerson Bot for handoff as per sample code. It works fine when I run it locally from emulator but....
Read more >"Upgrade to WebSocket required" using the development ...
I'm trying to follow the documentation to write an API to GET some data from a table in Cassandra. I work on a...
Read more >How to "upgrade" an HTTP connection to a WebSocket
I'd like to be able to get the "updates" or "changes" part when I receive the new connection notification. Having more sample code...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ok, thanks for the follow up. Yeah, that would do it 😂
That’s really interesting though. If you are able to give specific steps on how to reproduce this issue (creating/provisioning with Composer, where it creates the wrong app registration), we would be interested in investigating further.
Gotcha. Ok, I’ll go ahead and close. If it reoccurs or you are able to determine the exact steps, please comment or open a new bug. Thanks!