SonarQube 5.3 - Download plugins behind proxy (HTTPS)

0
votes

There are a couple of questions about this already, but none of the provided solutions work with SonarQube v5.3.

So far I've tried setting sonar.web.javaAdditionalOpts=-Dhttps.proxyHost=proxy.XXX -Dhttps.proxyPort=YYY, both http(s).proxyHost=proxy.XXX and http(s).proxyPort=YYY.

It's important to notice that when SonarQube is starting (I'm running the docker app) it tries to connect to http://update.sonarsource.org/update-center.properties, in which case I'm able to check that http proxy works:

sonar_1 | 2016.02.29 20:46:18 INFO  web[o.s.s.p.UpdateCenterClient] Update center: http://update.sonarsource.org/update-center.properties (HTTP proxy: proxy.XXX:YYY)

But, when trying to download any plugin from Update Center, it fails:

sonar_1 | org.sonar.api.utils.SonarException: Fail to download the plugin (ldap, version 1.5.1) from https://sonarsource.bintray.com/Distribution/sonar-ldap-plugin/sonar-ldap-plugin-1.5.1.jar (error is : Fail to download: https://sonarsource.bintray.com/Distribution/sonar-ldap-plugin/sonar-ldap-plugin-1.5.1.jar (no proxy))

Any help is much appreciated.

EDIT: Adding relevant debug logs according to the configuration been used.

  • Using only sonar.web.javaAdditionalOpts=-Dhttps.proxyHost=http://proxy.XXX -Dhttps.proxyPort=YYY -Dhttp.proxyHost=proxy.XXX -Dhttp.proxyPort=YYY: gist

  • Using http.proxyHost, http.proxyPort, https.proxyHost and https.proxyPort: gist

1
configurationproxysonarqubesonarqube5.3
General guidelines aside, to focus on a precise issue: can you set http.proxyHost/Port and https.proxyHost/Port in sonar.web.javaAdditionalOpts , switch sonar.log.level to DEBUG and share some more logs of the failure ? - Nicolas B.
@n_stan sure, I'll edit my post. - resilva87

1 Answers

1
votes

The HTTPS proxy properties (https.proxyHost and https.proxyPort) must be set in sonar.web.javaAdditionalOpts because they are not understood/suppoerted in sonar.properties.

The HTTP proxy properties (http.proxyHost and http.proxyPort) can be set either in sonar.web.javaAdditionalOpts or in sonar.properties directly.

Careful though: if you set the HTTP ones in sonar.web.javaAdditionalOpts, make sure to comment out the http.proxyHost and http.proxyPort lines in sonar.properties. Otherwise the latter would override the former (and I feel like this is what might be happening in your gist1 ).

Edit: you're running SonarQube in a docker container, in which case sonar.web.javaAdditionalOpts are currently set in the run.sh script. For additional Java properties you'll have to modify this directly.