> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-reverse-proxy-connection.md).

# Mobile Client reverse proxy connection issues

Resolve Mobile Client connection problems in reverse proxy deployments.

A reverse proxy connection is complex to set up. Expect initial problems, and the person configuring it should have done this kind of work before.

* The Gallagher certificate is **not exportable**, so the site needs its own signed (likely purchased) certificate, installed on **both** the proxy and the Command Centre server.
* Set the Web Servers to **Signed Token** (Server Properties → Web Services in Configuration Client). This step is often forgotten.
* Gallagher **recommends Signed Token** for reverse-proxy connections.

> **Note:** Diagnosis needs the Mobile logs, Proxy logs **and** the CAPI2 logs. These are not simple to read and likely require a Gallagher developer. See Microsoft's guidance on [how to enable CAPI2 logging](https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/diagnostic-logging-troubleshoot-workplace-join-issues).

***

🔗 **Related**

* [Connection Options - Signed Token vs TLS Client Certificate](/knowledge-hub/products/cloud-services/command-centre-mobile-client/configure/mobile-client-connection-options-signe.md). Why TLS cannot be used through a proxy.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-reverse-proxy-connection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.