Port 9000 is shared by several tools: PHP-FPM’s FastCGI listener, SonarQube, the MinIO S3 API and older Portainer installs all default to it. It should not be reachable from the public internet.
- Port
- 9000
- Protocol
- TCP
- Service
- PHP-FPM / SonarQube / MinIO
- Expose to internet?
- No
- Also used by
- PHP-FPM (FastCGI), SonarQube, MinIO S3 API, Portainer (legacy HTTP), Graylog
Is port 9000 safe to open?
If PHP-FPM is listening on a public interface, anyone can send FastCGI requests that make it execute arbitrary PHP code. Portainer controls Docker, MinIO holds your object storage and SonarQube holds source code analysis, so none should be public without strong authentication.
How to secure PHP-FPM / SonarQube / MinIO
- Make PHP-FPM listen on a Unix socket or 127.0.0.1:9000 (
listen =in the pool config) and setlisten.allowed_clients. - Change MinIO’s root credentials and publish its API through TLS.
- Put Portainer and SonarQube behind TLS and restrict access to your team.
- Check the owner with
sudo ss -ltnp 'sport = :9000'.
Check if port 9000 is open
Linux: what is listening on this port
sudo ss -tlpn | grep ':9000 'Windows (PowerShell): what is listening
Get-NetTCPConnection -LocalPort 9000 -State Listen | Select-Object LocalAddress, OwningProcess, @{n='Process';e={(Get-Process -Id $_.OwningProcess).Name}}From another machine: is it reachable
nc -zv HOST 9000
# or
nmap -p 9000 HOST
# Windows
Test-NetConnection HOST -Port 9000Test the PHP-FPM / SonarQube / MinIO service itself
curl -sI http://HOST:9000/Restrict port 9000 in the firewall
Replace 10.0.0.0/8 with the network or address that needs access. Docker publishes container ports through its own iptables rules, which bypass ufw; bind published ports to 127.0.0.1 (-p 127.0.0.1:9000:9000) instead of relying on the host firewall.
ufw: allow only your private network, deny everyone else
sudo ufw allow from 10.0.0.0/8 to any port 9000 proto tcp
sudo ufw deny 9000/tcpfirewalld: allow one source network only
sudo firewall-cmd --permanent --remove-port=9000/tcp
sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="10.0.0.0/8" port port="9000" protocol="tcp" accept'
sudo firewall-cmd --reloadiptables
sudo iptables -A INPUT -p tcp --dport 9000 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 9000 -j DROPWindows Firewall (PowerShell, as Administrator)
New-NetFirewallRule -DisplayName "Block 9000 from internet" -Direction Inbound -Protocol TCP -LocalPort 9000 -RemoteAddress Internet -Action BlockMonitor port 9000
Run a TCP port monitor against your public IP on port 9000: here, a failed connection is the healthy result, so you know the firewall is still doing its job. On Linux, the Statance agent also reports every listening port on the server. TCP port monitoring.
Related ports
| Port 80 | HTTP | Low risk |
| Port 9090 | Prometheus / Cockpit | Medium risk |
| Port 2375 | Docker Engine API (unencrypted) | Critical risk |
FAQ
What is port 9000 used for?
Port 9000 is shared by several tools: PHP-FPM’s FastCGI listener, SonarQube, the MinIO S3 API and older Portainer installs all default to it. It is also used by PHP-FPM (FastCGI), SonarQube, MinIO S3 API, Portainer (legacy HTTP), Graylog.
Is it safe to open port 9000?
Not to the public internet. If PHP-FPM is listening on a public interface, anyone can send FastCGI requests that make it execute arbitrary PHP code. Portainer controls Docker, MinIO holds your object storage and SonarQube holds source code analysis, so none should be public without strong authentication.
Is port 9000 TCP or UDP?
PHP-FPM / SonarQube / MinIO uses TCP on port 9000.
How do I check if port 9000 is open?
On the server, run sudo ss -tulpn | grep ':9000 ' (Linux) or Get-NetTCPConnection -LocalPort 9000 (Windows) to see what is listening. From another machine, run nc -zv HOST 9000 or Test-NetConnection HOST -Port 9000.
Know the moment a port stops answering.
TCP, HTTP, DNS and SSL checks from six regions, plus server metrics from a one-line agent.