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

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

You get the following error message dialog when you try to authenticate on the Devolutions Server instance with Remote Desktop Manager.

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

### Solution

There are two different solutions for this issue:

* Reduce the number of AD Groups that the user account is part of. We are aware that most of the time, because of the design of the AD structure, it is not possible to reduce the number of AD groups.
* Increase the settings for the ***MaxFieldLength*** and the ***MaxRequestBytes*** registry entries on the server. Please consult the following Microsoft article for more information on how to increase these values. <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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.devolutions.net/server/knowledge-base/troubleshooting-articles/the-remote-server-returned-an-error-400-bad-request.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.