Error binding workspace

Sonarlint.txt (13.0 KB)

Is it compatible for both sonarqube and sonarlint if I will install java 7?

Hello, thanks for the additional logs.

Could you please open a separate thread for your question about Java versions? Let’s try to focus on proxy settings on this thread.

I noticed in the user settings you shared that you used the following:

"": "-Dhttps.proxyHost= -Dhttps.proxyPort=3128 -Dhttps.nonProxyHosts=localhost||"

As far as I can tell, https.nonProxyHosts is not a property supported by the Java network stack.

Could you please try with http.nonProxyHosts instead?

Additionally, could you please check what happens if you don’t set any proxy-related configuration?

Hi Jean,

I’ve tried to change the proxy host to below configuration. But as tested the same error occured.

“”: “-Dhttp.proxyHost=http://9.208.xxxx.xx -Dhttp.proxyPort=3128 -Dhttp.nonProxyHosts=localhost||”,

This is the error that i am seeing. without proxy cofiguration.

[Error - 10:17:00.228] org.apache.hc.client5.http.HttpHostConnectException: Connect to [,] failed: Connection timed out: no further information
at java.base/ Method)
at java.base/ Source)
at java.base/ Source)
at org.apache.hc.core5.reactor.InternalConnectChannel.onIOEvent(
at org.apache.hc.core5.reactor.InternalChannel.handleIOEvent(
at org.apache.hc.core5.reactor.SingleCoreIOReactor.processEvents(
at org.apache.hc.core5.reactor.SingleCoreIOReactor.doExecute(
at org.apache.hc.core5.reactor.AbstractSingleCoreIOReactor.execute(
at java.base/ Source)

[Debug - 10:17:00.228] Cannot connect to server event-stream, retrying in 120s

I have tried to test the connection without proxy and it went successful. Obviously the issue here is the proxy settings.

Hey, thanks for the additional info.

Could you please clarify what you mean by:

If the connection is successful without proxy settings, why try to set proxy settings in the first place?

As far as I can tell, if the only exception that you see in the logs is the one about the server event stream, then connected mode should mostly work fine, with the exception that changes on the server (e.g. changes in quality profile, transitions on issues) won’t be reflected immediately in the IDE.

Hi Jean,

It’s because our environment setup is using proxy settings for Sonarqube. Is the sonarlint compatible with connectinng with proxy? As it is the only issue here

Please let me know if you have any idea on the fix it would help.

Hello, at this stage we still don’t have any idea about what is going on: the exception message - Connection timed out: no further information - does not give much information to work with.

These kinds of issues are very hard to investigate because we cannot reproduce the exact environment that you have in terms of proxy settings, network routes, etc.

As far as I can tell, users on this community forum have been able to configure connected mode with a proxy in SonarLint for VSCode.

Could you please confirm that the proxy settings that you configured allow your development environment to reach the SonarQube server?

For instance, you could check that the server’s status API can be queried with the following:

curl --verbose --proxy 'http://9.xx.xx.xx:3128' ''

If it is successful, it will return a JSON object with the server’s status and version. If not, the --verbose option should tell us more about what may be going on.

For the users who are able to configure sonarqube connected mode which proxy configuration did they used vscode as well?

We need to proceed by elimination to get to the root cause of the issue. So I would like to first understand whether the proxy settings that you are trying to use are valid for your network setup.

My line of thought is that if these proxy settings don’t work with another standard tool (like curl), there is no chance that they would work with SonarLint.

Can you please try the troubleshooting command I suggested above?

Hi Jean,

Below is the output of the command curl --verbose

root@DESKTOP-DEM92U2:/mnt/c/Users/BB23V7JPM/Desktop# curl --verbose --proxy '' ''
*   Trying
* Connected to ( port 3128 (#0)
* allocate connect buffer!
* Establish HTTP proxy tunnel to
> Host:
> User-Agent: curl/7.68.0
> Proxy-Connection: Keep-Alive

Hello, thanks for the additional information.

If this is the only output that curl gives, I believe that the root cause of the issue is that this particular proxy does not permit access to your SonarQube server from your development environment.

My suggestion is that you first find proxy settings that allow curl to get an answer from the SonarQube server, and then we can have a look at how to tell SonarLint to use these working proxy settings.

Hi Jean,

Thank you for your feedback, but considering the result of the curl command isn’t it the connection is working from my local to proxy sonarqube. Because I can see connected status to proxy

If the proxy settings were correct, a call to api/system/status would return a JSON object like this:


I don’t see this in the output from curl that you shared above.