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

# Errore ID Devolutions Gateway predefinito non trovato

Risolva l'errore Devolutions Gateway ID default could not be found impostando un gateway predefinito in Devolutions Server o Devolutions Cloud.

In Remote Desktop Manager, se la registrazione delle sessioni è configurata per un gateway ma non è stato impostato un gateway predefinito, la sessione non può essere stabilita. Remote Desktop Manager restituisce quindi il seguente errore: "Unable to connect with Devolutions Gateway: Gateway ID (default) could not be found."

### Soluzione

Per risolvere il problema, apra il suo spazio di lavoro Devolutions Server o Devolutions Cloud, vada in ***Administration*** e faccia clic sull'icona Devolutions Gateway.

Imposti il gateway predefinito desiderato nella sezione ***General*** del menu Devolutions Gateway e salvi le modifiche.


---

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