> For the complete documentation index, see [llms.txt](https://docs.certinext.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.certinext.io/documentation/troubleshooting-and-faqs/error-codes-reference.md).

# Error Codes Reference

This section provides a centralized reference of CERTINext error codes, their causes, and recommended resolutions to support faster troubleshooting.

### **Error Code Reference Table**

| Error Code | Description                 | Possible Cause                 | Resolution                                    |
| ---------- | --------------------------- | ------------------------------ | --------------------------------------------- |
| ERR-001    | Bot not connected           | Network issue / Bot inactive   | Verify connectivity and restart Bot           |
| ERR-002    | Certificate issuance failed | CA integration issue           | Check CA connector credentials and API access |
| ERR-003    | DCV validation failed       | Domain not reachable           | Verify DNS resolution and DCV path            |
| ERR-004    | Deployment failed           | Permission denied              | Validate server credentials and access rights |
| ERR-005    | CSR generation error        | Invalid template configuration | Review CSR template fields                    |
| ERR-006    | API authentication failed   | Invalid API key/token          | Regenerate and update credentials             |
| ERR-007    | Certificate not found       | Inventory mismatch             | Re-run discovery scan                         |
| ERR-008    | Renewal failed              | Expired certificate / CA issue | Retry renewal and validate CA status          |
| ERR-009    | Unsupported server type     | Invalid provisioning config    | Select supported server type                  |
| ERR-010    | Key store access error      | Incorrect password/path        | Verify keystore credentials                   |

### **Usage**

* Use error codes from logs, UI alerts, or API responses
* Match with table for root cause
* Apply resolution steps
