Other issues

Troubleshooting other issues related to the server updates and maintenance.

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 Using IIS on Windows section.

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. See Server logs for more information.

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.

SonarQube on AWS ECS: startup fails with unknownhostexception

If your SonarQube, installed on AWS ECS, fails to start up with unknownhostexception, try the following:

• Check if the ECS container is running in network bridge mode and change it to host mode.

Related pages

• Server logs

• Performance issues

• Database-related issues

• Elasticsearch-related issues