> 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/4.0/troubleshooting/ipxe-endpoint-certificate-errors.md).

# iPXE Endpoint Certificate Errors

Typical errors seen on endpoints that are related to certificates.

## Request failed: ... validation procedure

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

This error means that the certificate used by 2PXE is not trusted by the server that the request was sent to, typically the iPXE Anywhere Web Service server. Often this happens when using the 2PintSoftware.com certificate for 2PXE without the 2PintSoftware.com root certificate in the Trusted Root Certification Authorities store.

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

<figure><img src="https://content.gitbook.com/content/FSXaKC2Zqibd4KXt4dvD/blobs/vRGFl4Shk8fXVR8i6bQf/image.png" alt=""><figcaption></figcaption></figure>

Ensure the 2PintSoftware.com root certificate is in the Trusted Root Certification Authorities store:

<figure><img src="https://content.gitbook.com/content/FSXaKC2Zqibd4KXt4dvD/blobs/AtXOPCs7CSpm5T8EZzs0/image.png" alt=""><figcaption></figcaption></figure>

2PXE installs the 2PintSoftware.com root certificate on the 2PXE server automatically when it gets its certificate (see [Certificate Considerations](/2pxe-server/4.0/planning/certificate-considerations.md)). If the iPXE Anywhere Web Service runs on a different server, export the root certificate from the 2PXE server and import it into the Trusted Root Certification Authorities store on that server.


---

# 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/4.0/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.