# 53000: Signaling connection error

Log Type: APPLICATION

Log Level: ERROR

## Description

Raised whenever a signaling connection error occurs that is not covered by a more specific error code.

### Possible causes

* The client could not establish a connection to Twilio's signaling server or the signaling path was lost.
* Reconnection attempts were exhausted after a network disruption, resulting in a final disconnect with this error.
* Corporate firewall or proxy is blocking secure WebSocket traffic required for signaling on TCP 443 to Twilio Video signaling hosts.
* High latency to the chosen signaling region can slow or prevent establishing the signaling connection.

### Possible solutions

* Retry connecting to the Room.
* Ensure the user has a stable internet connection or try a different network.
* Try connecting to another region or explicitly set the signaling region with the SDK region option, or rely on Global Low Latency.
* Verify that firewalls allow outbound WSS to the appropriate regional signaling hostnames on port 443.
* Ensure Access Tokens have sufficient TTL and are refreshed as needed so reconnections can authenticate successfully.
* Handle reconnection states in your app and, if a 53000 disconnect occurs, prompt the user to rejoin the Room.

#### Additional resources

* [Building a JS Video App: Recommendations and Best Practices](/docs/video/build-js-video-application-recommendations-and-best-practices)
* [Video Regions and Global Low Latency](/docs/video/tutorials/video-regions-and-global-low-latency)
* [Video IP Addresses](/docs/video/ip-addresses)