WAF anormaly

Hi Service Informatique2,

You have to allow the id  as per the log on policy if the ID does not come out, put the WAF service in debug from the advanced shell.

service WAF:debug -ds nosync

Check the logs again from log viewer or from the /log/reverseproxy.log and you should see more information from the log since the service is in debug mode.

To disable the debug, please run the command again.

For more information refer the below link : 

https://support.sophos.com/support/s/article/KB-000036242?language=en_US 

and 

https://support.sophos.com/support/s/article/KB-000035562?language=en_US 

Thanks and Regards

Hello, I've tried your command, but I have this result :

SFOS 18.0.6 MR-6-Build655# service WAF:debug -ds nosync
400 Bad Request

Hi  Service Informatique2 ,

Please check the below steps and share the output : 

• Check that the WAF is running: # service WAF:status -ds nosync
• Do a manual restart of WAF: # service WAF:restart -ds nosync
• Record the error messages in the logs if reverseproxy cannot start.
• Check if the network socket is created for the WAF (netstat natup | grep httpd).
• Verify that no other service is running on Port 80 or 443 in the UTM.

• Check if the WAF is running correctly on Port 80: # netstat natup |grep :80
• Check that the service is running: # service WAF:status -ds nosync
• Start/Restart/Stop: # service WAF:<start/restart/stop> -ds nosync
• View Live Log: # tail –f /log/reverseproxy.log

Thanks and regards

Hello, thanks for your support.

WAF is running well.

I can't restart WAF because we are in a production environnement and so I can't have any downtine.

Waf is running correctly on Port 80

And I have many many logs in reverseproxy.log

I've downloaded a copy of reverseproxy.log to see if I have more information about the false positive Waf anomaly.

Hello, thanks for your support.

WAF is running well.

I can't restart WAF because we are in a production environnement and so I can't have any downtine.

Waf is running correctly on Port 80

And I have many many logs in reverseproxy.log

I've downloaded a copy of reverseproxy.log to see if I have more information about the false positive Waf anomaly.