I’m having trouble setting up the JIRA integration in SonarQube because our internal JIRA instance can’t be reached properly.
Our corporate network requires all external connections to go through a proxy server. However, our JIRA system runs on our internal network at something like http://internal-jira-server.
When I configure my web browser, I have to add the internal-jira-server hostname to the proxy bypass list so it connects directly instead of going through the proxy.
Is there a way to configure SonarQube to skip the proxy when connecting to our internal JIRA server, similar to how browser proxy settings work?
Any help would be appreciated.
yeah, try setting the http.nonProxyHosts Java system property in your SonarQube startup script or wrapper.conf. just add -Dhttp.nonProxyHosts=internal-jira-server to the JVM options. fixed the same issue for me with our internal systems.
To configure SonarQube to bypass the proxy for your internal JIRA server, you need to set the http.nonProxyHosts property. This can be done by adding it to your sonar.properties file or passing it as a JVM argument like -Dhttp.nonProxyHosts=internal-jira-server|*.internal.domain. Make sure to replace internal-jira-server with your actual JIRA hostname or IP address. After making this change, don’t forget to restart SonarQube to apply the new settings, which functions similarly to proxy bypass configurations in web browsers.
Had this exact problem setting up our SonarQube environment last year. The http.nonProxyHosts property works, but there’s one gotcha that might save you some headaches. When you specify the internal hostname, use the exact same format SonarQube will use when connecting. We had to include both the short hostname and the FQDN because different parts of the integration were resolving the server name differently. Also check your SonarQube logs after restart to confirm it’s connecting directly and not timing out on proxy attempts. The connection errors are usually pretty clear about whether it’s still trying to route through the proxy or hitting the internal server directly.