Why is my user stuck in a Presence Channel?

Usually, when a client disconnects, it closes the TCP socket on both ends and we can send the "member removed" event immediately. However, certain situations can result in the client not cleanly disconnecting, and leaving a "half open connection" where a client will still be seen as online by the server even though they aren't connected. We find and close these half open connections by sending a ping to the client after a certain period of inactivity, and then if no pong response is received, the connection is assumed dead and closed. This can take a couple of minutes to happen.

The timeout for inactive connections in Pusher is 60 seconds. After the 60 seconds a ping is sent and if a pong is not received within 15 seconds then the connection is cleaned up. This means that Pusher can indicate a connection is open for up to 75 seconds before cleaning up.

You can't change the amount of time before a ping is sent, and the amount of time to wait for a pong response unless your app is on dedicated cluster.

If your app is on dedicated cluster and you want to change the ping and pong timeouts to support your use case better, please, let us know at support@pusher.com.

Was this article helpful?
0 out of 0 found this helpful
Haven't found what you were looking for?
Submit a ticket