Server can't bind to host

This article only applies if you are using a custom jar. If you are using a jar found in Multicraft, renaming your server jar is not necessary
On rare occasions, it's possible for a Minecraft server to crash in such a way that Multicraft is not able to end the process. If this happens, when you next try to start the server you will get an error like this:

13.06 11:23:34 [Server] INFO Address already in use
13.06 11:23:34 [Server] WARNING Could not bind to host

If this happens, you can make Multicraft kill the old process.

1. Stop your server if it's running or attempting to run.
2. Using FTP, rename your server jar to custom_server.jar.
3. In the Multicraft control panel, change the server selected to custom_server.jar, then click save.
4. Start your server.
  • 1 Users Found This Useful
Was this answer helpful?

Related Articles

Troubleshooting Lag

Timings ReportBukkit and Spigot servers can perform a timings report to find exactly which events...

Taking a screenshot

On occasion, a member of support will ask you to take a screenshot of an issue you are...

Forge is missing essential library files.

04.12 19:25:50 [Server] INFO You will need to add them to your server before FML and Forge will...

Understanding Minecraft server log files

Being able to read, understand and troubleshoot issues using the log files that your Minecraft...

Disk quota exceeded

IntroductionTo prevent abuse, accidental or otherwise, all our servers have a disk quota. This...