> 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/devolutions-server-cannot-update-when-using-a-proxy.md).

# Devolutions Server no puede actualizarse cuando se utiliza un proxy

Resuelva los fallos de actualización de Devolutions Server detrás de un proxy tras la actualización a .NET 8.0 configurando appsettings.json con la configuración del proxy.

Tras la actualización a .NET 8.0, los entornos que utilizan un proxy pueden experimentar problemas cuando Devolutions Server intenta realizar una actualización.

### Solución

Para resolver este problema, configure Devolutions Server Console para que utilice un proxy personalizado definiendo la configuración en un fichero appsettings.json:

1. Vaya al directorio de instalación de Devolutions Server Console (`C:\Program Files (x86)\Devolutions\Devolutions Server Console`, por ejemplo).
2. En este directorio, cree un fichero llamado `appsettings.json`.
3. Añada la configuración de su proxy al fichero utilizando el siguiente ejemplo:

```json
  {
    "ProxySettings": {
      "Address": "XXX.XXX.X.XX:XXX",
      "BypassOnLocal": true,
      "ProxyCredentialSettingType": "WindowsCredentials",
      "Domain": "",
      "UserName": "",
      "Password": ""
    }
  }
```

4. Guarde el fichero.
5. Vuelva a abrir Devolutions Server Console e inicie de nuevo el proceso de actualización.


---

# 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/devolutions-server-cannot-update-when-using-a-proxy.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.