Hi Jose,
First of all it seems you’re misunderstanding the purpose of sonar.web.host. It’s meant to be an IP address, corresponding to the network interface on which SonarQube would listen:
Binding IP address. For servers with more than one IP address, this property specifies which
address will be used for listening on the specified ports.
I recommend keeping the default value for now.
Secondly there’s no need to listen on port 443. Yes that is the default port for HTTPS, however it’s your nginx proxy who’s going to listen on 443. Then the communication between proxy and SQ can happen on any port, e.g. default 9000. Not to mention that SonarQube does not support being run as root, so it can’t listen on port 443.
Last but not least as Ann mentioned, don’t forget that you’ve set sonar.web.context.
My advice:
- fix the above, notably
sonar.web.host - start SonarQube and verify that locally (from the same machine where SonarQube is running) you can query SonarQube via
localhost - then query via your proxy and trace down the request (e.g. proxy logs) if any trouble