Zaproxy: 502 Bad Gateway Errors

Created on 3 Dec 2019 · 3Comments · Source: zaproxy/zaproxy

Describe the bug
I'm seeing a lot of HTTP/1.1 502 Bad Gateway errors when visiting web sites. I'm currently using the pre-configured browser (click on Manual Explore) and visiting https://pentesterlab.com. All the files on the domain assets.pentesterlab.com (such as https://assets.pentesterlab.com/public/css/bootstrap.css) result in 502 Bad Gateway errors. I tried to follow the advice over at https://github.com/zaproxy/zaproxy/wiki/FAQsslHandshake but nothing worked. I don't have an upstream proxy configured in ZAP or on my system

To Reproduce
Steps to reproduce the behavior:

Go to 'Manual Explore'
Set the URL to https://pentesterlab.com
You'll notice that the page does not render properly and the History tab shows 502 Gateway errors

Expected behavior
The requests should be proxied correctly. I tried various things including enabling and disabling SSLv2Hello

Screenshots

screen

Software versions

ZAP: D-2019-12-02
OS: Mac OS X
Java: java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
Browser: Firefox 70.0.1 (64-bit)

Errors from the zap.log file
See https://github.com/zaproxy/zaproxy/wiki/FAQconfig for the location of the zap.log file for your OS.

All I see are entries such as this:

297556 [ZAP-ProxyThread-224] WARN org.parosproxy.paros.core.proxy.ProxyThread - An exception occurred while attempting to connect to: https://assets.pentesterlab.com/public/js/spectragram.min.js The exception was: Received fatal alert: handshake_failure Root cause: SSLHandshakeException: Received fatal alert: handshake_failure The following document may be of assistance in resolving this failure: https://github.com/zaproxy/zaproxy/wiki/FAQsslHandshake

Additional context
Add any other context about the problem here.

third-party

Source