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

# Fejl, standard-id for Devolutions Gateway blev ikke fundet

Løs fejlen om, at standard-id'et for Devolutions Gateway ikke kunne findes, ved at angive en standardgateway i Devolutions Server eller Devolutions Cloud.

I Remote Desktop Manager kan sessionen ikke gennemføres, hvis sessionsoptagelse er konfigureret for en gateway, men der ikke er angivet en standardgateway. Remote Desktop Manager returnerer derefter følgende fejl: "Unable to connect with Devolutions Gateway: Gateway ID (default) could not be found."

### Løsning

For at løse det skal De åbne arbejdsområdet i Devolutions Server eller Devolutions Cloud, gå til ***Administration*** og klikke på ikonet Devolutions Gateway.

Angiv den ønskede standardgateway i afsnittet ***Generelt*** i menuen Devolutions Gateway, og gem ændringerne.


---

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