> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/engines/configure-engines/configure-the-engine-to-use-a-web-proxy.md).

# Configure the engine to use a web proxy

Configure a Cortex XSOAR 8.10 On-prem engine to use a web proxy.

Proxy settings can be configured in an engine by adding them as an engine configuration.

{% hint style="info" %}

### Note

You need to [configure Docker](https://docs.docker.com/config/daemon/systemd/#httphttps-proxy) to use a proxy. When using a BlueCoat proxy, ensure you encode the values correctly.
{% endhint %}

1. On the machine on which you installed the engine, navigate to the `d1.conf` file and add the following keys.

   | Key           | Value                                                                                                                                        | Description                                                                                 |
   | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
   | `http_proxy`  | <p><code>http\://\`\`\<user:password\@proxy-server:port#></code></p><p>For example <code><http://user:password@proxy-server:3128></code></p> | Environment uses http proxy. Special characters must be escaped.                            |
   | `https_proxy` | <p><code>https\://\`\`user:password\@proxy-server:port#</code></p><p>For example, <code><https://user:password@proxy-server:3128></code></p> | Environment uses https proxy. Special characters must be escaped.                           |
   | `no_proxy`    | <p><code>http\://\`\`\<user:password\@proxy-server:port#></code></p><p>For example <code><http://user:password@proxy-server:3128></code></p> | For specific addresses, a proxy bypass will by applied. Special characters must be escaped. |
2. If the environment variables are not set, or you wish to use a different settings than those specified in the environment variables, set the configuration with your specific proxy details in the **`d1.conf`** file. For example:

   ```programlisting
   {"http_proxy": "http://proxy.host.local:8080",
   "https_proxy": "https://proxy.host.local:8443"
   "no_proxy": "https://proxy.host.local:8020"}
   ```
3. Save the file.
4. On the machine where you installed the engine, navigate to the `upgrade.conf` file and edit the file to set `https_proxy` to your proxy address. For example, `https_proxy="https://proxy.host.local:8443"`.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>In a environment with a single engine, go to <code>/usr/local/demisto/upgrade.conf</code>. In an environment with multiple engines, go to <code>/usr/local/demisto/&#x3C;engine-name>/upgrade.conf</code>, replacing &#x3C;engine-name> with the name of the engine.</p><p>Note that the key in the <code>upgrade.conf</code> file must be <code>https_proxy</code>, even if your proxy address starts with <code>http://</code>.</p></div>
5. Save the file.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/engines/configure-engines/configure-the-engine-to-use-a-web-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.