Hello @wolfgang_hafelinger
Unfortunately I can’t be much more helpful than this conclusion you made:
Rather, I start to believe it may due to proxy availability (authorized to proxy) and or VPN availability or not.
It looks like due to some problem related to SSL configuration, we can’t decrypt the JSON we expect to get from the SonarQube Server/Cloud you connected to. And that’s why there’s a message about malformed JSON. It looks like it’s just a decryption error we trying to parse as JSON. Maybe we can improve the logging here. So since synchronization with server is not finished we can’t perform the analysis. That’s why you see this message:
Analysis skipped as the engine is not ready yet
So root cause it SSL configuration.
Just making sure you seen this page:
Normally, if you use traffic encryption - SonarQube for IDE should be able to pick up operating system settings and JVM configuration for IntelliJ. So if your IntelliJ is able to connect to the internet (for example open Marketplace, download and install plugins), then SonarQube for IDE should work alright as well. Assuming you don’t have some advanced config that makes situation a bit more complex.
So first step to troubleshoot would be to test if IntelliJ works fine with network. And if not - try to find misconfigured stuff like certificates and proxy settings.
If IntelliJ network related features works alright while SonarQube IDE doesn’t I would suspect you have some advanced settings enabled that makes SonarQube IDE using different JVM than IntelliJ itself.
Sorry for the late response.
Best,