We're updating the issue view to help you get more done. 

Log Analyzer fails to run when reverse proxy is configured in FishEye / Crucible

Description

Summary

Log Analyzer fails to run when reverse proxy is configured

Environment

Atlassian applications (e.g. FishEye/Crucible 4.2.1+, Bitbucket Server 5.+ or JIRA) 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 drop-down 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

Another possible error:

Workaround

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

Fix

  1. Check that you running Java 8u111+

  2. If yes, then add to Java environment:

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

    See related KB: Basic authentication fails for outgoing proxy in Java 8u111

Environment

Atlassian applications with a Reverse Proxy Configured

Testing Notes

None

Status

Assignee

Unassigned

Reporter

Sauce

Labels

None

Add-on Type

Server

Team

None

CC

None

Risk factor

None

QA Kickoff Status

None

QA Demo Status

None

Affected Product/s

FishEye / Crucible

Fix versions

Priority

Major