Port 4369 is epmd, which tells Erlang nodes which port each other node is listening on for distributed Erlang. RabbitMQ and CouchDB clusters depend on it. It should not be reachable from the public internet.
- Port
- 4369
- Protocol
- TCP
- Service
- Erlang Port Mapper Daemon (epmd)
- Expose to internet?
- No
- Also used by
- RabbitMQ, CouchDB, ejabberd, Elixir applications
Is port 4369 safe to open?
epmd reveals node names and their distribution ports. Erlang distribution is protected only by a shared cookie; anyone who knows or guesses it can connect and run arbitrary code on the node. Neither epmd nor the distribution port should be reachable from outside the cluster.
How to secure Erlang Port Mapper Daemon (epmd)
- Allow 4369 and the Erlang distribution port (25672 for RabbitMQ) only between cluster nodes.
- Make sure the
.erlang.cookiefile is long, random and readable only by the service user. - For single-node RabbitMQ, bind epmd to localhost (
ERL_EPMD_ADDRESS=127.0.0.1).
Check if port 4369 is open
Linux: what is listening on this port
sudo ss -tlpn | grep ':4369 'Windows (PowerShell): what is listening
Get-NetTCPConnection -LocalPort 4369 -State Listen | Select-Object LocalAddress, OwningProcess, @{n='Process';e={(Get-Process -Id $_.OwningProcess).Name}}From another machine: is it reachable
nc -zv HOST 4369
# or
nmap -p 4369 HOST
# Windows
Test-NetConnection HOST -Port 4369Test the Erlang Port Mapper Daemon (epmd) service itself
epmd -namesRestrict port 4369 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:4369:4369) 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 4369 proto tcp
sudo ufw deny 4369/tcpfirewalld: allow one source network only
sudo firewall-cmd --permanent --remove-port=4369/tcp
sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="10.0.0.0/8" port port="4369" protocol="tcp" accept'
sudo firewall-cmd --reloadiptables
sudo iptables -A INPUT -p tcp --dport 4369 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 4369 -j DROPWindows Firewall (PowerShell, as Administrator)
New-NetFirewallRule -DisplayName "Block 4369 from internet" -Direction Inbound -Protocol TCP -LocalPort 4369 -RemoteAddress Internet -Action BlockMonitor port 4369
Run a TCP port monitor against your public IP on port 4369: 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 5672 | AMQP (RabbitMQ) | High risk |
| Port 15672 | RabbitMQ management UI | High risk |
| Port 5984 | Apache CouchDB | High risk |
FAQ
What is port 4369 used for?
Port 4369 is epmd, which tells Erlang nodes which port each other node is listening on for distributed Erlang. RabbitMQ and CouchDB clusters depend on it. It is also used by RabbitMQ, CouchDB, ejabberd, Elixir applications.
Is it safe to open port 4369?
Not to the public internet. epmd reveals node names and their distribution ports. Erlang distribution is protected only by a shared cookie; anyone who knows or guesses it can connect and run arbitrary code on the node. Neither epmd nor the distribution port should be reachable from outside the cluster.
Is port 4369 TCP or UDP?
Erlang Port Mapper Daemon (epmd) uses TCP on port 4369.
How do I check if port 4369 is open?
On the server, run sudo ss -tulpn | grep ':4369 ' (Linux) or Get-NetTCPConnection -LocalPort 4369 (Windows) to see what is listening. From another machine, run nc -zv HOST 4369 or Test-NetConnection HOST -Port 4369.
Know the moment a port stops answering.
TCP, HTTP, DNS and SSL checks from six regions, plus server metrics from a one-line agent.