Failed to bind to port: clearing the port and restarting

A "Failed to bind to port" error means something else is still holding the listen port. A clean container restart almost always fixes it.

The short version

Failed to bind to port means something is still holding the listen port, usually a previous server process after an unclean crash. Restart the container rather than just the Minecraft process; that recycles everything and frees the port. If it repeats on every boot, a modpack may be changing the port silently.

A Failed to bind to port or BindException: Address already in use error means the Minecraft server tried to open the listen port (25565 by default for Java) and was refused, because something else already holds it. On Hostd, that "something else" is almost always your own previous server process; the container did not shut down cleanly and the kernel still has the socket open.

#Restart the container, not just Minecraft

Open Dashboard → your server → Console panel and hit Restart. A restart from the dashboard recycles the whole container, which means the old port binding is released along with it. Hitting Start without a stop first will not help; the container has to fully exit and come back. After the restart, the port is free.

#If it repeats every boot

A persistent bind error after the container has been fully recycled points at one of two things:

  • A custom port that does not match what the proxy is forwarding. If you have changed server-port= in Files → /data/server.properties to something other than the default, the container will start Minecraft on the new port but the dashboard will still send traffic to the old one. Either revert to the default or open a ticket from Dashboard → Support so we can re-point the proxy.
  • A node-side wedge. Rare but possible: the kernel on the host has the socket parked and only a node-level restart will clear it. Open a ticket and we will reset the container on our side.

#Modpacks that change the port silently

Some Forge and NeoForge packs ship a default server.properties with a non-default port (a few FTB packs are the main culprits). When the pack installer drops the file in, the server tries to bind to 25566 or similar instead. If you cannot reach the server even though the console says "Done!", check that server-port= in Files → /data/server.properties matches the port shown on your Connect tab.

#Where to go next

#Frequently asked questions

What does Failed to bind to port mean in Minecraft?

The server tried to listen on its port and something else already had it. On a hosted server this is nearly always a previous process that has not fully exited, not another server competing for the port.

How do I fix a port binding error?

Restart the container from the dashboard, not just the server process. The container recycles and the port is released. If the same error returns on every boot, open a ticket so it can be cleared node-side.

Can a modpack change my server port?

Some packs ship a server.properties with their own server-port value, which then does not match what the platform expects. If binding fails immediately after installing a pack, check that value before anything else.

Written and maintained by the Hostd engineering team. Last updated 2026-05-23. Notice a mistake? Tell us.

Keep reading