General Troubleshooting of SecureSuite Platform Installation Issues

Problem

An error occurred during installation of the CIS SecureSuite Platform application, including but not limited to the following:

• IAM or other service startup errors

• Java Path errors

• For cloud deployments on non-AWS hosts (Azure, Google Cloud, Oracle Cloud), please see:
  SecureSuite Platform Installation returns "Error occurred getting the public IP address of your machine"Preview

This KB article is intended as a supplement to the troubleshooting steps in the official documentation:
https://cisecurity-securesuite-documentation.readthedocs-hosted.com/en/latest/Resolve%20Installation%20Errors/

Solution

Please follow the steps below to review the most common causes for SecureSuite Platform installation issues.

• If this is a server that previously hosted a CIS-CAT Pro Dashboard or CSAT Pro installation, please ensure all former components of these applications (MariaDB, Neo4j) have been removed. This includes the JAVA_HOME Environment Variable, which may still be pointing to the non-existent Dashboard / CSAT Pro directory.

  • You can access this property under “System Properties” → “Advanced” → “Environment Variables”. If correctly configured, the JAVA_HOME entry should point to:
    C:\Program Files\SecureSuite\java\jdk17.0.13_11
    
    

    Open

    

     

  • If this entry is present, you can also test the bundled Java instance by opening an administrative cmd.exe prompt and calling the java -version command, which should return output similar to the following:

    C:\> java -version openjdk version "17.0.13" 2024-10-15 LTS OpenJDK Runtime Environment Corretto-17.0.13.11.1 (build 17.0.13+11-LTS) OpenJDK 64-Bit Server VM Corretto-17.0.13.11.1 (build 17.0.13+11-LTS, mixed mode, sharing)

     

• Run the SecureSuite_Uninstaller.exe in the C:\Program Files\SecureSuite directory to remove any currently deployed components

  • You can verify all components have been successfully removed by checking the following services & folders:
    https://cisecurity-securesuite-documentation.readthedocs-hosted.com/en/latest/Installation%20and%20Upgrade%20-%20Windows/#uninstall-manually
    
    

• Reboot the host system - this is required to remove any still pending services & processes, and may cause the second installation attempt to fail if the system is not restarted beforehand.
  
  

• After the uninstallation & reboot completes, ensure that none of the required ports are now in use by another application or service:
  https://cisecurity-securesuite-documentation.readthedocs-hosted.com/en/latest/Installation%20and%20Upgrade%20-%20Windows/#traffic-and-ports
  Prior to the new installation attempt, none of the required ports (80, 443, 3306 & 8081) should be occupied by any service or application.
  
  

• Run the latest SecureSuite v1.2.1 Installer downloaded from CIS WorkBench:
  https://workbench.cisecurity.org/download/securesuite/platform

  • During the setup, select the option to create a new Self-Signed certificate (rather than an existing organizational one). This will make it significantly easier to troubleshoot the rest of the deployment, and you can always switch certificates later by re-running the installer.
    
    

    Open

    

     

  • If during the setup you encounter any additional errors, capture the Installer Logs (bottom left) before the installer window is exited, which will include detailed entries on any setup inconsistencies or failed deployments.

Should the installation work as expected with a self-signed certificate, you can then use the following guidelines to use an organizational .p12 TLS certificate instead:
https://cisecurity-securesuite-documentation.readthedocs-hosted.com/en/latest/Installation%20and%20Upgrade%20-%20Windows/#configure-https

Keywords; SecureSuite Platform SSP Install Errors JAVA_HOME

Content by Label