Technical Tip: HA not in sync because of integrity.json file

Description

This article describes a workaround for the HA sync issue, which is caused by the config sync of the integrity.json file.

Scope

FortiWeb.

Solution

FortiWeb in HA can show that nodes are not in sync due to the config mismatch issue, which can be seen under HA diff check on the GUI.

This will look as shown in the screenshot below:

This is a known issue and will be fixed in version 8.0.5; however, for now, there is a workaround for this if the OS version is older. Follow the steps below:

1. Run this command in CLI:

 diagnose system waf-signature downgrade enable

2. Contact the Support for the older version of the signature database, as it will reset the file.
   
   

3. Upload that file by navigating to System -> Config -> FortiGuard -> Update from File and upload the old signature file to reset the version from 0.428 to 0.412.
   
   

4. After that, verify the version shows 0.412.
   
   

5. Once on the older version, navigate to the CLI of FortiWeb and upgrade the database by running the following command:

execute update-now

6. This process will reset the signature file, downgrade the signature to the previous version, and then upgrade it back to the latest. There is no downtime required during this process.
   
   

Note: After this, the HA will sync automatically. If this still shows the same error, then reach out to Support for further assistance.