FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
vifi
Staff
Staff
Article Id 343393
Description This article describes how to fix an issue where proxy policies are not shown in the FortiGate web GUI.
Scope FortiGate v7.0 and above.
Solution

Sometimes, proxy policies are not shown in the FortiGate web GUI, yet it is possible to view the policies via the CLI:

 

proxy2.png

 

Restarting the WAD daemon resolves this issue:

 

diagnose test application wad 99

 

Alternatively, the fnsysctl command can be used to send a kill signal to all WAD processes to restart them.

 

fnsysctl killall wad  

 

For more details on how to restart WAD processes, see Technical Tip: How to restart the WAD process.

Performing the activity of killing the WAD daemon will interrupt or even terminate all proxy sessions (explicit or transparent proxy) as well as any traffic going through firewall policies with proxy based inspection.

 

Sometimes it might be required to also restart the httpsd process.

fnsysctl killall httpsd

 

 

Note:

Super Admin privilege is required to run the 'fnsysctl' command. Otherwise, FortiGate will return an error as mentioned in this article: Technical Tip: fnsysctl command returns Unknown action 0.

The command 'fnsysctl' is not available on units with 'FIPS-CC' mode enabled on FortiOS. To verify if FIPS-CC is enabled or not, use the following command:

 

get system status

 

Related article:

Technical Tip: Find and restart/kill a process on a FortiGate by the process ID (PID) via pidof