could you provide me with more information on that matter for further debugging?
- What flavor and version of Eclipse are you using?
- What version of SonarLint for Eclipse are you using?
- What version does the SonarQube instance have you’re trying to connect to?
- Could you provide me with the verbose console output? (this can be accessed via the Console view → SonarLint Console → check the Verbose output and Analyzer logs via the Gears menu on the top right)
java version “11.0.18” 2023-01-17 LTS
Java™ SE Runtime Environment 18.9 (build 11.0.18+9-LTS-195)
Java HotSpot™ 64-Bit Server VM 18.9 (build 11.0.18+9-LTS-195, mixed mode)
In sonarQube I have changed sonar.search.port=0 and sonar.web.port=9000
In wrapper file → wrapper.java.command=C:\Program Files\Java\jdk-11\bin\java
SonarLint → SonarLint 7.13
Eclipse → eclipse-inst-jre-win64 → Version: 2023-03 (4.27.0)
Starting SonarLint for Eclipse 18.104.22.168073
Started embedded server on port 64120
Starting standalone SonarLint engine 22.214.171.124073…
Node.js could not be automatically detected, has to be configured manually in the SonarLint preferences!
thank you very much for the detailed information! I’ll be checking that on my side and with the SonarQube team, therefore my response will take some time as we try to find the issue and already a solution.
Thanks for your patience!
are you using some form of proxy to connect to your SonarQube instance? Such an error might come from a misconfiguration of a proxy between SonarLint and SonarQube.