> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/2pxe-server/troubleshooting/ipxe-endpoint-certificate-errors.md).

# iPXE Endpoint Certificate Errors

Covering some errors seen on the endpoints and some typical errors that are related to certificates

## Request failed: ... validation procedure

Full Error: Request failed: The remote certificate is invalid according to the validation procedure.

When you see this, that means the certificate you have assigned via the thumbprint in the 2PXE config isn't trusted by the iPXE server.  Often this happens when using the 2PintSoftware self-signed certificate for 2PXE but forgetting to add the root cert into your trusted root certificate store.

Certificate generated by 2PXE for the 2PXE process, issued by 2PintSoftware.com:

<figure><img src="https://1599432282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nkrKH5nKL8LvEgvw7HO%2Fuploads%2Fcz5vJqVZr1WQZA6w1WeS%2Fimage.png?alt=media&amp;token=8891f963-8971-4c90-82b6-6d63f99486bd" alt=""><figcaption></figcaption></figure>

Ensure the 2PintSoftware.com root cert is in the Trusted Root Certification Certificate Store:

<figure><img src="https://1599432282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nkrKH5nKL8LvEgvw7HO%2Fuploads%2F5cBExVsTEmvuzbfJxPrZ%2Fimage.png?alt=media&amp;token=53ff6474-9623-4060-9c71-2078c3c5870e" alt=""><figcaption></figcaption></figure>

If you still need to import that certificate, it can be found here: \
"C:\Program Files\2Pint Software\2PXE\x64\ca.crt"


---

# 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://documentation.2pintsoftware.com/2pxe-server/troubleshooting/ipxe-endpoint-certificate-errors.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.
