> 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/server/fr/knowledge-base/troubleshooting-articles/the-remote-server-returned-an-error-400-bad-request.md).

# The remote server returned an error (400) Bad Request

Corrige le message d'erreur « remote server returned an error 400 Bad Request » dans Remote Desktop Manager en réduisant le nombre de groupes AD ou en augmentant les limites de taille des en-têtes IIS

Vous obtenez la boîte de dialogue du message d'erreur suivant lorsque vous tentez de vous authentifier sur l'instance Devolutions Server avec Remote Desktop Manager.

```
The remote server returned an error (400) Bad Request
```

### Solution

Il existe deux solutions différentes à ce problème :

* Réduire le nombre de groupes AD dont fait partie le compte utilisateur. Nous sommes conscients que, la plupart du temps, en raison de la conception de la structure AD, il n'est pas possible de réduire le nombre de groupes AD.
* Augmenter les paramètres des entrées de registre ***MaxFieldLength*** et ***MaxRequestBytes*** sur le serveur. Veuillez consulter l'article Microsoft suivant pour plus d'information sur la façon d'augmenter ces valeurs. <https://support.microsoft.com/en-us/help/2020943/http-400-bad-request-request-header-too-long-response-to-http-request>


---

# 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/server/fr/knowledge-base/troubleshooting-articles/the-remote-server-returned-an-error-400-bad-request.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.