I installed sonarqube server 8.3.x, sonar scanner 4.7.x, and have Jenkins on same Linux VM. I have the Jenkins plugin for sonar at 2.7.1 on the website. Now everytime I run a build, when it gets to the sonarqube report…it goes into error…saying that it cannot connect with url:9000. I have edited sonar.properties several times…same as package.json as it is a nodejs project…as well as the sonar.js…but it still happens…note that I use VM on AWS and the inbound rules has 9000 already added. Dunno what the problem is
Hi,
Welcome to the community!
Did you really install SonarQube 8.3? Why on earth would you choose a version that old? SonarQube 8.3 is well past EOL. You should upgrade to either the latest version or the current LTA (long-term active version) at your earliest convenience. Your upgrade path is:
8.3 → 8.9.10 → 9.9.6 → 10.6 (last step optional)
You may find these resources helpful:
If you have questions about upgrading, feel free to open a new thread for that here.
If your error persists after upgrade, please come back to us.
Ann
I kinda made a mistake with that title. It is server 18.x, scanner 4.x, plugin 2.7.1…did nmap on my VM today …it didn’t list port 9000…even after allowing on SG and NACL …logs keep saying can’t connect to server…used IP…changed to localhost…same error
| G Ann Campbell ganncamp SonarSourcer
September 26 |
- | - |
Hi,
Welcome to the community!
Did you really install SonarQube 8.3? Why on earth would you choose a version that old? SonarQube 8.3 is well past EOL. You should upgrade to either the latest version or the current LTA (long-term active version) at your earliest convenience. Your upgrade path is:
8.3 → 8.9.10 → 9.9.6 → 10.6 (last step optional)
You may find these resources helpful:
If you have questions about upgrading, feel free to open a new thread for that here.
If your error persists after upgrade, please come back to us.
Ann
Hi,
We’re in the 10-series now, so it’ll be quite some time before 18.x is out.
You can find the server version in your page footer.
Your first step is to access SonarQube in a browser to verify what the URL is. You can then configure that into your Jenkins analysis. If after that you still can’t connect, you need to talk to your network folks.
HTH,
Ann