80014: Connection timed out

The connection was not established, or a response was not received, within the time allowed. This often points to a slow or unreliable network path between the client and Ably.

What you should do

Usually nothing, since the SDK retries automatically. If the connection never establishes, check that the network and any firewall or proxy between the client and Ably allow access to Ably's endpoints, and look for a slow or unreliable path that keeps requests from completing in time.

Why it happens

The connection wasn't established, or an expected response didn't arrive, within the time the SDK allows before timing out. This usually reflects a slow or unreliable network path, or the client being unable to reach Ably's primary and fallback endpoints.

What you'll see

The error is reported with code 80014. The message is typically connection timed out, and the request is retried automatically.