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

# Devolutions Server ne peut pas se mettre à jour lors de l'utilisation d'un proxy

Résolvez les échecs de mise à jour de Devolutions Server derrière un proxy après la mise à jour vers .NET 8.0 en configurant appsettings.json avec les paramètres de proxy.

Suite à la mise à jour vers .NET 8.0, les environnements utilisant un proxy peuvent rencontrer des problèmes lorsque Devolutions Server tente d'effectuer une mise à jour.

### Solution

Pour résoudre ce problème, configurez la Devolutions Server Console pour utiliser un proxy personnalisé en définissant les paramètres dans un fichier appsettings.json :

1. Naviguez vers le répertoire d'installation de la Devolutions Server Console (`C:\Program Files (x86)\Devolutions\Devolutions Server Console`, par exemple).
2. Dans ce répertoire, créez un fichier nommé `appsettings.json`.
3. Ajoutez votre configuration de proxy au fichier en utilisant l'exemple suivant :

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

4. Enregistrez le fichier.
5. Rouvrez la Devolutions Server Console et relancez le processus de mise à jour.


---

# 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/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.