> 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/server/de/knowledge-base/troubleshooting-articles/invalid-self-signed-certificate-in-chrome-and-edge.md).

# Ungültiges selbstsigniertes Zertifikat in Chrome und Edge

Erläutert, warum Chrome und Edge ältere selbstsignierte Zertifikate von Windows Server ablehnen und wie Sie ein gültiges Zertifikat für Devolutions Server erstellen.

Die standardmäßig in Windows Server (vor 2022) generierten selbstsignierten Zertifikate werden von Chrome und Edge nicht mehr als gültig angesehen. Weitere Informationen zu Chrome finden Sie in der Google-Dokumentation zur [Richtlinie RSAKeyUsageForLocalAnchorsEnabled](https://chromeenterprise.google/policies/#RSAKeyUsageForLocalAnchorsEnabled).

### Lösung

In Windows Server 2022 können Sie ein neues selbstsigniertes Zertifikat generieren. In älteren Versionen können Sie das folgende PowerShell-Skript verwenden, um ein gültiges selbstsigniertes Zertifikat zu generieren:

```powershell
#Create the cert and place it in the personal cert store
$cert = New-SelfSignedCertificate -DnsName $(([System.Net.Dns]::GetHostByName($env:computerName)).HostName) -CertStoreLocation "cert:\LocalMachine\My" -KeyUsage DigitalSignature,CertSign,CRLSign -KeyAlgorithm RSA -KeyLength 2048 -Provider "Microsoft Enhanced RSA and AES Cryptographic Provider" -NotAfter (Get-Date).AddYears(5)
```


---

# 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/server/de/knowledge-base/troubleshooting-articles/invalid-self-signed-certificate-in-chrome-and-edge.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.