> 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-errors/command-centre-errors-the-configured-s.md).

# The Configured Server is not Trusted by this Client

[Command Centre - Errors](/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors.md) › The Configured Server is not Trusted by this Client

## Symptom

The Command Centre Client fails to allow login with:

```
Command Centre Client - The configured server is not trusted by this client
```

This affects both the Click-Once and the MSI installer clients. It only appears to affect **Windows 10 builds 1809 and 1903**.

![Error: the configured server is not trusted by this client](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-c5c8856d7a4d92e91df17f28b626ca991ec28df3%2FSECHUB-CCS-ERR-SERVER-NOT-TRUSTED-01.png?alt=media)

## Cause

The error is logged in `C:\Users\<user>\AppData\Local\Gallagher\CommandCentreClient.log`. There are two possible causes.

### Error 1, self-signed certificate not trusted

```
UnsafeOpcUaClientLogonManager.DiscoverEndpointComplete Failed to connect to server. Error: Self Signed Certificate is not trusted.
```

**Workaround:** Check that the `ServerThumbprint` value in the client `CommandCentreClient.exe.config` matches that of a working client.

```xml
<add key="ServerThumbprint" value="[REDACTED]"/>
```

The value can be manually modified to match. If the config file has multiple `ServerThumbprint` keys there should only be one. Comment out the line you want to omit by wrapping it in `<!--` and `-->`:

```xml
<!--<add key="ServerThumbprint" value="[REDACTED]"/>-->
<add key="ServerThumbprint" value="[REDACTED]"/>
```

Then try logging in. If one works, delete the other.

### Error 2, cannot create the client certificate container

```
ERROR, OpcUaClientConfigurationProvider.FindOrCreateClientCertificate Exception: Could not create a container for the new key pair. Error=00000005 (-2146233088)
```

This occurs in Windows 10 1903 and later. New Windows users who are members of the Windows **Users** group only are unable to create or add the Command Centre Client certificate in the user's personal store. This is due to the user not having sufficient permissions to the `C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys` folder.

**Workaround:** Manually export a Command Centre Client certificate from another user or workstation **from the same site**, and import the client certificate into the personal store for the affected Windows user.

**Alternative:** Run the `CommandCentreClientAddCertPermissions` and `CommandCentreClientResetCertPermissions` scripts to add and then reset the permissions on the Machine Keys folder. These are available from Gallagher Technical Support.

1. Add permissions with `CommandCentreClientAddCertPermissions`.
2. After logging in to the Command Centre Client, reset permissions with `CommandCentreClientResetCertPermissions`.


---

# 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-errors/command-centre-errors-the-configured-s.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.
