Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Running ZAP in daemon mode on an EC2 instance with -host the all-interfaces address and then pointing a browser at the instance's public IP and port makes ZAP unresponsive with ZAP Error [java.net.SocketTimeoutException]: Read timed out. The root cause the reporter found: ZAP listens on all interfaces, sees the incoming request to its own public IP as a request to proxy, forwards it to itself, and loops until it runs out of memory.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
The immediate workaround that worked: put nginx in front of ZAP as a reverse proxy and access ZAP through it instead of hitting the daemon port directly. The diagnosis, requests to ZAP's own public address being proxied back into itself, is the thing to remember if you run ZAP bound to the all-interfaces address on a cloud VM.
Source: https://github.com/zaproxy/zaproxy/issues/2318
Shows how to fix zAP Error java.net.SocketTimeoutException: Read timed out running ZAP daemon on AWS EC2. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes docker run failing with 'Error response from daemon: Conflict.
Fixes the synthetic data agent workflow failure agent timed out running privacy evaluation on a large generated dataset by applying the specific fix in the steps, proving it on one small scope first, then rerunning and reconciling counts.