> For the complete documentation index, see [llms.txt](https://docs.enginsight.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enginsight.com/docs/knowledge-base/english/troubleshooting/the-enginsight-platform-cannot-connect-to-the-siem-what-can-i-do.md).

# The Enginsight platform cannot connect to the SIEM. What can I do?

If the Enginsight platform shows that it cannot establish a connection to the SIEM, this can have several causes. Check the following:

***

## Reachability of the Enginsight Application Server

To test whether the SIEM Management Server can reach the Enginsight Application Server, follow these steps:

{% stepper %}
{% step %}
Log in to the **SIEM Management Server** and open the **Loggernaut configuration file** using the following command:

```
sudo nano /opt/enginsight/loggernaut/config.json
```

{% endstep %}

{% step %}
Note down the URL that is specified in the `api` section.
{% endstep %}

{% step %}
Check whether the Application Server can be reached using the following command:

```
curl <NotedURL>/v1
```

{% hint style="info" %}
Remember to replace `<NotedURL>` accordingly.
{% endhint %}

The response must return the HTTP status code **200**.
{% endstep %}
{% endstepper %}

***

## Reachability of the SIEM Management Server

To test whether the Enginsight Application Server can reach the SIEM Management Server, log in to the **Application Server** and run the following command:

```
curl -v -u "<SIEMManagementServerUsername>:<SIEMManagementServerPassword>" <SIEMManagementServerDomain>/v1/status
```

{% hint style="info" %}
Remember to replace the placeholders in `<>` accordingly:

* `<SIEMManagementServerUsername>`
* `<SIEMManagementServerPassword>`
* `<SIEMManagementServerDomain>`
  {% endhint %}

The response must return HTTP status code **200**. If this is not the case, check the following:

### 1. Correct firewall rule configuration

Check whether the required firewall rules have been configured.

{% hint style="success" icon="lightbulb" %}
For more information on which firewall rules are required for the SIEM Management Server, see the Enginsight manual: [System requirements | Enginsight SIEM](https://docs.enginsight.com/docs/manual/english/installation-und-konfiguration/system-requirements/enginsight-siem)
{% endhint %}

### 2. Validity of the SSL/TLS certificates

Check whether your configured SSL/TLS certificates are still valid and replace them if necessary.

{% hint style="success" icon="lightbulb" %}
For more information on how to replace an SSL/TLS certificate in Enginsight, see the Knowledge Base: [How do I update a SSL/TLS certificate by Let's Encrypt in Enginsight?](/docs/knowledge-base/english/configuration/how-do-i-update-a-ssl-tls-certificate-by-lets-encrypt-in-enginsight.md) or [How do I replace a self-signed SSL/TLS certificate in Enginsight?](/docs/knowledge-base/english/configuration/how-do-i-replace-a-self-signed-ssl-tls-certificate-in-enginsight.md)
{% endhint %}

### 3. Use of a self-signed SSL/TLS certificate or Windows PKI

If you use a self-signed SSL/TLS certificate or a Windows PKI (Public Key Infrastructure), you must manually store the certificate files (complete certificate chain with a separate private key) on the Application Server.

You must then mark the root certificate as trusted on both the Application Server and the SIEM Management Server.

{% hint style="success" icon="lightbulb" %}
For more information on how to store and configure a self-signed SSL/TLS certificate in Enginsight, see the Knowledge Base: [How do I store and configure a self-signed SSL/TLS certificate in Enginsight?](/docs/knowledge-base/english/configuration/how-do-i-store-and-configure-a-self-signed-ssl-tls-certificate-in-enginsight.md)
{% endhint %}

### 4. Use of a proxy

If you use a proxy, the proxy environment must be explicitly configured on the SIEM Management Server, the SIEM Index Server, and in the Docker containers `solr`, `loggernaut`, and `traicer`.

Check whether all configuration changes have been made accordingly and whether the proxy has been configured correctly.

{% hint style="success" icon="lightbulb" %}
For more information on which configuration changes are required when using a proxy, see the Knowledge Base: [Which configuration changes do I need to make in Enginsight if I use a proxy?](/docs/knowledge-base/english/configuration/what-configuration-adjustments-do-i-need-to-make-in-enginsight-if-i-use-a-proxy.md)
{% endhint %}

***