Start Free
SonarQube Community Build | Server upgrade and maintenance | Troubleshooting | Other issues

Troubleshooting various issues

On this page

Issues with IIS and SAML integration

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.

Issue with downloading regulatory reports

If nothing happens when you try to download a regulatory report (in the SonarQube Community Build UI at Project Information > Regulatory Report) and your SonarQube Community Build is deployed on Kubernetes, the issue could be your download speed or the report size. To fix this, increase your body size and connection timeout Ingress settings as follows:

annotations:
    cert-manager.io/cluster-issuer: sectigo
    nginx.ingress.kubernetes.io/proxy-body-size: "64m"
    nginx.ingress.kubernetes.io/proxy-connect-timeout: "300"
    nginx.ingress.kubernetes.io/proxy-read-timeout: "300"

Invalid destination error

To help you find out what the issue is, check the valid destination in the log file as follows:

  1. Set the log level to DEBUG.
  2. Check the web.log file for the valid recipient as illustrated below.
Failed to match SubjectConfirmationData@Recipient to any supplied valid recipients: [http://localhost:9000/oauth2/callback/saml]

IIS 10 on Windows: running SonarQube as a service raises an error

If you've secured your SonarQube Community Build instance behind a proxy by using IIS 10 on Windows and the error WinSW.CommandException: Failed to open the service control manager database. Access is denied —> System.ComponentModel.Win32Exception: Access is denied is raised when you try to run SonarQube as a service, try the following:

  • In IIS, disable Dynamic Restriction Settings which come enabled by default under the IP Address and Domain Restrictions feature.  

Was this page helpful?

© 2008-2025 SonarSource SA. All rights reserved. SONAR, SONARSOURCE, SONARQUBE, and CLEAN AS YOU CODE are trademarks of SonarSource SA.

Creative Commons License