> 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.12/configure-cortex-xsoar/engines/configure-engines.md). # Configure engines When installing an engine, a `d1.conf` file is installed on your machine. Some configurations can only be done by editing the d1.conf file. If you install via Shell, you can edit the configuration in the UI as well as editing the file directly. A use case for modifying the engine configuration is if you want to generate engine logs for a specific log level. #### Edit the `d1.conf` file 1. On the machine on which you installed the engine, navigate to the `d1.conf` file: | Installation Type | Location | | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | RPM, DEB, Shell |

/usr/local/demisto

If using multiple engines, the location is /usr/local/demisto/name of the engine>. For example, /usr/local/demisto/d1\_e1

| | ZIP | Same folder as the binary. | 2. Modify the file as required. You can also [Configure the engine to use a web proxy](/cortex-xsoar-8-on-prem/8.12/configure-cortex-xsoar/engines/configure-engines/configure-the-engine-to-use-a-web-proxy.md). #### **Modify the configuration in Cortex XSOAR (Shell installations only)** Ensure that the data is in JSON format. The properties that you specify override the values defined in the `d1.conf` file. 1. From the engines table, select the engine for which you want to modify the configuration. 2. Click **Edit Configuration**. 3. In the **JSON formatted configuration** dialog box, modify the properties as required. ![edit\_engine\_config.png](/files/vYZDfRHM9cmCi58jeArS) #### Common properties when editing an engine configuration The following table describes the common properties when editing an engine configuration using the `d1.conf` file (located by default at **`/usr/local/demisto/`**) or in the **JSON formatted configuration** dialog box in Cortex XSOAR. | Property | Type | Values | Edit | | --------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **`http_proxy`** | String |

The IP address of the HTTP proxy through which the engine communicates.

For an example, see Configure the engine to use a web proxy.

| The engine `d1.conf` file. | | **`https_proxy`** | String |

The IP address of the HTTP/s proxy through which the engine communicates.

For an example, see Configure the engine to use a web proxy.

| The engine `d1.conf` file. | | **`LogLevel`** | String | | The engine `d1.conf` file or in the JSON formatted configuration dialog box. | | **`log.rolling.maxfilesize`** | String | The maximum size in MB to retain log files based. Default is 20 MB. | | | **`log.rolling.backups`** | String | The maximum number of log files to retain. Default is 3. | | | **`log.rolling.maxage`** | String |

The maximum number of days to retain old log files based on the time stamp encoded in the file name. Default is 0 (not to retain old log files based on age).

Note

A day is defined as 24 hours and may not exactly correspond to calendar days due to daylight savings, leap seconds, etc.

| | | **`BindAddress`** | String | The port on which the engine listens for agent connection requests and communication task responses. | The engine `d1.conf` file. | | **`EngineURLs`** | String array | An array of tenant addresses to which the engine tries to connect. If you change the tenant URL, you need to update this parameter. |

The engine d1.conf file.

Note

In addition, to support engine upgrades from the UI, edit the /usr/local/demisto/upgrade.conf file on the engine to include the SERVER\_URLS setting with the new tenant's address. Include only the host, without https\:// or any additional path at the end of the host name. For example: SERVER\_URLS="api-example.us.paloaltonetworks.com"

| | **`LogFile`** | String | Path to the **`d1.log`** file. If you change the name or location of the **`d1.log`** file, you need to update this parameter. | The engine `d1.conf` file. | | **`engine.handshake.max.retries.slow`** | String |

The maximum time in minutes the engine will try to reconnect after losing communication. Default is 600 (10 hours).

Note

If the engine loses communication for longer than this time, it will disconnect and you need to restart the service.

| The engine `d1.conf` 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.12/configure-cortex-xsoar/engines/configure-engines.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.