URL for "Link to Homepage" in Navbar goes to wrong URL

Must-share information (formatted with Markdown):

  • which versions are you using:
    • Developer Edition - Version 10.0 (build 68432)
  • how is SonarQube deployed:
    • Docker, AWS ECS
  • what are you trying to achieve
    • Clicking the “SonarQube” Logo in the navbar takes me to the correct page.
  • what have you tried so far to achieve this
    • Navigate settings for a way to change this URL.

My server is hosted at: https://platform.<domain.com>/sonar. Everything works as expected, however when clicking the “SonarQube” logo in the navbar, it navigates to https://platform.<domain.com> (dropping the /sonar path)

This is the “SonarQube” logo in the navbar I am referring to:

I am running the service in Docker on AWS ECS Fargate behind an AWS ALB. I run the service with the following configuration item passed in to the command: -Dsonar.web.context=/sonar

In the SonarQube settings, I have the following set for my Server base URL: https://platform.<domain.com>/sonar (sonar.core.serverBaseURL)

Where can I change this setting or control this behavior?

Hey there.

That’s interesting – we don’t experience that on our own internal instance https://next.sonarqube.com/sonarqube/.

I’m not sure this is doing anything. Can you try using environment variables, which is how we reccomend passing this configuraiton in a Docker environment?

1 Like

Sure, I have updated my service to use SONAR_WEB_CONTEXT environment variable set to /sonar and do not see different behavior.

Hey @Colin, do you have any further advice or documentation to reference?

Hey there.

It looks like this was just reported as a bug (specific to 10.0) internally. My fault for not passing this onto the right team earlier and assuming it was misconfiguration!

I’m sure a ticket will get created soon – I’ll keep you posted.

A ticket has been created which is targeted for SonarQube 10.1!


Thanks so much! I’ll keep an eye out for the next release!

Hey @Colin ,

I can’t see that Jira issue but saw that 10.1 was released, can you confirm that issue was included as part of the 10.1 release?

Phillip Ferentinos

I don’t know what happened to the Jira ticket – but I can confirm it is included in 10.1.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.