Getting error WebSocket disconnected
See original GitHub issueHi,
I’m getting an error on startup; this is what I’m doing.
I configure the host to be “auto” in NiM:
I create a simple main.js
file, and then I run it using node --inspect-brk main.js
. NiM detects the URL and opens, but I get the following error:
OS & Versions: OS: Manjaro Linux Node: v14.4.0 NiM: 2.4.2 (as seen by the first screenshot)
Thank you
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Getting the reason why websockets closed with close code 1006
Close Code 1006 is a special code that means the connection was closed abnormally (locally) by the browser implementation.
Read more >WebSocket Disconnects - PTC Support
WebSocket disconnects can happen by choice, or due to exceptional/error conditions. Here is some information about what happens in each case:.
Read more >Troubleshooting connection issues | Socket.IO
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 >Websocket disconnects with 1006 error, without a reason #1520
The players just disconnect with no reason at all. This usually happens at 5-30 minutes mark while the player is actively playing the...
Read more >Websocket connection disconnecting after ping - Forum
This repeated action goes on for about over 30 minutes or so before our applications stops receiving updates or pings. Any idea what...
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
@farzadmf Thanks for the update. I’ll leave this issue open for others to find easier. It would be nice to see a n upstream fix soon.
Hey @june07, an update on my side for my Linux machine:
When I tried again now, I’m seeing the same message as what we talked about on Windows, so I think it’s because of the same reason