> 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/rdm/de/knowledge-base/troubleshooting-articles/devolutions-gateway-id-default-not-found-error.md).

# Fehler: Devolutions Gateway ID default not found

Beheben Sie den Fehler „Devolutions Gateway ID default could not be found", indem Sie in Devolutions Server oder Devolutions Cloud ein Standard-Gateway festlegen.

Wenn in Remote Desktop Manager die Sitzungsaufzeichnung für ein Gateway konfiguriert ist, aber kein Standard-Gateway festgelegt wurde, kann die Sitzung nicht zustande kommen. Remote Desktop Manager gibt dann folgenden Fehler zurück: "Unable to connect with Devolutions Gateway: Gateway ID (default) could not be found."

### Lösung

Um dies zu beheben, öffnen Sie Ihre Devolutions Server- oder Devolutions Cloud-Datenquelle, gehen Sie zu ***Administration*** und klicken Sie auf das Devolutions Gateway-Symbol.

Legen Sie im Abschnitt ***Allgemein*** des Devolutions Gateway-Menüs das gewünschte Standard-Gateway fest und speichern Sie Ihre Änderungen.


---

# 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/rdm/de/knowledge-base/troubleshooting-articles/devolutions-gateway-id-default-not-found-error.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.