# Why Am I Receiving "Websocket Is Closed Before The Connection Is Established" Error Messages?

The **WebSocket is closed before the connection is established** error message indicates that some client code, or other mechanism, has closed the websocket connection before the connection was fully established. 

If the connection eventually succeeds then the message can be safely ignored. 

If you are using Google Chrome you may need to restart your browser. We've seen that after Chrome updates there is sometimes a network issue which stops WebSocket connections from succeeding.

If you are still having issues please contact us using the button below. 

{% hint style="info" %}
Still have questions? Please reach out to our Support team by visiting [this page](https://messagebird.com/support-center/Pusher-request-new).
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bird.com/pusher/channels/channels/troubleshooting/why-am-i-receiving-websocket-is-closed-before-the-connection-is-established-error-messages.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.