Known issues

Known issues

This section lists known issues in version FortiADC 7.1.0, but may not be a complete list. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.

Bug ID	Description
0829750	fnginxctld crash based on issue with longer loading time for websites going through FortiADC.
0828572	200D/100F/200F/1000F/2000F/4000F incorrectly uses FortiADC-VM as the CN (Common Name) for the default certificate Subject, which may cause FortiSandbox Cloud connection issues. This is expected to be fixed in the next release.
0827447	miglogd crash related to FortiAnalyzer.
0826540	In the GUI, failed to append child list when configuring Automation. This results when an alert type has reached the maximum entry capacity. The current maximum is 256 entries for each alert type, as categorized in the backend CLI: `config system alert-policy` `config system alert-action` `config system alert` `config system alert-email` `config system alert-snmp-trap` `config system alert-script` `config system alert-webhook` `config system alert-fortigate-ip-ban` `config system alert-syslog` `config system alert-policy` configurations are often composed of multiple `config system alert` entries, making the `config system alert` most likely to exceed the entry capacity. Please use `show full-configuration system alert` for details in the CLI. Workaround: After figuring out which alert type has exceeded the 256 entry capacity from the backend CLI, remove any unused automation alerts from the GUI.
0824203	There are some defects with the Country and phone number on the local user page and system Administrator page.
0823021	Timeout issue when creating a 2FA-local user and 2FA Administrator.
0822565	CLI and GUI response is not the same when creating a 2FA-local user.
0822356	New mysqld (MariaDB 10.6.7) will crash when it meets a corrupted database table. This behavior did not occur in the previous version because the corrupted database table would have been ignored. Workaround: Run the CLI command `execute log rebuild` to rebuild the Database.
0820293	FortiADC shows "bind failed(30002372)" warning during automation test.
0819547	When importing the automated local certificate through GUI, if the internet connection is down or too slow, it will cause the certificate generation to fail due to server timeout. It may take several seconds to receive the timeout error, during which the GUI will be non-responsive.
0816798	In an HA environment, if you are using a predefined automation configuration, resetting the configuration through the GUI (using the reset button) or unsetting comments through CLI will cause the HA synchronization to fail whenever a device reboots and rejoins the cluster. Using the GUI reset button resets the predefined configuration values to the predefined default values, all except the comments value which is set to the default value on the backend. For example, if using the HA predefined configuration, the reset will result in `set comments HA` → `set comments comments`. When a new device (or a rebooted device) joins the HA cluster, the synchronization will fail due to the mismatched `set comments` value between the device that has the predefined default value (`set comments HA`) and the reset device that has the default value (`set comments comments`). In the CLI, if `set comments` in the predefined configuration has been `unset` and is the default value `set comments comments`, then the same HA synchronization issue will occur. Workaround: In the CLI, edit `set comments` to ensure it is not the default value (`set comments comments`) and it matches the value of the predefined configuration (for example, `set comments HA`).
0811061	When using CLI command `conf-sync` to get a configuration file more than 10 MB, the operation may get stuck showing only "auth access", unable to retreive the file.
0798862	Health Check does not support RFC 7919 yet.
0782143	From the GUI, if the FortiAnalyzer is cloned, the OFTP connection of the original configuration will disconnect, with debug showing it has stopped the connection to the FortiAnalyzer server.

Known issues

This section lists known issues in version FortiADC 7.1.0, but may not be a complete list. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.

Bug ID

Description

0829750

fnginxctld crash based on issue with longer loading time for websites going through FortiADC.

0828572

200D/100F/200F/1000F/2000F/4000F incorrectly uses FortiADC-VM as the CN (Common Name) for the default certificate Subject, which may cause FortiSandbox Cloud connection issues.

This is expected to be fixed in the next release.

0827447

miglogd crash related to FortiAnalyzer.

0826540

In the GUI, failed to append child list when configuring Automation. This results when an alert type has reached the maximum entry capacity.

The current maximum is 256 entries for each alert type, as categorized in the backend CLI:

config system alert-policy
config system alert-action
config system alert
config system alert-email
config system alert-snmp-trap
config system alert-script
config system alert-webhook
config system alert-fortigate-ip-ban
config system alert-syslog

config system alert-policy configurations are often composed of multiple config system alert entries, making the config system alert most likely to exceed the entry capacity. Please use show full-configuration system alert for details in the CLI.

Workaround:

After figuring out which alert type has exceeded the 256 entry capacity from the backend CLI, remove any unused automation alerts from the GUI.

0824203

There are some defects with the Country and phone number on the local user page and system Administrator page.

0823021

Timeout issue when creating a 2FA-local user and 2FA Administrator.

0822565

CLI and GUI response is not the same when creating a 2FA-local user.

0822356

New mysqld (MariaDB 10.6.7) will crash when it meets a corrupted database table. This behavior did not occur in the previous version because the corrupted database table would have been ignored.

Workaround: Run the CLI command execute log rebuild to rebuild the Database.

0820293

FortiADC shows "bind failed(30002372)" warning during automation test.

0819547

When importing the automated local certificate through GUI, if the internet connection is down or too slow, it will cause the certificate generation to fail due to server timeout. It may take several seconds to receive the timeout error, during which the GUI will be non-responsive.

0816798

In an HA environment, if you are using a predefined automation configuration, resetting the configuration through the GUI (using the reset button) or unsetting comments through CLI will cause the HA synchronization to fail whenever a device reboots and rejoins the cluster.

Using the GUI reset button resets the predefined configuration values to the predefined default values, all except the comments value which is set to the default value on the backend. For example, if using the HA predefined configuration, the reset will result in set comments HA → set comments comments. When a new device (or a rebooted device) joins the HA cluster, the synchronization will fail due to the mismatched set comments value between the device that has the predefined default value (set comments HA) and the reset device that has the default value (set comments comments).

In the CLI, if set comments in the predefined configuration has been unset and is the default value set comments comments, then the same HA synchronization issue will occur.

Workaround: In the CLI, edit set comments to ensure it is not the default value (set comments comments) and it matches the value of the predefined configuration (for example, set comments HA).

0811061

When using CLI command conf-sync to get a configuration file more than 10 MB, the operation may get stuck showing only "auth access", unable to retreive the file.

0798862

Health Check does not support RFC 7919 yet.

0782143

From the GUI, if the FortiAnalyzer is cloned, the OFTP connection of the original configuration will disconnect, with debug showing it has stopped the connection to the FortiAnalyzer server.

Release Notes

Known issues

Known issues