> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryearmark.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Live transcription not working

> Transcript stuck on connecting or not starting

## What you'll see

The live transcript stays stuck on "connecting" or never starts after you begin recording. Audio is being captured but no text appears.

<Frame caption="Live transcript panel while the stream is establishing">
  <div
    style={{
  backgroundImage: 'url(https://mintcdn.com/earmark/vNkCE4NL0UOVgfZk/images/background-blue.png?fit=max&auto=format&n=vNkCE4NL0UOVgfZk&q=85&s=8d57271bb6e72c3715e83d97907c438b)',
  backgroundSize: 'cover',
  backgroundPosition: 'center',
  borderRadius: '1rem',
  padding: '4%',
}}
  >
    <div
      style={{
    borderRadius: '0.875rem',
    overflow: 'hidden',
    boxShadow: '0 24px 60px rgba(15, 23, 42, 0.28)',
  }}
    >
      <img src="https://mintcdn.com/earmark/7bmTb55b6UAEQSbk/images/transcript-live-1.png?fit=max&auto=format&n=7bmTb55b6UAEQSbk&q=85&s=7433ef279a229f3bfc72c76b6121ecf9" alt="Meeting view with live transcript area shown while transcription is connecting or starting." style={{ width: '100%', display: 'block' }} width="830" height="570" data-path="images/transcript-live-1.png" />
    </div>
  </div>
</Frame>

## Why this happens

Earmark streams audio to AssemblyAI for transcription using a secure WebSocket connection. If your network blocks WebSocket upgrades  -  common with corporate firewalls, VPNs, and TLS inspection proxies  -  the connection can't be established.

## What to allow

| Setting  | Value                      |
| -------- | -------------------------- |
| Hostname | `streaming.assemblyai.com` |
| Protocol | WSS                        |
| Port     | 443                        |

WebSocket endpoint:

```text theme={null}
wss://streaming.assemblyai.com/v3/ws
```

## What to check

* **Firewall / proxy rules**  -  WebSocket traffic on port 443 must not be blocked or downgraded to plain HTTPS
* **TLS inspection**  -  some corporate proxies intercept and re-sign TLS traffic, which can break WebSocket upgrades
* **VPN split tunneling**  -  if your VPN routes all traffic through a corporate gateway, WebSocket connections may be dropped

<Tip>
  If you're on a corporate network and transcription works fine on your home network, your IT team likely needs to allowlist the AssemblyAI hostname above.
</Tip>