Walk the causes in order. Stop at the first one that matches.
Send http://%WAF SERVER%/mikiri-waf-test to the Filter itself.
return and never proxies the URL. Filter does not analyze that answer. The URL must fall into a proxied location.waf_host_dm. The event is recorded and the request is not blocked.PATH zone, or the host is in waf_host_wl.waf_product_key or waf_api_url does not reach a valid license and API.The detail is A test request is not blocked.
3 is MLA. Follow Behavioral model false blocks.Nginx on the Filter returns 502 when it cannot connect to the upstream, or when that upstream is not listening. Confirm the address in proxy_pass, then open the connection from the Filter host. The same note is in the troubleshooting section of Web application.
The request never reached Filter, or the host is analyzed and the request was allowed. A direct request to the application address is not analyzed. DNS and the traffic-copy placement are in Getting started.
API writes the event. If the API cannot reach PostgreSQL, new records are not stored. The connection is port 5432, listed in Access and license. Agent errors are in Agent monitoring and in the event log classes of Event log.