bitlvl
EN

Port 9090 Prometheus · TCP

Prometheus' web UI and API: targets, alerts, and ad-hoc PromQL that returns every metric in the system.

Port9090
TransportTCP
ServicePrometheus
CategoryMonitoring and logging
Rangeregistered (1024–49151)
EncryptedNo, plaintext
ExposurePrivate network or VPN only

What runs on port 9090

Prometheus' web UI and API: targets, alerts, and ad-hoc PromQL that returns every metric in the system. No authentication of its own, so reverse-proxy it or keep it internal. Also Cockpit's web console on Red Hat/Fedora (9090/TCP with TLS), Openfire's admin console and a few other admin UIs.

Software that uses it: Prometheus · Cockpit (Linux web console) · Openfire admin · Thanos Query (uses 9090 too)

Should port 9090 be open?

Private network or VPN only. Nothing good comes from this port being reachable from the internet. Keep it on an internal network, reach it over a VPN or an SSH tunnel, and firewall it from everything that does not need it.

Check port 9090

# on the host: is anything listening, and which process?
ss -ltnp 'sport = :9090'
sudo lsof -i :9090

# from another machine: is it reachable?
nc -zv host 9090
nmap -p 9090 host
curl -v telnet://host:9090      # raw TCP connect test, Ctrl-C to leave

A port that answers from the internet when it should not is the finding; nmap from a machine outside your network (or a VPS) is the honest test, because scans from inside the LAN pass the firewall you are trying to verify.

Allow or block port 9090

# ufw (Ubuntu/Debian)
sudo ufw allow from 10.0.0.0/8 to any port 9090 proto tcp
sudo ufw deny 9090/tcp

# nftables
nft add rule inet filter input ip saddr 10.0.0.0/8 tcp dport 9090 accept
nft add rule inet filter input tcp dport 9090 drop

# iptables (legacy)
iptables -A INPUT -p tcp --dport 9090 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p tcp --dport 9090 -j DROP

# firewalld
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=9090 protocol=tcp accept'

Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 9090" with no source is just "open".

Related ports

Part of the port number reference. Ports are 16-bit numbers; see also the subnet calculator and the packet decoder, which shows ports inside TCP and UDP headers.

Questions

Is port 9090 TCP or UDP?

TCP. Prometheus is a connection-oriented protocol; there is no UDP service on 9090 by default (a scanner reporting UDP 9090 open is usually seeing a filtered port).

Is port 9090 encrypted?

No, plaintext. Anything sent over it can be read by whoever is on the path, so it belongs on a trusted network or inside a VPN or SSH tunnel.

How do I check whether port 9090 is open?

On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 9090 and which process. From another machine, nc -zv host 9090 or nmap -p 9090 host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).

Can Prometheus run on a different port?

Yes; the number is a convention, not a requirement. Changing it reduces log noise from scanners but does not add security, and every client, firewall rule and monitoring check then needs the new number. Keep the default unless you have a concrete reason.