Hi
@sameer Vidanage,
There can be multiple reasons for that, it can be caused by new ciphers you've implemented recently or changed the mode from Bridge to NGRP, for example.
But here's something that can help:
Reverse Proxy (TRP/KRP): Can't find incident ID in the GUI or "The incident ID is: N/A"
this article has the troubleshooting steps that can help find and fix the issue.
Let me know if that helps,
Ira
------------------------------
Ira Miga
Imperva
Knowledge Engineer
------------------------------
Original Message:
Sent: 06-18-2022 03:11
From: sameer Vidanage
Subject: Incident id N\A in the error logs
Hi Team,
users complain the requested pages has been blocked and it only shows incident id N\A . Need to know how to get the exact incident id instead of N\A
#On-PremisesWAF(formerlySecuresphere)
------------------------------
sameer Vidanage
Lead Engineer
Kelaniya
------------------------------