Known issues
FortiProxy 7.2.9 includes the known issues listed in this section. For inquiries about a particular bug, please contact Customer Service & Support.
| Bug ID | Description |
|---|---|
|
913703 |
Multiple wad processes are in "Dead" state and users cannot access any website that requires proxy. |
|
990366 |
Device freezes and randomly reboots. |
|
998612 |
FortiProxy cannot display local traffic log. |
|
992247 |
HA connection from secondary FortiProxy to FortiAnalyzer goes through the virtual IP instead of the dedicated management interface. |
|
991280 |
No FortiGuard firmware updates in GUI. Upgrade can only be done manually by uploading the firmware image file. |
|
1005060 |
Ingress traffic shaper hits a bandwidth throttle that cannot be more than 2.5 Gbps. Workaround: Use egress shaper for better scalability. |
FortiNBI
The following issues have been identified in FortiNBI. For inquiries about a particular bug, please contact Customer Service & Support.
| Bug ID | Description |
|---|---|
| 975570 |
Certificate warning when starting up the isolator. Workaround: Ignore the certificate warning. |
| 881957 |
Error in Google Chrome or Microsoft Edge login page when FortiNBI is on. Workaround: Use Firefox. |
|
N/A |
Log collection fails if the isolator is not installed. |
|
N/A |
Instability issues caused by isolator state tracking. |
|
N/A |
Isolator download timeout is too long. |
|
N/A |
Service state are not accurate in edge scenarios during restart. |
|
N/A |
GUI is unavailable due to a broken link to Windows App SDK. |
|
N/A |
No timeout when task fails to start repeatedly. |