Can't install SonarLint in Eclipse Version: 2021-12 (4.22.0)

Error msg:
Unable to read repository at https://eclipse-uc.sonarlint.org/content.xml.

Stack trace:

javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
	at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:131)
	at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117)
	at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:307)
	at java.base/sun.security.ssl.Alert$AlertConsumer.consume(Alert.java:285)
	at java.base/sun.security.ssl.TransportContext.dispatch(TransportContext.java:180)
	at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:164)
	at java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1152)
	at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1063)
	at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:402)
	at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:436)
	at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:384)
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376)
	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
	at org.eclipse.ecf.provider.filetransfer.httpclient45.HttpClientFileSystemBrowser.runRequest(HttpClientFileSystemBrowser.java:248)
	at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:71)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

Eclipse IDE for Enterprise Java and Web Developers
eclipse.buildId=4.22.0.I20211124-1800
java.version=11.0.4
java.vendor=Amazon.com Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product

Hello @piotr and welcome to the community!

This looks like a network/SSL problem. The update site in your logs is not available, but eclipse actually looks up a lot of files. Logs are a bit misleading because it probably prints last file it tried. Correct link to SonarLint update site is https://eclipse-uc.sonarlint.org/compositeContent.xml and it’s available.
You can check if you can reach this correct link with embedded eclipse browser and your main browser to troubleshoot.
I checked with JRE you are using - Amazon Corretto-11.0.4, and was unable to reproduce. So it’s not an SSL JDK issue. Looks like some kind of networking issue on your side. Try to check firewalls, proxy settings, network monitors and all kind of software that can affect your connection.
Hope it helps.

Hello!

Thanks for reply. I can open https://eclipse-uc.sonarlint.org/compositeContent.xml from embedded in Eclipse and normal browser. I had turned off proxy in Eclipse.
Is it possibility to easy debug this? Any other idea?

Hi,

The next step to debug the issue would be to start Eclipse with SSL debug logs enabled.
See Debugging SSL/TLS connections for details, but in short you should edit eclipse.ini file to add -Djavax.net.debug=all to the VM arguments.

eclipse.ini:

-vmargs
-Djavax.net.debug=all

This should give you very verbose logs in Eclipse logs about SSL connections, and you can try to see what is the issue (missing certificate, wrong truststore, …).