11. Known Issues

11.1. AAC#004: Multiple Sandbox Issues

Introduced Version

Fixed Version

<= 3.7.8


There are currently three issues with the sandbox integration:

  1. Wrong python script capev2.py

  2. Reports can't be downloaded

  3. Files coming from the Bifrost Quarantine have no Name (missing)

Those issues will be fixed with the next release.

11.1.1. AAC#004: Workarounds

  1. To fix the capev2.py file, contact support. We can provide you with the correct file

  2. No workaround - upgrade needed

  3. No workaround - upgrade needed

11.2. AAC#003: Case Management - onDelete is not defined

Introduced Version

Fixed Version



Version 3.7.4 of the Analysis Cockpit introduced a bug, which occurs when trying to edit Access rights for Case Status in the Case Management settings. The following error appears along with a visual bug on the right side of your browser window which says "Retry":


Error: Something went wrong

onDelete is not defined

There is currently no workaround for this bug, you need to upgrade to version 3.8.2 or higher to fix this.

11.3. AAC#002: Context Deadline Exceeded

Introduced Version

Fixed Version



When debugging GRPC connectivity issues between your components (for example Management Center to Analysis Cockpit), you might encounter an error similar to the following one:

 2 "LEVEL":"Warning",
 3 "MESSAGE":"could not dial grpc",
 4 "MODULE":"api",
 5 "REQUEST_IP":"",
 6 "TIME":"2023-03-06T12:35:37Z",
 7 "USER":"admin",
 8 "error":"context deadline exceeded",
 9 "host":"cockpit3.domain.local:7443"

11.3.1. AAC#002: Workaround

There is no workaround for this type of error. The error usually occurs because one of the following things are preventing proper communication between your components:

  • Firewall is using TLS Inspection

  • Proxy is using TLS Inspection

  • DNS Issues


Your components expect specific certificates from each other when communicating. If a device is trying to inspect TLS traffic, the certificate will change and you receive the above error.

To help you figuring out what is causing the problem, you can try the following. You can use openssl on your source system to see which certificate is presented by the destination host (change the host and port values as needed)

nextron@asgard2:~$ openssl s_client -host cockpit3.domain.local -port 7443
depth=0 O = Nextron Systems GmbH, CN = cockpit3.domain.local
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 O = Nextron Systems GmbH, CN = cockpit3.domain.local
verify error:num=21:unable to verify the first certificate
verify return:1
write W BLOCK
Certificate chain
 0 s:O = Nextron Systems GmbH, CN = cockpit3.domain.local
   i:O = Nextron Systems GmbH, CN = Analysis Cockpit 3
Server certificate

The marked lines show you the certificate which is presented by the destination host. If this certificate is different from the one you installed, then the problem might be a device trying to do TLS Inspection.

We are currently working on improving the presented error message, to give a better understanding what might be the issue at hand.

11.4. AAC#001: Nested LDAP Groups not working

Introduced Version

Fixed Version



Using nested groups in your LDAP/AD will result in no users because the query will fail.

11.4.1. AAC#001: Workaround

Change your LDAP GroupFilter to the following: