Fortinet black logo

Release Notes

Home FortiProxy 7.2.10 Release Notes
7.2.10
7.4.4
7.4.3
7.4.2
7.4.1
7.4.0
7.2.10
7.2.9
7.2.8
7.2.7
7.2.6
7.2.5
7.2.4
7.2.3
7.2.2
7.2.1
7.2.0
7.0.17
7.0.16
7.0.15
7.0.14
7.0.13
7.0.12
7.0.11
7.0.10
7.0.9
7.0.8
7.0.7
7.0.6
7.0.5
7.0.4
7.0.3
7.0.2
7.0.1
7.0.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.1
2.0.0
1.2.13
1.2.12
1.2.11
1.2.10
1.2.9
1.2.8
1.2.7
1.2.6
1.2.5
1.2.4
1.2.3
1.2.2
1.2.1
1.2.0
1.1.6
1.1.5
1.1.4
1.1.3
1.1.2
1.1.1
1.1.0
1.0.7
1.0.6
1.0.5
1.0.4
1.0.3
1.0.2
1.0.1
1.0.0

Known issues

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.

990366

Device freezes and randomly reboots.

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.

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:

  • Try running “wsl –shutdown” and then restarting the isolator.

  • Use the FortiNBI WSLg graphics, which has lower performance than the Microsoft’s WSLg graphics.
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.
Previous
Next

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.

990366

Device freezes and randomly reboots.

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.

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:

  • Try running “wsl –shutdown” and then restarting the isolator.

  • Use the FortiNBI WSLg graphics, which has lower performance than the Microsoft’s WSLg graphics.
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.
Previous
Next