CentOS上SonarQube 5.6.7运行正常但Web界面无法访问求助

Hey there, let's troubleshoot this SonarQube web access issue on CentOS step by step— I've run into similar problems before, so these checks should help you narrow down the root cause:

1. Confirm SonarQube is Listening on the Right Port #

SonarQube defaults to port 9000, but first we need to make sure it's actually binding to that port (and not just the loopback interface). Run these commands on your CentOS server:

# Check listening ports with netstat
netstat -tulpn | grep 9000
# Or use ss if netstat isn't installed
ss -tulpn | grep 9000

• If you get no output: SonarQube isn't listening on port 9000. Check the web logs (more on that later) for binding errors, or verify your configuration file settings.
• If the output shows 127.0.0.1:9000: SonarQube is only accessible locally. You'll need to edit the sonar.properties file (usually in /opt/sonarqube/conf/) and change sonar.web.host=127.0.0.1 to sonar.web.host=0.0.0.0, then restart the service.

2. Check Firewall Restrictions #

CentOS uses either firewalld or iptables by default, and either might be blocking incoming traffic to port 9000.

For firewalld: #

# List current allowed ports/services
firewall-cmd --list-all
# If 9000/tcp isn't listed, add it permanently
firewall-cmd --add-port=9000/tcp --permanent
# Reload the firewall to apply changes
firewall-cmd --reload

For iptables: #

# List current rules
iptables -L -n
# Add a rule to allow port 9000 (if missing)
iptables -A INPUT -p tcp --dport 9000 -j ACCEPT
# Save the rules (varies by CentOS version)
service iptables save

Note: If this is a cloud server (AWS, Azure, etc.), don't forget to check your cloud provider's security group rules— they might be blocking port 9000 too.

3. Rule Out SELinux Blocking #

SELinux on CentOS can prevent services from listening on non-standard ports or accessing network resources. Let's test if SELinux is the culprit:

# Temporarily disable SELinux (for testing only)
setenforce 0

Now try accessing the SonarQube web interface again. If it works, you'll need to add port 9000 to SELinux's allowed HTTP ports permanently:

# Add the port to SELinux context
semanage port -a -t http_port_t -p tcp 9000
# Re-enable SELinux (always keep it enabled for security)
setenforce 1

4. Verify SonarQube Configuration & Permissions #

First, make sure you're not running SonarQube as root— SonarQube 5.6.7 explicitly prohibits root execution, which can cause hidden issues. If you started it with root, fix this immediately:

# Create a dedicated sonar user
useradd sonar
# Set ownership of the SonarQube directory
chown -R sonar:sonar /opt/sonarqube
# Switch to the sonar user and restart the service
su - sonar
./bin/linux-x86-64/sonar.sh restart

Next, check the sonar.properties file for any misconfigurations:

• Ensure sonar.web.port is set to the port you're trying to access (default 9000)
• Double-check database connection settings (even if the service starts, a flaky DB connection might break the web interface— look for DB errors in the logs)

5. Inspect SonarQube Logs for Errors #

Logs are your best friend here. Head to the SonarQube logs directory (usually /opt/sonarqube/logs/) and check these files:

• web.log: Look for errors related to port binding, HTTP server startup, or database connections
• sonar.log: Check for general service startup issues or permission errors
  If you see specific errors like Address already in use or Permission denied, that'll point you straight to the fix.

6. Test Network Connectivity from Your Client #

From the machine you're trying to access SonarQube from, run these tests to rule out network issues:

# Ping the CentOS server to confirm basic connectivity
ping <your-centos-server-ip>
# Test if port 9000 is reachable
telnet <your-centos-server-ip> 9000
# Or use nc if telnet isn't available
nc -zv <your-centos-server-ip> 9000

If the ping works but the port test fails, the issue is definitely a firewall/network restriction somewhere.

Go through these steps one at a time, and you should be able to get the web interface up and running. If you hit a specific error message in the logs, feel free to share it here for more targeted help!

内容的提问来源于stack exchange，提问作者Santosh