Proxy, SonarCloud, OpenShift, Tekton

Hi all,

I’m evaluating SonarCloud and try to run an analysis through a corporate proxy. I have tried analysis with two methods:

I have tried configure proxy with JAVA_OPTS, SONAR_SCANNER_OPTS, SONAR_RUNNER_OPTS, but nothing helped

Environment setup

Tekton Pipelines in OpenShift - tekton task Tekton Hub with sonarqube mounted via ConfigMap
Java 17

Full Stack trace Maven

[ERROR] Error resolving version for plugin 'verify org.sonarsource.scanner.maven:sonar-maven-plugin' from the repositories [local (/workspace/maven-settings), central (]: Plugin not found in any plugin repository -> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1]

Full Stack trace sonar-scanner file

bash-5.1$ sonar-scanner -X 
14:17:20.506 INFO: Scanner configuration file: /usr/src/
14:17:20.508 INFO: Project root configuration file: /usr/src/
14:17:20.533 INFO: SonarScanner
14:17:20.533 INFO: Java 11.0.14 Alpine (64-bit)
14:17:20.533 INFO: Linux 4.18.0-372.69.1.el8_6.x86_64 amd64
14:17:20.648 DEBUG: keyStore is : 
14:17:20.648 DEBUG: keyStore type is : pkcs12
14:17:20.648 DEBUG: keyStore provider is : 
14:17:20.648 DEBUG: init keystore
14:17:20.648 DEBUG: init keymanager of type SunX509
14:17:20.736 DEBUG: Create: /opt/sonar-scanner/.sonar/cache
14:17:20.736 INFO: User cache: /opt/sonar-scanner/.sonar/cache
14:17:20.737 DEBUG: Create: /opt/sonar-scanner/.sonar/cache/_tmp
14:17:20.738 DEBUG: Extract sonar-scanner-api-batch in temp...
14:17:20.741 DEBUG: Get bootstrap index...
14:17:20.741 DEBUG: Download:
14:17:40.829 ERROR: SonarCloud server [] can not be reached
14:17:40.830 INFO: ------------------------------------------------------------------------
14:17:40.830 INFO: ------------------------------------------------------------------------
14:17:40.830 INFO: Total time: 20.331s
14:17:40.845 INFO: Final Memory: 14M/1979M
14:17:40.845 INFO: ------------------------------------------------------------------------
14:17:40.845 ERROR: Error during SonarScanner execution
org.sonarsource.scanner.api.internal.ScannerException: Unable to execute SonarScanner analysis
        at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.lambda$createLauncher$0(
        at java.base/ Method)
        at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.createLauncher(
        at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.createLauncher(
        at org.sonarsource.scanner.api.EmbeddedScanner.doStart(
        at org.sonarsource.scanner.api.EmbeddedScanner.start(
        at org.sonarsource.scanner.cli.Main.execute(
        at org.sonarsource.scanner.cli.Main.main(
Caused by: java.lang.IllegalStateException: Fail to get bootstrap index from server
        at org.sonarsource.scanner.api.internal.BootstrapIndexDownloader.getIndex(
        at org.sonarsource.scanner.api.internal.JarDownloader.getScannerEngineFiles(
        at org.sonarsource.scanner.api.internal.IsolatedLauncherFactory.lambda$createLauncher$0(
        ... 7 more
Caused by: connect timed out
        at java.base/ Method)
        at java.base/
        at java.base/
        at java.base/
        at java.base/
        at java.base/

Any help would be great, thank you!


Welcome to the community!

This is a pure proxy problem. Maven can’t get to the central repo to download what it needs to run analysis. You should talk to your network folks.

For the sonar-scanner error, the docs suggest adding our domains to your proxy whitelist.


I agree, the error indicates a problem with the proxy, but don’t know where to look for cause.

When run curl command with proxy to it is working correctly. I’ve seen in this topic: Sonar-scanner-maven does not work with HTTP (not HTTPS) PROXY authentication that sonar-maven plugin does not work with proxy settings, isn’t that right?

Regarding the sonar-scanner I got reply from network team that is allready whitelisted. Is there other option I can set/provide to sonar to enable connection or am I missing something?

Thanks for quick reply,

Hi Oskar,

We try to keep it to one topic per thread. Otherwise it can get messy, fast. So let’s talk about Maven here.

The topic you refer to repeatedly asserts that it does work and points out how to make it work.

Are you running that command from the build agent or from your localhost?


Good morning Ann,

True it’s better to keep one topic per thread.

The command is run from build agent and checked and we have proxy settings provided in .m2/settings.xml.
I have run also couple of tests with MAVEN_OPTS, but it didin’t helped


My question was about the curl command you said was successful. Did you run that successful curl command from your localhost or from the build agent?


Successful curl command is run from build agent


Hi Oskar,

Thanks for the confirmation. Now, going back to that thread you found, this post details how the user worked with his proxy:

Additionally, the Maven docs tell you how to configure a proxy.


Hi Ann,

The post above is not helpful for me, it describes authentication keys, which I don’t need :neutral_face: I’ve run couple of tests again with configured and mounted proxy settings in maven setttings.xml file to our pipeline, but I got the same error as before regarding proxy

Error resolving version for plugin 'verify org.sonarsource.scanner.maven:sonar-maven-plugin' from the repositories [local (/workspace/maven-settings), central (]: Plugin not found in any plugin repository -> [Help 1]

Do you have any ideas, how we can check if we are trying to connect by provided proxy or if there are other options how to provide proxy settings to maven to?


Hi Oskar,

Sorry, but I’ve given you what I’ve got. You really need to dig into this with your network folks and with Mavenistas.


Hi Ann,

Thank you for your commitment and time, I will talk to the proxy team again


1 Like