> 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.13/learn-about-cortex-xsoar/onboarding-in-cortex-xsoar/engines/troubleshoot-cortex-xsoar-engines/troubleshoot-engine-connectivity.md).

# Troubleshoot Engine Connectivity

The following provides instructions for troubleshooting connectivity issues from the engine to the endpoint.

1. Follow the instructions in [network troubleshooting](https://xsoar.pan.dev/docs/reference/articles/troubleshooting-guide#host-based-networking).
2. Ensure that the engine can reach the endpoint by running the following command on the server engine.

   **`sudo curl -kvv <endpointURL>`**
3. If the engine could not reach the endpoint, try the IP with curl instruction adding the http(s)//, or try using ping.

   If this works, add the IP to the /etc/hosts file with the hostname and try to reach the endpoint again by running the following command on the engine server

   **`sudo curl -kvv <endpointURL>.`**

   If this still fails, then this is an issue of connectivity between the engine and endpoint and you need to resolve this with your networking team.
4. Once connectivity has been confirmed via curl:
   * Try connecting within Docker without passing host networking.

     **`docker run -it --rm demisto/netutils:1.0.0.6138 curl -kvv <endpointURL>`**

     If this succeeds but the integration still fails, it could be a integration credentials issue. In that case, open a [support case](https://support.paloaltonetworks.com/support).
   * If without passing host networking fails, run the following:

     **`docker run -it --rm --network=host demisto/netutils:1.0.0.6138 curl -kvv <endpointURL>`**

     If this succeeds, add "python.pass.extra.keys": "--network=host" to /usr/local/demisto/d1.conf and retest the integration.

     If you see a Docker or Selinux issue, see [Troubleshoot Docker Networking Issues](/xsoar-6-administrator-guide/6.13/learn-about-cortex-xsoar/onboarding-in-cortex-xsoar/docker/troubleshoot-docker-networking-issues.md).
5. If the installation issue remains, open a support case with logs from the main server and engine.
   1. On the engine server, in `/usr/local/demisto/d1.conf`, set "LogLevel": "debug”.
   2. On the main server, navigate to **Settings** → **ABOUT** → **Troubleshooting** and verify that the Log Level is set to Debug.
   3. Restart the d1 service and let it run for a few minutes.

      **`sudo systemctl restart d1`**
   4. On the main server, go to **Settings** → **ABOUT** → **Troubleshooting**+Download logsto download a log bundle.
   5. Capture a journalctl:

      **`journalctl --since "1 day ago" > engineTroubleshootingJournalctl.log`**
   6. On the engine server, tar up the logs, conf, journalctl, and install log on the engine.

      **`tar -cvzf engineLogs.tar.gz /var/log/demisto /usr/local/demisto/d1.conf /tmp/demisto_install.log engineTroubleshootingJournalctl.log`**

**Engine 443 Error**

This error might occur when a connection is established between an engine and the Cortex XSOAR server, because, by default, Linux does not allow processes to listen on low-level ports.

**Error Message**

**`listen tcp :443: bind: permission denied`**

**Solution**

* In the `d1.conf` file, change the port number to a higher one, for example, 8443.
* Run this command: **`sudo setcap CAP_NET_BIND_SERVICE=+eip /path/to/binary`**. After running this command the server should be able to bind to low-numbered ports.


---

# 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/xsoar-6-administrator-guide/6.13/learn-about-cortex-xsoar/onboarding-in-cortex-xsoar/engines/troubleshoot-cortex-xsoar-engines/troubleshoot-engine-connectivity.md?ask=<question>&goal=<endgoal>
```

`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.