Get connection status on Socket.io client

node.jssocket.io

node.js Problem Overview


I'm using Socket.io, and I'd like to know the status of connection to the server from the client-side.

Something like this:

socket.status // return true if connected, false otherwise

I need this information to give a visual feedback to the user if the connection has dropped or it has disconnected for any reason.

node.js Solutions


Solution 1 - node.js

You can check the socket.connected property:

var socket = io.connect();
console.log('check 1', socket.connected);
socket.on('connect', function() {
  console.log('check 2', socket.connected);
});

It's updated dynamically, if the connection is lost it'll be set to false until the client picks up the connection again. So easy to check for with setInterval or something like that.

Another solution would be to catch disconnect events and track the status yourself.

Solution 2 - node.js

You can check whether the connection was lost or not by using this function:-

var socket = io( /**connection**/ );
socket.on('disconnect', function(){
//Your Code Here
});

Hope it will help you.

Solution 3 - node.js

These days, socket.on('connect', ...) is not working for me. I use the below code to check at 1st connecting.

if (socket.connected)
  console.log('socket.io is connected.')

and use this code when reconnected.

socket.on('reconnect', ()=>{
  //Your Code Here
});

Solution 4 - node.js

Track the state of the connection yourself. With a boolean. Set it to false at declaration. Use the various events (connect, disconnect, reconnect, etc.) to reassign the current boolean value. Note: Using undocumented API features (e.g., socket.connected), is not a good idea; the feature could get removed in a subsequent version without the removal being mentioned.

Solution 5 - node.js

@robertklep's answer to check socket.connected is correct except for reconnect event, https://socket.io/docs/client-api/#event-reconnect As the document said it is "Fired upon a successful reconnection." but when you check socket.connected then it is false.

Not sure it is a bug or intentional.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionfranzlorenzonView Question on Stackoverflow
Solution 1 - node.jsrobertklepView Answer on Stackoverflow
Solution 2 - node.jsAnsari AbdullahView Answer on Stackoverflow
Solution 3 - node.jsNa NonthasenView Answer on Stackoverflow
Solution 4 - node.jsIlanView Answer on Stackoverflow
Solution 5 - node.jsQiulangView Answer on Stackoverflow