The SonarQube Marketplace Needs the Server’s Proxy Route

Marketplace and update checks leave from SonarQube, so configure the installation's supported sonar.properties inputs:

http.proxyHost=proxy.example
http.proxyPort=8080
https.proxyHost=proxy.example
https.proxyPort=8080

Merge the values and perform a full restart of the main service through its supported lifecycle. The supplied sample warns that api/system/restart does not reload this file.

Hosts are bare names/addresses with ports separate. HTTPS properties select HTTPS destinations, not a demand for another proxy listener protocol. Omitted HTTPS host/port default to the HTTP values in the documented configuration; explicit entries matter when routes differ. An HTTP address from the HTTP proxy list can fill these fields for allowed public Marketplace downloads only when no http.proxyUser or http.proxyPassword is configured.

Where authentication is required, the reference's http.proxyUser/http.proxyPassword cover HTTP, HTTPS and SOCKS proxies. Use the intermediary account rather than the SonarQube administrator login.

After restart, keep the actual failed server-side URL and error. Update information and selected plugin artifacts can use different hosts. The administrator's browser reaching another site does not establish that the proxy permits this download.