> ## 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.

# App appears disconnected or stale

> Data not updating, meetings not syncing, or app stuck loading

## What you'll see

The app loads but data looks stale  -  meetings don't update, artifacts don't appear, or the UI feels stuck. You might also see loading spinners that never resolve.

<Frame caption="When the UI loads but live updates do not arrive">
  <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/live-sync-toggle-on.png?fit=max&auto=format&n=7bmTb55b6UAEQSbk&q=85&s=15717ce535577d14d065ff2b3aeed393" alt="Earmark meeting interface highlighting sync-related controls when realtime updates may appear stuck." style={{ width: '100%', display: 'block' }} width="256" height="133" data-path="images/live-sync-toggle-on.png" />
    </div>
  </div>
</Frame>

## Why this happens

Earmark uses Convex as its realtime backend. Convex relies on WebSocket connections to push updates to clients without polling. If your network blocks WebSocket upgrades while allowing plain HTTPS, the app will load but won't receive live updates.

## What to allow

| Setting      | Value                         |
| ------------ | ----------------------------- |
| Convex API   | `https://sync.tryearmark.com` |
| HTTP Actions | `https://api.tryearmark.com`  |
| Protocols    | WSS and HTTPS                 |
| Port         | 443                           |

WebSockets are established over HTTPS (WSS) on port 443  -  the same port as regular web traffic. Blocking WebSocket upgrades while allowing plain HTTPS is the most common cause of this issue.

## Connectivity test

Run Convex's network test tool to verify your network can reach Earmark's backend:

<Card title="Convex network test" icon="wifi" href="https://network-test.previews.convex.dev/">
  Checks basic HTTPS and WebSocket connectivity to Convex domains. All checks should pass for Earmark to function correctly behind a firewall or proxy.
</Card>

## What to check

* **Proxy / firewall rules**  -  ensure WSS traffic to `sync.tryearmark.com` is not being blocked or downgraded
* **TLS inspection**  -  deep packet inspection can interfere with WebSocket handshakes
* **Browser extensions**  -  some ad blockers or privacy extensions block WebSocket connections

<Tip>
  If the Convex network test above fails any checks, share the results with your IT team  -  it pinpoints exactly which connection type is being blocked.
</Tip>
