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

# Devolutions Gateway ID default not found error

Fix the Devolutions Gateway ID default could not be found error by setting a default gateway in Devolutions Server or Devolutions Cloud.

In Remote Desktop Manager, if session recording is configured for a gateway but a default gateway has not been set, then the session cannot go through. Remote Desktop Manager then returns the following error: "Unable to connect with Devolutions Gateway: Gateway ID (default) could not be found."

### Solution

To remedy this, open your Devolutions Server or Devolutions Cloud workspace, go to ***Administration***, and click on the Devolutions Gateway icon.

Set the desired default gateway in the ***General*** section of the Devolutions Gateway menu and save your changes.


---

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