> 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/ssh-shell-entry-failed-to-connect.md).

# La entrada SSH Shell no se pudo conectar

Corrija el error de conexión fallida de la entrada SSH Shell, incluido No authentication method available, desactivando la autenticación interactiva en la configuración del terminal.

La entrada Shell no ha podido conectarse con la autenticación interactiva.

```
An unknown SSH error was encountered.
No authentication method available
```

Aparecen errores al conectarse con un SSH Shell en Remote Desktop Manager 2019.

### Causa

La ***autenticación interactiva*** en el terminal está establecida en ***True*** en la pestaña ***Avanzado***.

En ***Archivo – Configuración – Tipos – Terminal***, la autenticación interactiva en el terminal también es configurable.

#### Solución

Cambie el valor a ***False*** si no se requiere la autenticación interactiva en el terminal.

#### Solución alternativa

{% hint style="danger" %}
Añadir líneas en el servidor SSH puede interrumpir el proceso de autenticación. No haga esto nunca sin una copia de seguridad.
{% endhint %}

Si se requiere la autenticación interactiva para confirmar que el servidor SSH incluye las líneas:

`KbdInteractiveAuthentication yes ChallengeResponseAuthentication yes UseLogin no UsePam yes`


---

# 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/ssh-shell-entry-failed-to-connect.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.