# Document and connection errors

Source: [https://docs.aventail.co.uk/docs/workspace/troubleshooting-document-too-large](https://docs.aventail.co.uk/docs/workspace/troubleshooting-document-too-large)

Test a short message first, then check the document and browser connection.

### Separate chat from document problems

Process overview; detailed actions and examples are below.

1.  **Separate chat from document problems**
    
    Test a short plain message before troubleshooting an attachment. Keep the exact error.
    
    -   Plain chat: Does a short message work?
    -   Small document: Try TXT or MD
    -   Browser access: Check local-network and origin errors

**Read the troubleshooting steps**

## Start with a short message

Send a message without an attachment. If that also fails, check that Link is running, the model is **serving**, and Workspace has **Your node** selected. See [Connect your model](https://docs.aventail.co.uk/docs/workspace/getting-started#connect-your-model).

If plain chat works, try a small TXT or MD document. Check the attachment help for the current size limit and confirm the selected model can handle the document's text.

## Check browser access

A browser request can fail before inference starts because of local-network permissions or origin restrictions. A working terminal request does not prove that the browser can reach the same endpoint.

Retain the exact error and compare it with [local API troubleshooting](https://docs.aventail.co.uk/docs/getting-started/run-first-interface#if-the-request-fails). Do not disable browser security to make the request work.

## Older deployments

The [July 2026 Control notes](https://docs.aventail.co.uk/docs/changelog/control#july-2026) record an origin-allowlist defect that appeared as “document too large.” That history does not establish the cause of every current size error.

If a deployment predates that fix, contact support about refreshing its serving configuration. Redeployment may interrupt requests and require another download. Do not call an undocumented repair endpoint with a copied account token.

## Information for support

Include the exact error, browser and Link versions, selected model, file type/size, and whether plain chat works. Use a non-sensitive sample document if a reproduction is needed.