Log Analyzer fails to run when reverse proxy is configured in FishEye / Crucible
Log Analyzer fails to run when reverse proxy is configured
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:
Steps to Reproduce
Set up Reverse Proxy
Configure Administration > Server > Web Server :
Run Log Analyzer using any of the 3 settings in the drop-down menu
The logs should get scanned
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:
You can set up another instance of Fisheye/Crucible that does not have a proxy and point the Log Analyzer to your proxied instance.
Check that you running Java 8u111+
If yes, then add to Java environment:
See related KB: Basic authentication fails for outgoing proxy in Java 8u111
Atlassian applications with a Reverse Proxy Configured
This has been fixed in Support Tools Plugin 4.0.2 and Atlassian Troubleshooting & Support Tools Plugin 1.8.3.
I split the
problem into a separate issue ATST-839.
The problem appears to be we're trying to fetch the reverse-proxy config rather than the outbound proxy config.. Reverse-proxy isn't supposed to matter as the log scanner makes outbound calls rather than hitting the instance itself