> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/gateway/da/knowledge-base/how-to-articles/change-the-devolutions-gateway-certificate.md).

# Skift certifikatet til Devolutions Gateway

Skift det TLS-certifikat, der bruges af Devolutions Gateway, direkte fra Devolutions Server Console i nogle få hurtige trin.

Certifikater til Devolutions Gateway kan skiftes hurtigt og nemt i Devolutions Server Console. Følg instruktionerne nedenfor:

1. Åbn Devolutions Server Console, og klik på knappen ***Rediger*** i sektionen ***Devolutions Gateway*** på fanen ***Ledsagere***.
2. Skift derefter ***HTTP-lytter*** til ***https***, og klik på ellipseknappen (***…***) i feltet ***Certifikatfil*** under overskriften ***Certifikatkonfiguration***.
3. Vælg den `.pfx`-certifikatfil, der skal skiftes til, og klik på ***Ok*** for at gemme ændringerne.
4. Vent, indtil tjenesten genstarter, eller gør det manuelt i konsollen Windows Services.
5. Kontrollér til sidst tilstanden for Devolutions Gateway som beskrevet i [Fejlfinding af Devolutions Gateway](/gateway/da/knowledge-base/troubleshooting-articles/devolutions-gateway-troubleshooting.md#verify-the-health-of-a-gateway).


---

# 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.devolutions.net/gateway/da/knowledge-base/how-to-articles/change-the-devolutions-gateway-certificate.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.