Summary

Log Analyzer fails to run when reverse proxy is configured

Environment

FishEye/Crucible 4.2.1+ with a Reverse Proxy Configured with:
Administration > Server > Web Server the following:

• Proxy Scheme
• Proxy Port
• Proxy Host

Steps to Reproduce

1. Set up Reverse Proxy
2. Configure Administration > Server > Web Server :

• Proxy Scheme
• Proxy Port
• Proxy Host

1. Run Log Analyzer using any of the 3 settings in the dropdown menu

Expected Results

The logs should get scanned

Actual Results

The logs don't get scanned and you automatically get the following message:
Hercules didn't find any known problems in the following log file:
<path to file>
This happens without scanning the logs

Workaround

Option 1

1. If FishEye is running Java 8u111+
2. Add the following to the FISHEYE_OPTS:

   -Djdk.http.auth.tunneling.disabledSchemes="" 
   

Note: see related Basic authentication fails for outgoing proxy in Java 8u111 article

If this workaround does not help, see FE-6966.

Option 2
You can set up another instance of Fisheye/Crucible
that does not have a proxy and point the Log Analyzer
to your proxied instance.