> 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/cc-software/troubleshoot/command-centre-connection-issues/command-centre-connection-issues-u-2.md). # Unable to log into Command Centre Client via IPv6 [Command Centre - Connection Issues](/knowledge-hub/products/cc-software/troubleshoot/command-centre-connection-issues.md) › Unable to log into Command Centre Client via IPv6 If a site uses IPv6 for a Command Centre Client connection, edit `CommandCentreClient.exe.config` in `C:\Program Files (x86)\Gallagher\Command Centre\Client\`. An OPC connection requires square brackets `[ ]` around the IPv6 expression. **Correct format:** ```xml ``` **Incorrect format** (note the lack of square brackets around the IPv6 expression): ```xml ``` > **Note:** The connection time may be longer than IPv4. If the server name can be translated to IPv6, you do not have to edit the config file of the Configuration Client. ![IPv6 correct format: address wrapped in square brackets](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-6626361028c900c053c78dc152a360d59d90883c%2FSECHUB-CCS-CONN-IPV6-02.png?alt=media) ![IPv6 incorrect format: address with no square brackets](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-3f98e7a68b8138dde6191bc6235950695526a4ca%2FSECHUB-CCS-CONN-IPV6-01.png?alt=media) *** 🔗 **Related** * [Workstations located across a large geographic area](/knowledge-hub/products/cc-software/troubleshoot/command-centre-connection-issues/command-centre-connection-issues-works.md). Deploying many dispersed workstations. --- # 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/cc-software/troubleshoot/command-centre-connection-issues/command-centre-connection-issues-u-2.md?ask=&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.