DevOps & Cloud
Risk: Critical
Port 2375 — Docker REST API (Unencrypted)
Port 2375 is used for unencrypted HTTP communication with the Docker engine daemon.
PORT NUMBER
2375
PROTOCOL
TCP
DEFAULT PROCESS
dockerd
FIREWALL TARGET
2375/tcp
Instant Terminal Fixes for Port 2375
macOS & Linux Terminal
1. Check who is listening on port 2375:
sudo ss -tulpn | grep 23752. Kill process occupying port 2375 (EADDRINUSE fix):
sudo systemctl stop docker3. UFW Firewall Allow rule:
sudo ufw deny 2375Windows PowerShell (Admin)
1. Check listening port:
Get-NetTCPConnection -LocalPort 23752. Force kill process on port 2375:
Stop-Service docker -Force3. Docker Port Forwarding Mapping:
dockerd -H tcp://0.0.0.0:2375Common Error Encountered
Cannot connect to the Docker daemon at tcp://localhost:2375. Is the docker daemon running?
Security Advisory & Hardening
SEVERE SECURITY HAZARD: Exposing port 2375 without TLS allows anyone with network access to run root-level containers and take over the host operating system. Always use TLS (port 2376) or local UNIX socket `/var/run/docker.sock`.
Frequently Asked Questions
Port 2375 Questions & Answers
Common questions regarding default services, kill commands, and firewall configurations.
Port 2375 is commonly used for Docker REST API (Unencrypted). Port 2375 is used for unencrypted HTTP communication with the Docker engine daemon.