> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/quill/troubleshooting.md).

# Troubleshooting

Troubleshoot missing Quill replies and corporate network connectivity

Use this guide when Quill accepts a message but does not display a reply.

## Quill does not show a reply

Quill uses a real-time connection to display responses as they are generated. A corporate firewall, proxy, or secure web gateway can block that connection while the rest of AirOps continues to work.

1. Refresh the page. If the reply appears after the refresh, Quill completed the request but the live update did not reach your browser.
2. Try Quill from another network and, if permitted, a device that is not managed by the same corporate security policy. A mobile hotspot alone may not bypass security software installed on your device.
3. If Quill works outside the corporate network or device policy, ask your IT team to allow the domains and protocols below.

{% hint style="info" %}
Changing browsers, using a private browsing window, or switching networks may not help when security software on the device routes all traffic through the same corporate policy.
{% endhint %}

## Corporate network requirements

Allow HTTPS and secure WebSocket traffic over TCP port 443 to these domains:

| Domain                  | Protocol | Purpose                                    |
| ----------------------- | -------- | ------------------------------------------ |
| `app.airops.com`        | HTTPS    | AirOps and real-time channel authorization |
| `ws-mt1.pusher.com`     | WSS      | Primary real-time WebSocket connection     |
| `sockjs-mt1.pusher.com` | HTTPS    | XHR streaming and polling fallback         |
| `js.pusher.com`         | HTTPS    | Fallback transport code                    |

If your network policy supports wildcard domains, allow:

```
app.airops.com
*.pusher.com
```

The proxy must permit WebSocket upgrade requests and long-lived HTTPS connections used for XHR streaming. If TLS inspection disrupts these connections, exclude the Pusher domains from inspection.

## Contact AirOps Support

If Quill still does not display replies on another network, contact [AirOps Support](mailto:support@airops.com). Include your workspace URL, browser, and the approximate time of the affected message.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.airops.com/quill/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.