ERROR Sonar server http localhost 9000 can not be reached

Question

when running the following command  cmd  c C  sonar-runner-2 4 bin sonar-runner bat   sonar runner is installed on the build machine  i get the following errors  ERROR  Sonar server  http   localhost 9000  can not be reached ERROR  Error during Sonar runner execution ERROR  java net ConnectException  Connection refused  connect ERROR  Caused by  Connection refused  connect    what can cause these errors   Hi dinesh   this is my sonar-runner properties file   sonar projectKey NDM sonar projectName NDM sonar projectVersion 1 0  sonar visualstudio solution NDM sln   sonar sourceEncoding UTF-8 sonar web host sonarqube sonar web port 9000    Enable the Visual Studio bootstrapper sonar visualstudio enable true    Unit Test Results sonar cs vstest reportsPaths TestResults   trx    Required only when using SonarQube  lt  4 2 sonar language cs  sonar sources     As you can see i set the sonar web host sonarqube sonar web port 9000 but when i run sonar-runner bat i still get the ERROR  Sonar server  http   localhost 9000  can not be reached - why is it still looking for localhost 9000 and not sonarqube 9000 as i set   i saw that in the log of sonar-runner bat there the following line  INFO  Work directory  D  sTFS 26091 Sources NDM Source  sonar  while my solution is in D  sTFS 26091 Sources NDM Source   could this be the problem   thanks  Guy

User · Answer

Please check if postgres or any other database service  is running properly

User · Answer

When you allow the 9000 port to firewall on your desired operating System the following error  ERROR  Sonar server  http   localhost 9000  can not be reached  will remove successfully In ubuntu it is just like as by typing the following command in terminal  sudo ufw allow 9000 tcp  this error will removed from the Jenkins server by clicking on build now in jenkins

User · Answer

In sonar properties file in conf folder I had hardcoaded ip of my machine where sobarqube was installed in property sonar web host 10 9 235 22 I commented this and it started working for me

User · Answer

For others who ran into this issue in a project that is not using a sonar-runners property file  you may find  as I did  that you need to tweak your pom xml file  adding a sonar host url property   For example  I needed to add the following line under the  properties  element    lt sonar host url gt https   sonar my-internal-company-domain net lt  sonar host url gt    Where the url points to our internal sonar deployment

User · Answer

In the config file there is a colon instead of an equal sign after the sonar web host   Is   sonar web host sonarqube   Should be  sonar web host sonarqube

User · Answer

For me the issue was that the maven sonar plugin was using proxy servers defined in the maven settings xml  I was trying to access the sonarque on another  not localhost alias  and so it was trying to use the proxy server to access it  Just added my alias to nonProxyHosts in settings xml and it is working now  I did not face this issue in maven sonar plugin 3 2  only after i upgraded it    lt proxy gt     lt id gt proxy id lt  id gt     lt active gt true lt  active gt     lt protocol gt http lt  protocol gt     lt host gt your-proxy-host host gt     lt port gt your-proxy-host lt  port gt     lt nonProxyHosts gt localhost 127 0   other-non-proxy-hosts lt  nonProxyHosts gt   lt  proxy gt enter code here

User · Answer

You should configure the sonar-runner to use your existing SonarQube server  To do so  you need to update its conf sonar-runner properties file and specify the SonarQube server URL  username  password  and JDBC URL as well  See https   docs sonarqube org display SCAN Analyzing with SonarQube Scanner for details   If you don t yet have an up and running SonarQube server  then you can launch one locally  with the default configuration  - it will bind to http   localhost 9000 and work with the default sonar-runner configuration  See https   docs sonarqube org latest setup get-started-2-minutes  for details on how to get started with the SonarQube server

User · Answer

I got the same issue  and I changed to IP and it working well  Go to System References --  Network --  Advanced --  Open TCP IP tabs --  copy the IPv4 Address   change that IP instead localhost  Hope this can help

User · Answer

If you use SonarScanner CLI with Docker  you may have this error because the SonarScanner container can not access to the Sonar UI container   Note that you will have the same error with a simple curl from another container   docker run --rm byrnedo alpine-curl 127 0 0 1 9000     Total      Received   Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed   0     0    0     0    0     0      0      0 -- -- -- -- -- -- -- -- --     0 curl   7  Failed to connect to 127 0 0 1 port 8080  Connection refused   The solution is to connect the SonarScanner container to the same docker network of your sonar instance  for instance with --network host   docker run --network host -e SONAR HOST URL  http   127 0 0 1 9000  --user    id -u    id -g   -v   PWD  usr src  sonarsource sonar-scanner-cli    other parameters of this command comes from the SonarScanner CLI documentation

[build] ERROR: Sonar server 'http://localhost:9000' can not be reached

Examples related to build

Examples related to sonarqube