> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/access/client-registry/troubleshooting-client-registry.md).

# Troubleshooting Client Registry

Resolve common issues with client registration, authentication, and connectivity.

The following table addresses common issues you might encounter when registering clients with Connectware. Use these solutions to quickly resolve problems with client registration, authentication, and connectivity.

## Troubleshooting - Self-Registering Clients via REST API

These issues apply to clients registering via the `/api/client-registry/register` REST API. Also see [Self-Registering Clients via REST API](/2-6-1/access/client-registry/self-registering-clients-via-rest-api.md).

For detailed information about the Client Registry REST API parameters, see [Auth-Server API](/2-6-1/reference/api-reference/auth-server-api.md).

| Issue                              | Possible Cause                 | Solution                                                                                                                                                              |
| ---------------------------------- | ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Client not appearing in registry   | Registry is locked             | Unlock the registry using the lock icon in the Admin Web App.                                                                                                         |
| Registration failing               | Username/password too short    | Ensure username ≥ 3 characters, password ≥ 5 characters. Also adhere to the [Password Policy Configuration](/2-6-1/access/security/password-policy-configuration.md). |
| CSR rejection                      | CN mismatch in CSR             | Ensure CSR's Common Name matches the requested username.                                                                                                              |
| Client stuck in "pending"          | Admin hasn't granted access    | Review and approve from Client Registry interface.                                                                                                                    |
| Unexpected "locked" (423) response | Registry timeout               | Registry auto-locks after 5 minutes; unlock it again.                                                                                                                 |
| Certificate authentication failing | Invalid or missing certificate | Ensure CSR is valid and the signed certificate is used.                                                                                                               |

## Troubleshooting - Self-Registering MQTT Clients

These issues apply to MQTT clients self-registering via authentication attempts. Also see [Self-Registering MQTT Clients](/2-6-1/access/client-registry/self-registering-mqtt-clients.md).

| Issue                                            | Possible Cause              | Solution                                                                                                                                                              |
| ------------------------------------------------ | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Client not appearing in registry                 | Registry is locked          | Unlock the registry using the lock icon in the Admin Web App.                                                                                                         |
| Registration failing                             | Username/password too short | Ensure username ≥ 3 characters, password ≥ 5 characters. Also adhere to the [Password Policy Configuration](/2-6-1/access/security/password-policy-configuration.md). |
| Client stuck in "pending"                        | Admin hasn't granted access | Review and approve from Client Registry interface.                                                                                                                    |
| Connection failures after registration           | Missing permissions         | Assign appropriate roles to the newly created user.                                                                                                                   |
| Multiple failed connection attempts              | Incorrect credentials       | Verify credentials match exactly what was registered.                                                                                                                 |
| Client disconnecting after successful connection | Permission issues           | Ensure publish/subscribe permissions are correctly assigned.                                                                                                          |


---

# 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://docs.cybus.io/2-6-1/access/client-registry/troubleshooting-client-registry.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.