-
which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension): SonarQube v10.0.0.68432 Community Edition. No extensions or plugins used.
-
how is SonarQube deployed: zip, Docker, Helm : I’m deploying it with the sonarqube-10.0.0.68432.zip downloaded directly from the SonarQube website. I’m also using Centos 7 as my environment.
-
what are you trying to achieve: I’ve gone through the documentation and help videos to setup SonarQube on my virtual machine, I’ve gotten to the point of running SonarQube successfully with…
`[sonar@sqesonarqube linux-x86-64]$ ./sonar.sh start`I get a ERR_CONNECTION_TIMED_OUT when typing this address on my local machine :
`http://<virtual_machine_ip_address>:8083/sonarqube`My sonar.properties file is configured as such:
sonar.jdbc.username=sonar sonar.jdbc.password=sonar sonar.web.context=/sonarqube sonar.web.port=8083 sonar.jdbc.url=jdbc:postgresql://localhost:5432/sonarqube -
what have you tried so far to achieve this: I’ve gone through all my logs to make sure my SonarQube is running properly.
web.log output:
2023.06.14 14:54:29 INFO web[][o.s.s.p.w.MasterServletFilter] Initializing servlet filter org.sonar.server.plugins.PluginsRiskConsentFilter@5ffcf507 [pattern=UrlPattern{inclusions=[/*], exclusions=[*.css, ...]}]
2023.06.14 14:54:29 INFO web[][o.s.s.q.ProjectsInWarningDaemon] Counting number of projects in warning is not started as there are no projects in this situation.
2023.06.14 14:54:29 INFO web[][o.s.s.p.p.PlatformLevelStartup] Running Community Edition
2023.06.14 14:54:30 INFO web[][o.s.s.p.Platform] Web Server is operational
sonar.log output:
2023.06.14 14:54:30 WARN app[][startup] ####################################################################################################################
2023.06.14 14:54:30 WARN app[][startup] Default Administrator credentials are still being used. Make sure to change the password or deactivate the account.
2023.06.14 14:54:30 WARN app[][startup] ####################################################################################################################
2023.06.14 14:54:35 INFO app[][o.s.a.SchedulerImpl] Process[ce] is up
2023.06.14 14:54:35 INFO app[][o.s.a.SchedulerImpl] SonarQube is operational
- I was able to ping my virtual machine successfully from my local machine
- I was able to get a response back when running
curl -v <virtual_machine_ip>:8083/sonarqube
on my VM
output:
* Trying <virtual_machine_ip>...
* TCP_NODELAY set
* Connected to <virtual_machine_ip> (<virtual_machine_ip>) port 8083 (#0)
> GET /sonarqube HTTP/1.1
> Host: <virtual_machine_ip>:8083
> User-Agent: curl/7.61.1
> Accept: */*
>
< HTTP/1.1 302
< Location: /sonarqube/
< Transfer-Encoding: chunked
< Date: Wed, 14 Jun 2023 21:57:48 GMT
<
* Connection #0 to host <virtual_machine_ip> left intact
- I also tried accessing the webpage on different devices using different networks.
Additional Info
- I was able to host an apache webpage on the VM and access that page from my local machine through port 80.
These are all the steps I’ve taken so far, I’m leaning towards it being a proxy/firewall related issue because I am setting this all up on a VM provided by my company, however I just wanted to post this thread in case I was overlooking something in my setup. Thanks in advance!