Troubleshooting the installation
Double-check that settings for proxy are correctly set in
<sonarqubeHome>/conf/sonar.properties. Note that if your proxy username contains a backslash, then it should be escaped; a username
domain\user in the file should look like this example:
For some proxies, the exception
java.net.ProtocolException: Server redirected too many times might mean an incorrect username or password has been configured.
SonarQube starts an Elasticsearch process, and the same account that is running SonarQube itself will be used for the Elasticsearch process. Since Elasticsearch cannot be run as root, that means SonarQube can't be either. You must choose some other, non-root account with which to run SonarQube, preferably an account dedicated to the purpose.
When reporting Quality Gate status to DevOps platforms, SonarQube uses a DNS cache time to live policy of 30 seconds. If necessary, you can change this setting in your JVM:
Please be aware that low values increase the risk of DNS spoofing attacks.
When running in an environment where the DevOps platform or other related tooling is secured by self-signed certificates, the CA needs to be added to the java truststore of SonarQube.
In a zip installation, the systems truststore can be found in
$JAVA_HOME/lib/security/cacerts. In order to add a new certificate to the truststore you can use the following command as an example:
In our official Docker images, you can find the systems truststore in
<JAVA_HOME>/lib/security/cacerts. In order to add new certificates here as well you can:
- Bind mount an existing truststore containing your certificates to
- Import your CA certificate the same way as in the zip installation but inside the container.
If you deploy SonarQube on Kubernetes using the official Helm Chart, you can create a new secret containing your required certificates and reference this via:
If you are using an IIS reverse proxy with SAML authentication, you may encounter one of the following issues:
- The URL redirection to the SAML Identity Provider (sonar.auth.saml.loginUrl) is not managed correctly.
- "You are not authorized to access this page" error is raised when logging in.
In that case, make sure that, at the IIS server level, you have performed all the configuration steps described in the section Securing the server behind a proxy>Using IIS on Windows in Operating the server.
© 2008-2023, SonarSource S.A, Switzerland. Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution-NonCommercial 3.0 United States License. SONARQUBE is a trademark of SonarSource SA. All other trademarks and copyrights are the property of their respective owners.