which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
what are you trying to achieve
what have you tried so far to achieve this
Hi,
we are using SonarQube Version 6.7.5 (build 38563) and since some weeks we are not able to open the License Manager section. Using an administrative account, if we try to open the License Manager section (Configuration -> License Manager) the system returns the a blank page:
Could you check in SonarQube logs if there is any error that could explain this behavior?
Pay specific attention to {{sonar.log}} and {{web.log}} for this.
If there is no error, then use the development tool of your web browser (usually you just have to press F12) and then reload the page.
Do you see any useful error/information in network or console section?
If I were you I would check the URL is working accessing it via my web-browser. I would also try to find this query in SonarQube access.log while loading the license manager page and while accessing the js file directly.
If you do not see this 404 error in the access.log, it could mean problem is coming from the reverse proxy that is redirecting queries from you intranet host to SonarQube.
I would then have a look there too.
In your access.log there is no call to static/license/app.js. As an example here is the log entry I have in my access.log when accessing the same page than you on my 6.7.5 SonarQube server:
If problem was that SonarQube could not serve the app.js, you would get an entry with an error 404.
Here there is no trace at all of this call. It means that the query did not reached SonarQube.
You are connecting to SonarQube is http://sonar.intranet.ifis.local. This means that there is a reverse-proxy that re-route queries between sonar.intranet.ifis.local and the URL of SonarQube that should look like <SonarQube-server-host>:<SonarQube-port>.
I recommend you to access SonarQube directly using http://<SonarQube-server-host>:<SonarQube-port> (without using the reverse-proxy). Open the License Manager page and if you are not reproducing the problem, it means something get wrong in the redirection and prevent the page to be loaded. You should then dig into your reverse-proxy configuration.
Nothing shows that the problem is coming SonarQube based on the information you provided.