And a thorough description of the problem / question:
Plugin stopped working
The Java Runtime Environment can not be located. Please install a JRE, or configure its path with the sonarlint.ls.javaHome property. You can also let SonarQube for VS Code download the JRE from AdoptOpenJDK. This JRE will be used only by SonarQube for VS Code.
Output from plugin
2025-08-18 15:16:43.340 [info] [Error - 15:16:43] SonarLint Language Server client: couldn't create connection to server.
@daulis , @MT_L , @Mideum , just to be clear - do you also see the JRE could not be located error followed by couldn't create connection to server? Could you also share what OS are you on? Do you have sonarlint.ls.javaHome setting configured?
We have not changed anything regarding startup / JRE path detection in the latest release.
Could it be that when you updated, a ‘Universal’ version of the plugin (without embedded JRE) was installed for some reason? To test the theory, you could download the Linux (or your respective platform) VSIX from our releases page, and install it manually to VS Code.
Alternatively, you can check the ~/.vscode/extensions folder to see the the version of the plugin installed, and all the distribution files that came with it. For example, for me on MacOS the folder is ~/.vscode/extensions/sonarsource.sonarlint-vscode-4.29.0-darwin-arm64, and when I check inside it contains the jre folder.
As you see on our releases page, we ship 4 platform-specific packages with embedded JREs, and one universal package without the JRE. Then, it’s up to the VSCode’s plugin update logic to deduce the target platform and install the correct package. I am assuming something went wrong with this service for a short period of time when you updated the plugin, so you ended up with a universal VSIX without the JRE.
2025-08-20 11:02:50.406 [info] [Error - 11:02:50 AM] SonarLint Language Server client: couldn't create connection to server.
2025-08-20 11:02:50.406 [info] [object Object]
I am seeing the same error.
vscode locally development work on by Linux Mint 21.3.
vscode remote ssh development (Rocky Linux 9.5 (Blue Onyx)) cause that error.
I don’t have sonarlint.ls.javaHome configured.
Please notice rolling back to version 4.28.0 on remote ssh machine, everything is working as expected.
After manually setting “sonarlint.ls.javaHome” in Remote[SSH: ] settings.json. It works in remote development.
That is not a requirement in 4.28.0 but in 4.29.0.
I am still guessing that for some reason, at the moment that you updated, VS Code could not correctly determine the target OS and installed a distribution without the embedded JRE. So to fix the issue you will either need to specify sonarlint.ls.javaHome property (which you already did), or download the Linux-specific distribution and install it manually.
Please try to manually upgrade as described here. The reason can be found here.
From the example you provided, the javaHome setting is, I think, incorrect. The sonarlint.ls.javaHome setting needs path to the directory where JRE was installed. Output of where java points to the path to the Java executable.
