Connecting SonarQube to internal JIRA server without proxy

Other Questions Jira
1

I’m having trouble getting the SonarQube JIRA plugin to work with our company’s internal JIRA server. Our network setup requires all external connections to go through a proxy. But our JIRA is hosted internally at http://ourjira.

When I use my web browser, I can add the JIRA hostname to a list of exceptions that don’t use the proxy. Is there a way to do something similar in SonarQube?

I’ve tried looking through the SonarQube settings, but I can’t find anything about proxy exceptions or ignoring specific hostnames. Has anyone else run into this issue before? Any tips on how to configure SonarQube to connect directly to our internal JIRA without going through the proxy would be really helpful.

Thanks in advance for any advice!

2

hey lucask, i’ve dealt with similar setup before. try adding ‘http.nonProxyHosts=ourjira’ to sonar.properties file. restart sonarqube after. if that dont work, check ur network config to allow direct connection to internal JIRA. hope this helps!

3

As someone who’s worked extensively with SonarQube in various network environments, I can share a trick that often resolves this issue. Have you considered using environment variables to set the non-proxy hosts? You can add this to your SonarQube startup script:

export SONAR_JDBC_JDBC_URL=“jdbc:h2:tcp://localhost:9092/sonar”
export JAVA_ADDITIONAL_OPTS=“-Dhttp.nonProxyHosts=ourjira ${JAVA_ADDITIONAL_OPTS}”

This approach has the advantage of not requiring changes to the sonar.properties file, which can be overwritten during updates. It’s also more flexible if you need to adjust settings frequently.

Remember to restart SonarQube after making these changes. If you’re still having trouble, it might be worth checking if there are any firewall rules or network policies preventing direct communication between SonarQube and your internal JIRA server.

4

I encountered a similar situation when setting up SonarQube in our internal network. One solution that worked for us was configuring the JVM arguments for SonarQube. You can add the following to your sonar.sh or wrapper.conf file:

-Dhttp.nonProxyHosts=ourjira

This tells Java to bypass the proxy for the specified host. Make sure to adjust ‘ourjira’ to match your internal JIRA server’s exact hostname.

Additionally, verify that SonarQube can resolve the internal JIRA hostname. You might need to add an entry to the hosts file on the SonarQube server if DNS resolution isn’t working correctly.

If these steps don’t resolve the issue, you may need to involve your network team to ensure there are no firewall rules blocking direct communication between SonarQube and JIRA.