It’s working well on my side (Chrome 67.0.3396.99 and Safari 9.0 on Mac OS).
Raw curl seems pretty affirmative too:
n-b-sonar:~ n-b-sonar$ curl -I http://www.sonarcloud.io/ HTTP/1.1 302 Found Date: Wed, 25 Jul 2018 09:36:10 GMT Server: Apache Strict-Transport-Security: max-age=63072000; preload Location: https://sonarcloud.io/ Content-Type: text/html; charset=iso-8859-1
[Fiddler] The connection to ‘www.sonarcloud.io’ failed.
Error: TimedOut (0x274c).
System.Net.Sockets.SocketException A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 220.127.116.11:80
λ nslookup www.sonarqube.io.
Then I tried doing https://www.sonarcloud.io -> works
And now normal http also works…
Something quirky going on here…
Thanks for reporting this issue. I do confirm that there is an incorrect setup on our side.
We are using HSTS for SonarCloud, so as soon as you have connected through https, the HSTS flag is telling your browser to always use https for
sonarcloud.io domain. So the second time you tried to connect, Internet Explorer was automatically redirect you to the https web site without trying to connect to the server.
Yes, I thought so. Thanks for confirming (and hopefully fixing)
And my bad for the confusion ! Didn’t come to mind that setup could look different from the inside network I’m on. Thanks for following-up @Eric_Hartmann.
Problem fixed, HTTP (80) and HTTPS (443) are now enabled, HTTP redirecting to HTTPS