What Is Port 2368?
Port 2368 is an unassigned registered port. IANA has not allocated it to any official service. In the registered range (1024–49151), that means any application can use it — and one application in particular has made it its own.
Ghost, the Node.js blogging platform, defaults to port 2368. Every Ghost installation that hasn't been explicitly configured otherwise is listening here, usually bound to 127.0.0.1 and proxied through nginx on port 80. The port isn't in any RFC. Ghost just picked it, documented it, and kept it. 1
How Ghost Uses It
When you install Ghost, the default server configuration is:
Ghost runs on 2368. nginx sits in front, accepting traffic on port 80 (or 443 for HTTPS) and proxying requests back to Ghost at 127.0.0.1:2368. From the outside, you never see the port. From the inside, it's everywhere.
The Docker Hub official Ghost image exposes 2368 by default. Ghost's CLI tool will refuse to start a second instance if something is already on 2368 — you've hit that error if you've ever tried running two Ghost blogs on one server. 2
To change it: ghost config server.port <new-port> followed by ghost restart. 3
What Range Does This Port Belong To?
Port 2368 sits in the registered ports range (1024–49151). These ports are:
- Not reserved for root/admin use (unlike well-known ports below 1024)
- Intended for registration with IANA, though registration isn't enforced
- Freely usable by any application that wants them
IANA's registry shows no entry for 2368. That's not unusual — thousands of ports in this range are similarly unclaimed officially but well-known in practice.
Check What's Listening on This Port
If you're running Ghost and see a Port '2368' is in use error, another Ghost instance (or something else) got there first.
Why Unassigned Ports Matter
IANA's registry is an aspiration, not a law. Ports like 2368 show how the Internet actually works: a popular project picks a number, documents it, ships it as the default, and suddenly that number means something. Not because a standards body said so, but because enough people use it.
The registered range exists precisely for this — applications registering their preferred ports to avoid collisions. Ghost never formally registered 2368, but in practice, any developer who sees 2368 in a firewall rule or a netstat output knows what they're looking at.
آیا دا پاڼه ګټوره وه؟