Skip to content
statance
MenuClose
← All ports

Port 19999: Netdata dashboard

Medium risk

Port 19999 is the Netdata agent’s built-in web dashboard and API, which shows real-time metrics for the host. It should not be reachable from the public internet.

Port
19999
Protocol
TCP
Service
Netdata dashboard
Expose to internet?
No

Is port 19999 safe to open?

The local Netdata dashboard has no login by default. Anyone who can reach it sees detailed metrics: running applications, users, network connections, disk names and resource use. That is useful reconnaissance and can leak business information.

How to secure Netdata dashboard

  • Bind the dashboard to localhost with bind to = localhost under [web] in netdata.conf.
  • Or allow only trusted addresses with allow connections from in the same section.
  • Use an SSH tunnel or a proxy with authentication for remote viewing.

Check if port 19999 is open

Linux: what is listening on this port

sudo ss -tlpn | grep ':19999 '

Windows (PowerShell): what is listening

Get-NetTCPConnection -LocalPort 19999 -State Listen | Select-Object LocalAddress, OwningProcess, @{n='Process';e={(Get-Process -Id $_.OwningProcess).Name}}

From another machine: is it reachable

nc -zv HOST 19999 # or nmap -p 19999 HOST # Windows Test-NetConnection HOST -Port 19999

Test the Netdata dashboard service itself

curl -s http://HOST:19999/api/v1/info

Restrict port 19999 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:19999:19999) 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 19999 proto tcp sudo ufw deny 19999/tcp

firewalld: allow one source network only

sudo firewall-cmd --permanent --remove-port=19999/tcp sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="10.0.0.0/8" port port="19999" protocol="tcp" accept' sudo firewall-cmd --reload

iptables

sudo iptables -A INPUT -p tcp --dport 19999 -s 10.0.0.0/8 -j ACCEPT sudo iptables -A INPUT -p tcp --dport 19999 -j DROP

Windows Firewall (PowerShell, as Administrator)

New-NetFirewallRule -DisplayName "Block 19999 from internet" -Direction Inbound -Protocol TCP -LocalPort 19999 -RemoteAddress Internet -Action Block

Monitor port 19999

Run a TCP port monitor against your public IP on port 19999: 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 9090Prometheus / CockpitMedium risk
Port 9100Prometheus node_exporter / JetDirect printingMedium risk
Port 3000Grafana / Node.js development serversMedium risk

FAQ

What is port 19999 used for?

Port 19999 is the Netdata agent’s built-in web dashboard and API, which shows real-time metrics for the host.

Is it safe to open port 19999?

Not to the public internet. The local Netdata dashboard has no login by default. Anyone who can reach it sees detailed metrics: running applications, users, network connections, disk names and resource use. That is useful reconnaissance and can leak business information.

Is port 19999 TCP or UDP?

Netdata dashboard uses TCP on port 19999.

How do I check if port 19999 is open?

On the server, run sudo ss -tulpn | grep ':19999 ' (Linux) or Get-NetTCPConnection -LocalPort 19999 (Windows) to see what is listening. From another machine, run nc -zv HOST 19999 or Test-NetConnection HOST -Port 19999.

All ports →

Know the moment a port stops answering.

TCP, HTTP, DNS and SSL checks from six regions, plus server metrics from a one-line agent.