0

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
  • Please elaborate what exactly is "don't get a response". – Tero Kilkanen Mar 19 '17 at 7:42
  • @TeroKilkanen Chrome says "This site cannot be reached". You can visit yourself at 52.176.62.43 – Antarr Byrd Mar 19 '17 at 7:45
  • This means that either there is nothing listening to port 80 / 443, or that there is a firewall blocking connections. – Tero Kilkanen Mar 19 '17 at 13:43
  • @TeroKilkanen This firewall is set to have both 80 and 433 exposed. Caddy is the one listening on those ports. – Antarr Byrd Mar 19 '17 at 14:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.