Known issues
FortiProxy 7.0.18 includes the known issues listed in this section. For inquires about a particular issue, please contact Fortinet Customer Service & Support.
|
Bug ID |
Description |
|---|---|
|
888831 |
WAD crash at wad_cs_proc_content_block during cache stress. |
|
947350 |
Error in decrypting Kerberos ticket during Kerberos authentication. |
|
996825 |
scanunit application inside FortiProxy firmware crash. |
|
979076 |
WAD worker health status is not alive after moving users to FortiProxy. |
|
990293 |
When the FortiADC primary shuts down, the FortiProxy redundant interface switches over. |
|
1005060 |
Ingress traffic shaper hits a bandwidth throttle that cannot be more than 2.5 Gbps. Workaround: Use egress shaper for better scalability. |
|
1017952 |
FPX-2000E automatically powers off . |
|
1049784 |
On ESXi 7.0 or later, you cannot deploy FortiProxy 7.0.18 directly. Workaround: Deploy FortiProxy 7.0.17 first and then upgrade to 7.0.18. |
|
1052333 |
Some categories are missing under System > Replacement Messages in GUI. |