Fixing common Java error exit codes on your Minecraft server is very simple with Pine Hosting. This guide walks you through on how to identify the issue on your server and how to fix it.
Common Java Error Exit Codes:
| Code | Explanation | Solution |
| Exit Code: 1 | Your JAR file is either not named properly, missing, or corrupted. |
Make sure the name of your JAR file matches what is configured in your server. When running a modpack or a Custom JAR, reinstalling Forge/Fabric or your Custom JAR file should fix the issue. |
| Exit Code: 2 | Can indicate that there's a networking issue. |
Check your servers crash reports as explained here, or reach out to us for support. |
| Exit Code: 125 | The server port is not binding properly. This code may also be accompanied by a "Failed to bind to port error". | Changing your IP address should resolve the issue. If you encounter this just contact us to fix this for you. |
| Exit Code: 137 | The server is out of memory (RAM) | Finding ways to lower your memory usage or upgrading the RAM on your server here, will resolve this. |
| Exit Code: 143 | The server was terminated by an external factor. Can often occur by clicking the "Kill" button when the server is unresponsive. | If the error is being spammed, take a look at your crash reports as explained here and run a timing report. Otherwise it should be ignored. |
For any more assistance, feel free to contact us on Discord or the Website.
Our custom panel has a wide variety of exclusive features that make editing and managing game servers a breeze.
All game servers come with powerful hardware and a dedicated team of support members to help you build the servers exactly the way you want.
Start your minecraft server hosting journey today with Pine Hosting!
