> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-mp-guide/infrastructure/certificates/lets-encrypt-certificates/how-parallels-ras-requests-certificates-from-lets-encrypt.md).

# How Parallels RAS requests certificates from Let's Encrypt

When you create a new Let’s Encrypt certificate using Parallels RAS, the following process is carried out:

1. Parallels RAS Primary Connection Broker that hosts the licensing role makes the initial request to the Let’s Encrypt server to create an account.
2. Account creation confirmation is received. Parallels RAS creates a CSR and sends it to the Let’s Encrypt server.
3. A list of challenges is received, and Connection Broker reads the HTTP token sent by the Let’s Encrypt server.
4. Secure Gateway or HALB retrieves the tokens from the Connection Broker.
5. Once ready, Connection Broker notifies the Let’s Encrypt Server.
6. Let’s Encrypt starts the verification process by going to the Secure Gateway or HALB and confirming the availability of the token.
7. Challenges are completed including confirmation that the Secure Gateways or HALB can reply to the domain mentioned.
8. Assuming that the challenge is completed successfully, Parallels RAS requests a certificate.
9. Valid certificate is downloaded from the Let’s Encrypt server to Connection Broker.
10. Connection Broker distributes the certificate to the Secure Gateways or HALB.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.parallels.com/landing/ras-mp-guide/infrastructure/certificates/lets-encrypt-certificates/how-parallels-ras-requests-certificates-from-lets-encrypt.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.