> 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/integrations/video-management-systems/milestone/mips-client-cannot-connect.md).

# MIPs client cannot connect

Resolve MIPs client connection failures caused by communication, REST, or certificate issues.

### MIPs client cannot connect

1. On the MIPs client, from a command window, **PING** the Command Centre server name or IP. No reply points to a communication issue, a firewall, a physical break, or a name-resolution or IP-routing problem.
2. **Telnet** to the Command Centre server on **port 8904**. No connection points to a communication issue, REST not being licensed or enabled, or the default port 8904 having been changed.
3. If comms are fine but MIPs still will not connect, it is a **certificate issue**. On the Command Centre server: **Configuration Client → File → Server Properties → Web Services → REST API "Manage Certificates"**, then depending on the selected option (Default, Custom, or External) click the matching **View → Details** tab → **Copy to File…** and export as **DER encoded binary X.509 (.CER)**. On the MIPs client, install that certificate into **Local Computer → Trusted Root Certification Authorities**.

![Server Properties → Web Services tab: the REST API section with the "Manage Certificates" button](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-49a36b47718129b526e400ac035b8461a3b77cf7%2FSECHUB-INT-MILESTONE-MIPS-OVERVIEW-01.png?alt=media)

![The "Manage REST API Certificate" dialog: Default, Custom, and External certificate options with their View buttons](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-ee6418a4f8e2bd1bac5cc5a7a7d98a0fa73a3719%2FSECHUB-INT-MILESTONE-MIPS-OVERVIEW-02.png?alt=media)

![The Command Centre Server certificate successfully present in the client's Local Computer → Trusted Root Certification Authorities store (the end-state after a correct import)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-3ff4b0c0617b26bbe5e64a22e9f1a82c8d84751d%2FSECHUB-INT-MILESTONE-MIPS-OVERVIEW-03.png?alt=media)


---

# 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/integrations/video-management-systems/milestone/mips-client-cannot-connect.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.