> 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/fr/knowledge-base/troubleshooting-articles/ssh-shell-entry-failed-to-connect.md).

# Échec de connexion de l'entrée SSH Shell

Corrigez l'erreur de connexion de l'entrée SSH Shell, y compris No authentication method available, en désactivant l'authentification interactive dans les paramètres du terminal.

Échec de la connexion de l'entrée Shell avec l'authentification interactive.

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

Des erreurs apparaissent lors de la connexion avec un SSH Shell dans Remote Desktop Manager 2019.

### Cause

L'option ***Authentification interactive*** dans le terminal est définie à ***True*** sous l'onglet ***Avancé***.

Sous ***Fichier – Paramètres – Types – Terminal***, l'authentification interactive dans le terminal est aussi configurable.

#### Solution

Changez la valeur à ***False*** si l'authentification interactive dans le terminal n'est pas requise.

#### Solution alternative

{% hint style="danger" %}
L'ajout de lignes dans le serveur SSH peut briser le processus d'authentification. N'effectuez jamais cette opération sans une sauvegarde de données.
{% endhint %}

Si l'authentification interactive est requise, confirmez que le serveur SSH inclut les lignes :

`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/fr/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.