SonarScanner Proxy Failures: Maven Dependencies vs. Server Downloads
Match a Maven repository failure or a SonarScanner server download to the proxy configuration that controls it.
Use the first failed URL to choose the configuration owner:
| Download | Proxy source |
|---|---|
| Maven retrieves the scanner plugin/dependencies | Active settings.xml proxy, repository/mirror and nonProxyHosts |
| The running scanner obtains resources from SonarQube | Supported scanner-specific network settings |
For SonarScanner for Maven 5.0 and later or CLI 6.0 and later, the launching shell/CI environment can supply:
export SONAR_SCANNER_PROXY_HOST=proxy.example.net
export SONAR_SCANNER_PROXY_PORT=8080The property forms are sonar.scanner.proxyHost/sonar.scanner.proxyPort. Use a hostname and explicit separate port, not a full URL or guessed default. An HTTP entry from the HTTP proxy list can fill these fields for an allowed public SonarQube endpoint test only when the actual scanner configuration has no proxy-user or proxy-password settings.
Supply SONAR_SCANNER_PROXY_USER/SONAR_SCANNER_PROXY_PASSWORD through CI credential handling when required. The SonarQube analysis token authenticates another participant.
Keep the analysis URL as the real SonarQube service. The server's Marketplace proxy controls another process, and a successful Maven resolution does not test the scanner's connection. Match settings to the deployed scanner family/version before changing them.