Table Of Contents
Common Exit Codes and SolutionsStill have questions?
Come chat with us and we will get back to you as soon as possible!
Contact Support
Kobe Plane
Game Experience Engineer
Troubleshooting Common Java Error Exit Codes
Server Errors & Troubleshooting
·Sep 11, 2024
·3 min read
In some cases, your server may crash without any explanation or a crash report. Often in these situations, it’ll be accompanied by a number such as 1, 137, or 143.
#Common Exit Codes and Solutions
While Exit Codes can be hard to diagnose, they generally point to a few simple problems, which we cover in the table below.
| Exit Code | Description | Solution |
|---|---|---|
1 | Your server’s JAR file is either not named properly, missing, or corrupted. | Ensure the name of your JAR file matches what is configured in your server instance. If you’re running a modpack or a Custom JAR, consider reinstalling Forge/Fabric or your Custom JAR file. |
2 | In certain situations, this may signify a networking issue. | Check your server files for any crash reports. If you are unable to find any, please feel free to contact us for help. |
125 | Your server’s port is not binding properly. This code may also be accompanied by a Failed to bind to port error. | This error implies you may need a new, valid IP address assigned to your server. If you experience this error, please contact us for support! |
137 | Your server is out of memory (RAM). | If you experience this error code, you should investigate ways to lower your memory usage or upgrade the RAM allocated on your server. |
143 | Your server was terminated by an external factor. This error can sometimes occur when a server isn’t responding and you’ve clicked the kill button. | Generally, this error may be ignored. If the error appears repeatedly, you should consider reviewing crash reports, running a timing report, or contacting us for support. |