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

# Error de ID de Devolutions Gateway predeterminado no encontrado

Corrija el error «Devolutions Gateway ID default could not be found» estableciendo una puerta de enlace predeterminada en Devolutions Server o Devolutions Cloud.

En Remote Desktop Manager, si la grabación de sesiones está configurada para una puerta de enlace pero no se ha establecido una puerta de enlace predeterminada, la sesión no puede establecerse. Remote Desktop Manager devuelve entonces el siguiente error: "Unable to connect with Devolutions Gateway: Gateway ID (default) could not be found."

### Solución

Para solucionarlo, abra su Devolutions Server o su espacio de trabajo de Devolutions Cloud, vaya a ***Administration*** y haga clic en el icono de Devolutions Gateway.

Establezca la puerta de enlace predeterminada deseada en la sección ***General*** del menú de Devolutions Gateway y guarde los cambios.


---

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