[SOLVED] Scanner.sonarcloud.io domain down, blocking Sonar scans

SonarQube Cloud
1

It appears the scanner.sonarcloud.io domain just went down, preventing scans from running due to the scanner downloading files from that domain. I assume it’s not just us?

15:08:28.859 INFO  Scanner configuration file: /home/runner/work/_temp/sonar-scanner-cli-6.2.1.4610-Linux-X64/conf/sonar-scanner.properties
15:08:28.863 INFO  Project root configuration file: /home/runner/work/ABC/sonar-project.properties
15:08:28.883 INFO  SonarScanner CLI 6.2.1.4610
15:08:28.885 INFO  Java 17.0.12 Eclipse Adoptium (64-bit)
15:08:28.887 INFO  Linux 6.8.0-1020-azure amd64
15:08:28.916 INFO  User cache: /home/runner/.sonar/cache
15:08:29.603 INFO  JRE provisioning: os[linux], arch[x86_64]
15:08:30.970 INFO  EXECUTION FAILURE
15:08:30.971 INFO  Total time: 2.117s
15:08:30.971 ERROR Error during SonarScanner CLI execution
java.lang.IllegalStateException: Call to URL [https://scanner.sonarcloud.io/jres/OpenJDK17U-jre_x64_linux_hotspot_17.0.11_9.tar.gz] failed
	at org.sonarsource.scanner.lib.internal.http.ScannerHttpClient.callUrl(ScannerHttpClient.java:159)
	at org.sonarsource.scanner.lib.internal.http.ScannerHttpClient.downloadFile(ScannerHttpClient.java:90)
	at org.sonarsource.scanner.lib.internal.http.ScannerHttpClient.downloadFromExternalUrl(ScannerHttpClient.java:72)
	at org.sonarsource.scanner.lib.internal.JavaRunnerFactory$JreDownloader.download(JavaRunnerFactory.java:253)
	at org.sonarsource.scanner.lib.internal.cache.FileCache.download(FileCache.java:101)
	at org.sonarsource.scanner.lib.internal.cache.FileCache.getOrDownload(FileCache.java:88)
	at org.sonarsource.scanner.lib.internal.JavaRunnerFactory.getJreFromServer(JavaRunnerFactory.java:143)
	at org.sonarsource.scanner.lib.internal.JavaRunnerFactory.createRunner(JavaRunnerFactory.java:85)
	at org.sonarsource.scanner.lib.internal.ScannerEngineLauncherFactory.createLauncher(ScannerEngineLauncherFactory.java:53)
	at org.sonarsource.scanner.lib.ScannerEngineBootstrapper.bootstrap(ScannerEngineBootstrapper.java:123)
	at org.sonarsource.scanner.cli.Main.analyze(Main.java:75)
	at org.sonarsource.scanner.cli.Main.main(Main.java:63)
Caused by: java.net.UnknownHostException: scanner.sonarcloud.io: Name or service not known
	at java.base/java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
6 Likes
2

We’re experiencing the same issue - thanks for starting this thread!

1 Like
3

Hey @IGx89 and @ValentinVisma

I’ve sounded the alarms. Thanks for the report.

3 Likes
4

We are experiencing the same issue.

5

Hey there.

Our understanding is that a fix has been made, and we are just waiting for the value to propagate. I’ll update you again when we confirm it’s working again.

1 Like
6

Hello. Yep. Same for us. All pipes are blocked.

Execution failed for task ‘:sonarqube’.

java.lang.IllegalStateException: Call to URL [https://scanner.sonarcloud.io/jres/OpenJDK17U-jre_aarch64_mac_hotspot_17.0.11_9.tar.gz] failed

The problem is on the DNS level.

7

Same here

scanner.sonarcloud.io: Name or service not known
8

Hey @IGx89 @ValentinVisma @deepika22 @Sergei_Viskov @Grzegorz_Kuznik

It’s now working again on our side. Can you please verify on your side?

2 Likes
9

https://scanner.sonarcloud.io/jres/OpenJDK17U-jre_aarch64_mac_hotspot_17.0.11_9.tar.gz
Still serves an invalid (self-signed) certificate for me.

1 Like
10

Hey @renefritze

I can’t reproduce that. Can you share a bit more (a screenshot, logs?)

11

Can you provide an ETA on the resolution of this issue ?
We are totally blocked here

12

@lturmelcbq Probalby long as it takes for your local DNS cache to get updated (see instructions here on flushing your cache)

13

image
image879×1155 87.6 KB

That what Firefox shows me when I click on the certificate info on the link which it won’t connect to

14

had same issue but now it works, maybe try again now?

1 Like
15

Can confirm. OK now

2 Likes
16

I can confirm, domain is resolving now. Scan works.

17

Thanks for all the confirmation.

@IGx89 I hope you don’t mind I updated the topic title to indicate this incident has been solved.

1 Like
18

Thanks for the quick response! Confirmed working here too.

19

funny, since we build in the cloud, I doubt it will be efficient to change all pipelines to add this in the build process. My question was more about the TTL on the record… but forget it… i have my anwser

20

The TTL was 300, FWIW.