---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/53002#article
headline: "53002: Signaling connection timed out"
url: https://www.twilio.com/docs/api/errors/53002
inLanguage: en
dateModified: 2026-06-08T11:29:20.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 53002: Signaling connection timed out

Log Level: ERROR

## Description

This error occurs when the Video signaling connection times out. Twilio raises it when connection liveliness checks fail or when the signaling session expires. A Room can also surface 53002 after a network disruption if signaling reconnection takes too long and the client disconnects.

### Possible causes

* Outbound WSS traffic on port 443 to Twilio Video signaling domains is blocked by a firewall or network policy.
* A proxy or firewall closes idle WebSocket connections too quickly. Twilio recommends a WSS idle timeout of at least 300 seconds for Twilio Video signaling traffic.
* A forward proxy, TLS inspection, or deep packet inspection interferes with WSS signaling traffic instead of allowing pass-through.
* A VPN or unstable network path interrupts signaling long enough that reconnection cannot complete before the Room disconnects.

### Possible solutions

* Allow outbound WSS on port 443 to Twilio Video signaling domains and make sure the affected network allows the required Twilio Video traffic.
* Increase the WebSocket idle timeout on your proxy or firewall to at least 300 seconds for Twilio Video signaling connections.
* Configure proxies to support WSS pass-through without inspection for signaling traffic. If you use TLS inspection or application-aware filtering, exclude Twilio Video signaling traffic from that inspection path.
* If users connect through a VPN, configure split tunneling so Twilio Video traffic can use the local network path when possible.
* Run the Preflight API or the Video Diagnostics Application from the affected network to verify signaling and TURN connectivity before users join a Room.
* Handle `reconnecting`, `reconnected`, and `disconnected` events in your application so you can show connection status, retry appropriately, and capture 53002 when reconnection takes too long.

#### Additional resources

* [Firewall and Network Configuration](/docs/video/ip-addresses)
* [Preflight API](/docs/video/troubleshooting/preflight-api)
* [Reconnection States and Events](/docs/video/reconnection-states-and-events)