Skip to content
statance
MenuClose
← All ports

Port 3000: Grafana / Node.js development servers

Medium risk

Port 3000 is a common default for web applications: Grafana, Gitea, Rails and many Node.js frameworks listen on it, and Next.js and Create React App use it for local development. It should not be reachable from the public internet.

Port
3000
Protocol
TCP
Service
Grafana / Node.js development servers
Expose to internet?
No
Also used by
Grafana, Express, Next.js dev server, Ruby on Rails (puma), Gitea, Metabase

Is port 3000 safe to open?

Applications on port 3000 are usually meant to sit behind a reverse proxy on 443. Exposing them directly skips TLS and any protections the proxy adds, and development servers are not built for public traffic. Grafana in particular ships with the default login admin/admin until you change it.

How to secure Grafana / Node.js development servers

  • Bind the application to 127.0.0.1 and serve it through nginx, Caddy or another proxy with TLS.
  • Change default credentials immediately (Grafana prompts on first login).
  • Never run a development server (npm run dev, rails s) on a public interface.

Check if port 3000 is open

Linux: what is listening on this port

sudo ss -tlpn | grep ':3000 '

Windows (PowerShell): what is listening

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

From another machine: is it reachable

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

Test the Grafana / Node.js development servers service itself

curl -sI http://HOST:3000/

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

firewalld: allow one source network only

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

iptables

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

Windows Firewall (PowerShell, as Administrator)

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

Monitor port 3000

Run a TCP port monitor against your public IP on port 3000: 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 8080HTTP alternateMedium risk
Port 5000Flask / Docker Registry / AirPlayMedium risk
Port 8000HTTP alternate / development serversMedium risk

FAQ

What is running on port 3000?

Commonly Grafana, Gitea, a Rails app or a Node.js app. Run sudo ss -ltnp 'sport = :3000' on Linux or lsof -i :3000 on macOS to see the process.

What is port 3000 used for?

Port 3000 is a common default for web applications: Grafana, Gitea, Rails and many Node.js frameworks listen on it, and Next.js and Create React App use it for local development. It is also used by Grafana, Express, Next.js dev server, Ruby on Rails (puma), Gitea, Metabase.

Is it safe to open port 3000?

Not to the public internet. Applications on port 3000 are usually meant to sit behind a reverse proxy on 443. Exposing them directly skips TLS and any protections the proxy adds, and development servers are not built for public traffic. Grafana in particular ships with the default login admin/admin until you change it.

Is port 3000 TCP or UDP?

Grafana / Node.js development servers uses TCP on port 3000.

How do I check if port 3000 is open?

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

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.