> 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/http-status-code-unauthorized-error-message.md).

# Mensaje de error HTTP Status Code Unauthorized

Corrija el error HTTP Status Code Unauthorized en Remote Desktop Manager desactivando la autenticación básica en el sitio web de Devolutions Server en IIS.

Cuando la ***opción Basic Authentication*** está habilitada en la función Authentication del sitio web de Devolutions Server, Remote Desktop Manager muestra el siguiente mensaje de error:

```
HttpStatusCode: Unauthorized,
HttpErrorReason: Unauthorized,
Error: Unauthorized,
```

### Solución

1. Abra el ***Administrador de IIS***.
2. Expanda el árbol en el ***panel izquierdo***.
3. Seleccione el sitio web o la aplicación de Devolutions Server.
4. Abra la ***función Authentication***.
5. Desactive la ***Basic Authentication***.

Si ningún otro sitio de esa máquina requiere la ***Basic Authentication***, puede desinstalarla desde los ***Roles de servidor*** en el ***Administrador del servidor***.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/rdm/es/knowledge-base/troubleshooting-articles/http-status-code-unauthorized-error-message.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 `build a script that syncs our docs to a CMS` 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.