"Port is already allocated" fix
Fix "Failed to bind" / "port is already allocated" on a Victus Minecraft server — align server.properties with your panel allocation and clear stale processes.
A "port is already allocated" or "Failed to bind to port" error means something is already using the port the server tried to open — usually because server.properties has a port that does not match your assigned panel allocation, or a previous process did not shut down cleanly.
Fix 1 — Match server.properties to your allocation
- Open the Network tab and note your primary allocation IP and port.
- Open the Files tab, edit
server.properties, and setserver-portto that exact port. - Leave
server-ip=blank (empty) so it binds to the allocation automatically. - Save, then Restart from the Console tab.
# server.properties
server-ip=
server-port=25565 # must equal your panel allocation portFix 2 — Clear a stale process
- On the Console tab open the power menu and press Kill to force-stop any lingering process.
- Wait a few seconds, then press Start.
You can only bind to allocations assigned to your server on the Network tab. Setting a random port will fail because it is not allocated to you. If you need an extra port (for a plugin, a query port, or a proxy), add an allocation on the Network tab if your plan allows it.
If you run a Velocity/BungeeCord proxy plus backend servers, each backend needs its own allocation and each server-port must point at its own allocation — never share one port between two running servers.