> 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/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/docker/troubleshoot-docker-networking-issues.md).

# Troubleshoot Docker Networking Issues

Troubleshoot Docker networking issues in Cortex XSOAR 6.14.

In Cortex XSOAR, integrations and automation scripts run either on the server or in a Docker container.

* Server-based integrations: Integrations and automation scripts that run on the server include native integrations (part of the server binary) and JavaScript integrations. JavaScript integrations run within the Cortex XSOAR server process using a JS virtual environment. These integrations use the same network IPs as the server.
* Docker-based integrations: These include integrations written in Python or Powershell. Docker creates its own networking, thus the integrations are using a different networking stack from the Cortex XSOAR server. The source IPs for these integrations are different and provided according to the Docker networking configuration.

**Network issues for integrations**

When running integrations or automations that run within Docker containers you might encounter cases that networking fails for these integrations. The following examples show error messages that indicate a networking issue:

* `[Errno -2] Name does not resolve`
* `[Errno 110] Operation timed out`
* `Failed to establish a new connection: [Errno -3] Try again`

We recommend that you use the [Docker networking stack](https://docs.docker.com/network/) because it provides networking isolation and to consult the Docker documentation to resolve Docker networking issues.

If there are issues running Docker's networking stack, you have the option to run Docker containers with the host networking. In this mode, the container will share the host’s network stack and all interfaces from the host will be available to the container. The container’s host name will match the hostname on the host system. To enable host networking, add the following advanced server configuration in Cortex XSOAR:

* Key: **`python.pass.extra.keys`**
* Value: **`--network=host`**

After you add the server configuration, run the **`/reset_containers`** command from the Cortex XSOAR CLI to reset all containers and to begin using the new configuration.

For multi-tenant deployments, you need to add this setting to each tenant.

**Engines**

If you have Docker networking issues when using an engine, you need to modify the [d1.conf file](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/engines/configure-engines.md#UUID-0bab90bb-978d-3430-649d-1cbcb8b560d3).

1. On the machine where the Engine is installed, open the d1.conf file.
2. Add to the d1.conf file the following:

   ```programlisting
   {
           "LogLevel": "info",
           "LogFile": "/var/log/demisto/d1.log",
           "EngineURLs": [
           "wss://1234.demisto.live/d1ws"
           ],
                   "BindAddress": ":443",
           "EngineID": "XYZ",
           "ServerPublic": "ABC"
           "ArtifactsFolder": "",
           "TempFolder": "",
           "python.pass.extra.keys": "--network=host"
           }
   ```
3. Save the file.
4. Restart the engine using `systemctl restart d1` or `service d1 restart`.


---

# 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/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/docker/troubleshoot-docker-networking-issues.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.