It prints an error: This request has been blocked; the content must be served over HTTPS.
if I add https, I get error: ERR_SSL_PROTOCOL_ERROR
Is that an issue from our gitlab server? I assume thats something you will not be able to help us with? Is there any way to setup this to work with https?
I’m not sure if that’s coming from your browser or GitLab itself. In any case, serving your SonarQube server over HTTPS is a good practice. We do offer some documentation to get you started – but you should use whatever is most commonly used in your org (Nginx, Apache, IIS…)
It is not really similar. SonarQube requires users to set up their own “infrastructure”, like a standard reverse proxy, to manage HTTPS for the SonarQube server. Most users are already doing this in order to visit their SonarQube server over http://sonarqube.foo.com rather than http://sonarqube.foo.com:9000.
In the past, SonarQube functioned more like Grafana does. The downside to that approach was that whenever a vulnerability was found in the embedded proxy, users had to wait for a new version of SonarQube to be released, rather than being able to update the software on their own.