Connection to the websocket refused
See original GitHub issueHi,
I have a sip.js application here which I want to let connect to a routr instance. But it fails to connect to the websocket with this message:
WebSocket connection to ‘wss://…com:5063/’ failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
I’ve setup the certificates and have manually entered the wss port in the network settings.
Telnet doesn’t work either and a listen -al | grep LISTEN
shows that the port 5063 isn’t open.
Do you have any clue here?
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (8 by maintainers)
Top Results From Across the Web
connection refused · Issue #1489 · websockets/ws - GitHub
I'm trying to create a socket connection with the example code in the following manner: const ws = new ...
Read more >Javascript create WebSocket connection refused - content ...
Trying to open a WebSocket connection from a Browser to a server running on localhost:9000 here is my JS code:
Read more >websocket connection refused by target machine - Forum
As a first step to confirm connectivity, which is what appears to be your issue here, try using the interactive documentation as outlined...
Read more >WebSocket connection to 'ws://localhost:1234/tiptap' failed
I'm trying to understand how to use local websocket server. In order to use a local websocket server I modified the WebSocketProvider in ......
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...
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 FreeTop 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
Top GitHub Comments
I published a fix for this in the Edge channel of the Snapstore, as well as in the Docker Hub.
There is another unrelated issue with SIP.js that will affect your deployment. I’m closing this for now, but feel free to reopen if this issue reoccurs.
@psanders Hi,
thanks for investigating!
This is my log after a
sudo snap restart routr-server.routr-server
:Afterwards,
sudo lsof -i :5060
still has no output and an exit code of “1”.What I could also offer here, if you are interested (I don’t want to steal your time!): If you give me a public key and your (current) IP address, I could give you direct access to the server. You can send this information to me via philip@philiplb.de.