Fixing Failed to Bind Port & Address in Use
Resolve java.net.BindException: Address already in use in seconds by correcting container network bindings in your server properties.
1. Error Signature & Symptoms
When starting your server, the console prints:
[Server thread/ERROR]: **** FAILED TO BIND TO PORT!
[Server thread/ERROR]: The exception was: java.net.BindException: Address already in use
[Server thread/ERROR]: Perhaps a server is already running on that port?2. Cause 1: server-ip Has a Value in server.properties (90% of Cases)
Inside a containerized Pterodactyl environment, the Docker container does not have direct access to bind the physical host’s public IP directly. Wings handles the forwarding.
The Fix: Keep server-ip Blank
server.properties in your File Manager. Locate the line:server-ip=103.xxx.xxx.xxx # <-- WRONGChange it to:
server-ip= # <-- CORRECT (Completely blank)Save the file and start your server.
3. Cause 2: server-port Does Not Match Allocation
Verify that server-port in server.properties exactly matches your Primary Allocation Port shown on your server dashboard (e.g. 25675). If you imported a world from another host that used 25565, update the property to your OrynCloud assigned port.
4. Cause 3: Ghost Java Process in Container
If the server crashed during a restart cycle, a zombie Java process may hold the socket open. Click the red Kill button in the console to forcibly destroy the container, then click Start.