Configure the engine to use a web proxy ↗

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

You need to configure Docker to use a proxy. When using a BlueCoat proxy, ensure you encode the values correctly.

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>http://``<user:password@proxy-server:port#></p><p>For example `http://user:password@proxy-server:3128`</p>	Environment uses HTTP proxy. Special characters must be escaped.
`https_proxy`	<p>https://``user:password@proxy-server:port#</p><p>For example, `https://user:password@proxy-server:3128`</p>	Environment uses HTTPS proxy. Special characters must be escaped.
`no_proxy`	<p>http://``<user:password@proxy-server:port#></p><p>For example `http://user:password@proxy-server:3128`</p>	For specific addresses, a proxy bypass will be applied. Special characters must be escaped.

If the environment variables are not set, or you wish to use different settings than those specified in the environment variables, set the configuration with your specific proxy details in the d1.conf file. For example:
```
{"http_proxy": "http://proxy.host.local:8080",
"https_proxy": "https://proxy.host.local:8443"
"no_proxy": "https://proxy.host.local:8020"}
```
Save the file.
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".

In an environment with a single engine, go to /usr/local/demisto/upgrade.conf. In an environment with multiple engines, go to /usr/local/demisto/<engine-name>/upgrade.conf, replacing <engine-name> with the name of the engine.
Note that the key is in the upgrade.conf file and must be https_proxy, even if your proxy address starts with http://.
Save the file.