I gave a hostname of: sonarqube.local at the https binding and when I go to https://sonarqube.local the URL gets rewritten into the http one that’s running at port 9000.
So far so good. The tricky part is this… while I can access the server over the network from another system by going to the http://:9000 (I asked our network folks to allow traffic through 9000 port) I can’t get through the Sonarqube server if I go to: https://. It gives me “HTTP Error 404. The requested resource is not found.”
If I turn the IIS site off and try to go to the above https link again it actually times out, which makes me believe something is working but not completely, because when I start the IIS site again it goes back to the above 404 message.
Just as an FYI: my network admins confirmed for me that 443 is open at the network, same as 9000.
What am I doing wrong? Please help, somehow it works perfectly on the server itself when I use a browser but not on the network.
Please let me know what other kind of information you might need.
So you mean that if I were to follow the docs link you gave me (it’s the one I already used) http should not be accessible and any requests towards it should get redirected to https as well?
I understand what you mean. I only mentioned the plain HTTP non SSL link as proof that it’s up and running on HTTP and can be accessed, even though we don’t want HTTP.
My question for anyone that might know is if we follow the guide and use “sonarqube.local” as the site name and host name like in the image below, how would I access the server from the network?
