We have a video tutorial on Failed to Bind Port errors:
In rare occasions, a server is incorrectly assigned a port (the last 5 digits next to your server IP) that is already in use by another server. This will prevent the server from launching completely and will just attempt to restart repeatedly.
You can check this on your server log by navigating to the console of your server's Multicraft panel.
You may have any of the errors shown below, depending on the Server Type you have selected. :
Sample 1:
[Server] WARN **** FAILED TO BIND TO PORT!
[Server] WARN The exception was: io.netty.channel.unix.Errors$NativeIoException: bind(..) failed: Address already in use
[Server] WARN Perhaps a server is already running on that port?
Sample 2:
[Server] WARNING Could not bind to host /192.168.2.1:25655
[Server] INFO io.netty.channel.unix.Errors$NativeIoException: bind(..) failed: Address already in use
Sample 3:
[Server] INFO /usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint mc12345 (a9b8c7d6e5f4g3f2g1h0): Bind for 192.168.2.1:25655 failed: port is already allocated.
If you encounter this error with your server, please contact us immediately so that we can fix this for you.
If you require any further assistance, please contact our support at: https://shockbyte.com/billing/submitticket.php