Sonarqube Not Be Served By Caddy

[atbyrd (Antarr Byrd)]

I’m trying to visit a SonarQube installation I have installed behind the Caddy web server. When I visit the site I don’t get a response. I’ve tried proxying 8999(secure) and 9000(unsecure) with Caddy.

Caddyfile

https://52.176.62.43 {
  tls self_signed
  gzip
  proxy /  127.0.0.1:8999
}

http://52.176.62.43 {
  tls off
  gzip
  proxy / 127.0.0.1:9000
}

sonar.properties

# 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.
# By default, ports will be used on all IP addresses associated with the server.
sonar.web.host=127.0.0.1

# Web context. When set, it must start with forward slash (for example /sonarqube).
# The default value is root context (empty value).
#sonar.web.context=
# TCP port for incoming HTTP connections. Default value is 9000.
#sonar.web.port=9000
sonar.web.https.port=8999

curl

curl -I https://52.176.62.43/
curl: (7) Failed to connect to 52.176.62.43 port 443: Operation timed out

[matt (Matt Holt)]

What happens if you’re not proxying the connection (i.e. just serving static files)? Are you sure your system is configured properly?

[atbyrd (Antarr Byrd)]

It behaves the same

localhost:80 {
  tls off
  gzip
  root /opt/sonar/web
  # proxy / 127.0.0.1:9000
}

[atbyrd (Antarr Byrd)]

@matt If you visit the site, http://52.176.62.43/, it does seem to load a certificate.

[matt (Matt Holt)]

I’m not having any connectivity to it. I suspect your network isn’t properly configured or something.