Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
WebSocket doesn't support
See original GitHub issueI am using .NET Core 3.1 and MQTTnet 3.0.8 and MQTTnet.AspCore 3.0.8 for my broker service. It’s works fine when a client connect with mqtt protocol from MQTT.fx or .NET client; but whenever a request come from browser using ws protocol its seems like this
My .NET broker configuration
startup.cs
program.cs
I saw this Issue 390 conversation but nothing found useful for me.
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (3 by maintainers)
Top Results From Across the Web
javascript - WebSocket not connecting
1 Answer 1 ... A websocket client requires a websocket server to connect to. While all webSocket connections do start with a plain...
Read more >Web Sockets | Can I use... Support tables for HTML5, CSS3 ...
"Can I use" provides up-to-date browser support tables for support of front-end web technologies on desktop and mobile web browsers.
Read more >WebSocket not working
I think using WebSocket in a browser will work, but a third-party client won't. My connect code is like this: const WebSocket =...
Read more >How to resolve unable to connect error? : Help Desk
This error message indicates that you are likely working behind a proxy that doesn't support the WebSocket protocol.
Read more >Troubleshooting connection issues
You are trying to reach a plain WebSocket server; The server is not reachable; The client is not compatible with the version of...
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
It works. Thanks man
USE PORT 5000