4. Known problems and limitations

4.1. Active-CTI / RetroHunt - Post Update problem

In some cases, Active-CTI and RetroHunt (available with the LIS license) may not work optimally.

Workaround : contact Gatewatcher Technical Support.

4.2. GCenter Backup/Restore - Error management

If an error has been made by the user while applying the restore procedure, the menu progress bar (`Admin-Backup/Restore - Backup operations` screen) remains blocked and no error message is visible in the WebUI.

Workaround: no workaround.

4.3. GCenter Backup/Restore - Pairing the GCap

Following a GCenter backup, if the GCap pairing is deleted, then restoring the backup will not enable restoring the connection with the previously deleted GCap.

Workaround: reapply the pairing.

4.4. Incorrect GCap status after updating the GCenter

The GCap status may be wrong after updating the GCenter (Last update = unknown / State: Online but update outdated)

Workaround: apply again the ruleset configuration at the GCap level.

4.5. Sigflow Manager - Transform Category

Applying a Transform category raises a 500 error if no ruleset is available on GCenter.

Workaround: create a ruleset.

4.6. Sigflow Manager - Error 500 when adding a rule in a custom source

Adding a rule raises a 500 error if the following conditions are present:

The addition is done by editing a custom source
the rule already exists in another custom source (same SID)

Workaround: change the SID of the rule you want to add to avoid the SID conflict.

4.7. Sigflow Manager - Inconsistency in displaying the number of categories and rules in a category

The `Sigflow > Sources` homepage shows the number of categories and rules contained in each source.
It is possible that the information presented is inconsistent with the actual content of the sources.
This case can occur after editing a custom source or an update.

Workaround: no workaround.

4.8. Sigflow Configuration - Custom source name cannot contain space

In the `Config - Sigflow/sources` screen of the legacy web UI, it is possible to define a custom source of signatures for the Sigflow detection engine.
During the addition procedure, the source name must be entered.
This name must not contain any space otherwise it will generate an error.

Workaround: change the name by removing spaces.

4.9. GCenter Backup/Restore - Error in FQDN

In v2.5.3.103, when restoring a backup, if the FQDN of the target GCenter is different then an error is generated.

Workaround: change the FQDN of the target GCenter and perform a reboot.

4.10. Kibana - Error 500 due to changing storage media for ES data

Following the change of ES data storage media, a temporary 500 error may appear when accessing Kibana.

Workaround: wait a few minutes.

4.11. Migration - Problem with online update configuration

During the migration to v2.5.3.103, in some cases, the process fails due to the configuration of the online update.

Workaround: this problem is corrected in v2.5.3.103-HF1.

4.12. Migration - Problem with the detected user base of NDR interface

During the migration to v2.5.3.103, when the database of detected users, visible on the NDR interface in the `users` tab, contains several tens of thousands of entries, the update process does not succeed.

Workaround: this problem is corrected in v2.5.3.103-HF1.

4.13. Migration - Problem with the application of Sigflow rulesets

During the migration to v2.5.3.103, if a ruleset other than the `default_ruleset` is used it may not apply correctly.