Known issues

Known issues

FortiProxy 7.2.11 includes the known issues listed in this section. For inquiries about a particular bug, please contact Customer Service & Support.

Bug ID	Description
1068729	Wad crashes at wad_http_session_get_from_msg.
913703	Multiple wad processes are in "Dead" state and users cannot access any website that requires proxy.
991280	No FortiGuard firmware updates in GUI. Upgrade can only be done manually by uploading the firmware image file.
998612	FortiProxy cannot display local traffic log.
1005060	Ingress traffic shaper hits a bandwidth throttle that cannot be more than 2.5 Gbps. Workaround: Use egress shaper for better scalability.
1052333	Some categories are missing under System > Replacement Messages in GUI.
1060782	root.b is down and all related routes are missing for standalone FortiProxy in transparent mode. Workaround: Enable active-passive HA on the FortiProxy and ensure hbdev is up. Reboot the FortiProxy and verify that `get sys ha stat` shows the FortiProxy as primary without any warning of hbdev being down.

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.
881957	Error in Google Chrome or Microsoft Edge login page when FortiNBI is on. Workaround: Use Firefox.
975570	Certificate warning when starting up the isolator. Workaround: Ignore the certificate warning.

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.

881957

Error in Google Chrome or Microsoft Edge login page when FortiNBI is on.

Workaround: Use Firefox.

975570

Certificate warning when starting up the isolator.

Workaround: Ignore the certificate warning.

Known issues

FortiProxy 7.2.11 includes the known issues listed in this section. For inquiries about a particular bug, please contact Customer Service & Support.

Bug ID	Description
1068729	Wad crashes at wad_http_session_get_from_msg.
913703	Multiple wad processes are in "Dead" state and users cannot access any website that requires proxy.
991280	No FortiGuard firmware updates in GUI. Upgrade can only be done manually by uploading the firmware image file.
998612	FortiProxy cannot display local traffic log.
1005060	Ingress traffic shaper hits a bandwidth throttle that cannot be more than 2.5 Gbps. Workaround: Use egress shaper for better scalability.
1052333	Some categories are missing under System > Replacement Messages in GUI.
1060782	root.b is down and all related routes are missing for standalone FortiProxy in transparent mode. Workaround: Enable active-passive HA on the FortiProxy and ensure hbdev is up. Reboot the FortiProxy and verify that `get sys ha stat` shows the FortiProxy as primary without any warning of hbdev being down.

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.
881957	Error in Google Chrome or Microsoft Edge login page when FortiNBI is on. Workaround: Use Firefox.
975570	Certificate warning when starting up the isolator. Workaround: Ignore the certificate warning.

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.

881957

Error in Google Chrome or Microsoft Edge login page when FortiNBI is on.

Workaround: Use Firefox.

975570

Certificate warning when starting up the isolator.

Workaround: Ignore the certificate warning.

Secure Networking

Hybrid Mesh Firewall

NOC Management

LAN

WAN

Unified SASE

Single Vendor SASE

Cloud Network Security

Secure Endpoint Connectivity

Web Application / API Protection

Security Operations

Security Operations Automation

Identity

Early Detection & Prevention

Secure Networking

Hybrid Mesh Firewall

NOC Management

LAN

WAN

Communication & Surveillance

Unified SASE

Single Vendor SASE

Secure Endpoint Connectivity

Cloud Network Security

Cloud-Native Security

Web Application / API Protection

Security Operations

Security Operations Automation

Endpoint

Data Protection

Identity

Email

Early Detection & Prevention

Expert Services

Edge Firewall

Orchestration & management

SD Branch

Application Delivery

Single Vendor SASE

Secure Endpoint Connectivity

Secure Private Access

Thin Edge

Identity

Application Gateway

Enterprise Asset Management

Endpoint Agent

Agentless Security Posture

Identity

Wireless

Switching

Identity

Privilege Acccess Management

Next Generation Firewall

Orchestration & management

Expert Services

Web Application / API Protection

All

All

Account Management

SAAS Management

SAAS Application Security

Managed Services

Platform as a service (PAAS)

Other SAAS Services

4D Pillars

Cloud

Popular Solutions

All Products

Release Notes

Known issues

FortiNBI

Known issues

Known issues

FortiNBI