Known issues
FortiProxy 7.2.10 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. |
|
998612 |
FortiProxy cannot display local traffic log. |
|
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. |
|
1022209 |
"400 error!" for SAML authentication with FortiAuthenticator. |
|
1011771 |
Traffic is sometimes not processed with UTM profiles in policy. |
|
1003762 |
Loss of connection with no internet access and multiple crashes for the application WAD. |
|
990366 |
Device freezes and randomly reboots. Kernel panic observed. |
|
1052333 |
Some categories are missing under System > Replacement Messages in GUI. |
FortiNBI
The following issues have been identified in FortiNBI. For inquiries about a particular bug, please contact Customer Service & Support.
| Bug ID | Description |
|---|---|
|
N/A |
WSL2 X11 output corruption. This is a known bug on Microsoft’s WSLg graphics. Workaround:
|
| 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. |