Q. I launched a SonarQube instance on AWS using SonarQube (ami-0036773d8c82f256f) from AWS Marketplace. The EC2 instance is running and I can SSH into the host. However, when I browse to the IP address on the web, I receive \”Your connection is not secure\” error. When I accept risk and continue, I then receive 502 Bad Gateway error. How can I get past this? How do I verify SonarQube is running on the EC2 instance?
Follow these three steps to troubleshoot the issue:
1. 502 Bad Gateway occurs when SonarQube is not fully started. Please allow some time for the software to load and then refresh the browser.
2. To check if the SonarQube is running, please execute the following command:
sudo systemctl status sonarqube
3. If the system is running, you will be able to see the following status:
Active: active (running) /system.slice/sonarqube.service
4. You will then see sonarqube service details similar to the following log:
/system.slice/sonarqube.service ├─6329 /usr/bin/java -Xms32m -Xmx32m -Djava.net.preferIPv4Stack=true -jar /usr/local/sonarqube/lib/sonar-application-7.9.6.jar ├─6347 /usr/lib/jvm/java-11-openjdk-184.108.40.206.8-1.amzn2.0.3.x86_64/bin/java -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+Use... └─6595 /usr/lib/jvm/java-11-openjdk-220.127.116.11.8-1.amzn2.0.3.x86_64/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=/usr/l...
Please note that all 3 (three) processes above need to be started to connect to the web.If you only see 2 (two), you will get a bad gateway error.