Failed to connect to

Template for a good bug report, formatted with Markdown:

  • SonarCloud Scanner (SonarQube, Scanner, Plugin, and any relevant extension)
  • Failed to connect to
  • Create a PR which will trigger the SonarCloud Analysis.

The Github Action as well as the CI Integration is failing to connect to the This is delaying production deployment. Can you please let me know when the fix will be available and if there is a workaround.

Sonar-scanner version


1 Like

Same issue here …

Fail to download:
sonarqube_1 | Caused by: Connection refused (Connection refused)

same issue here

1 Like

Yup same issue
Step 17/35 : RUN curl --insecure -o ./ -L
—> Running in 9d7aa11cf165
e[91m % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0e[0me[91m
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
curl: (7) Failed to connect to port 443: Connection refused

Hey all,

Thanks for the report. I’ve raised this internally. Hold tight.


1 Like

This should be resolved now.


Thanks Colin! Yes it is working now

Thanks @Colin Will test out on the CI…

I’m surprised to see that the status on did not change at all. Is there anyway to look into it and minimize the down time?

Hi @Colin… Confirming that the issue is now resolved.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.