In Cortex XSOAR, integrations and automation
scripts run either on the server or in a Docker container.
Integrations and automation scripts that run on the server include
using a JS virtual environment. These integrations use the same
network IPs as the server.
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
When running integrations or automations that run within Docker
containers you might encounter cases that networking fails for these
integrations. The following are several examples of 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
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
After you add the server configuration, run the
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
If you have Docker networking issues when using an engine, you
need to modify the d1.conf file.
On the machine where the Engine is installed, open the d1.conf file.