Facing Errors: A Minecraft Server Troubleshooting Guide
Let's admit it: errors can be quite frustrating. In this article, we'll assist you in understanding and resolving errors that occur on your Minecraft server.
EULA Error: When initiating your server for the first time, you'll need to accept the Minecraft EULA (End User License Agreement). If you encounter this error and crash during startup displaying You need to agree to the EULA in order to run the server. Go to eula.txt for more info., simply accept the Minecraft EULA when prompted, or manually set eula=true in the eula.txt file.
Permission Denied: If you encounter an error like /entrypoint.sh: line 12: ./bedrock_server: Permission denied, navigate to the indicated file and change its permissions to 755 (you can do this by right-clicking or selecting the three dots next to the file, then going to “Permissions”).
Failed to Bind Port: This error appears as: FAILED TO BIND PORT! The exception was: java.net.BindException: Address already in use
This means another process is already using that port. Change your server port or, if you have a dedicated IP, contact support via live chat for assistance.
Unable to Read World Format: This error means the server couldn’t load your world — likely due to corruption or an incompatible world format. Fix it by generating a new world, converting the existing one, or importing a compatible, uncorrupted world.
Unable to Access server.jar File: This error often occurs when the server.jar file is missing, named incorrectly, or corrupted. Rename the file to server.jar if necessary, or upload/re-upload it manually. If it’s corrupted, consider reinstalling the server. |
Java Version Error: If prompted to use a specific Java version (for example: Minecraft 1.17 requires running the server with Java 16 or above.), adjust the Java version accordingly. Forge users may encounter compatibility issues, indicated by console errors. To fix this, select the correct Java version in the control panel’s startup section.
Out of Memory: Server freezes, player kicks, or an unresponsive console usually indicate RAM exhaustion. Allocate more RAM, optimize memory usage, and restart the server periodically.
Crashing Mods/Plugins: Unspecified startup errors are often caused by faulty mods or plugins. Identify and update or remove the problematic files to resolve the issue.
Failed to Open Curl Lib from Binary: Modify the ipv6 value in server.properties to resolve this error, ensuring it differs from the ipv4 address.
Pocketmine Errors: Make sure the PHP version matches the Pocketmine version to avoid startup errors.
Nukkit Errors: When prompted at startup, choose the server language (for example, eng for English) to prevent it from being misinterpreted as a crash.
Bedrock Server Permission Denied Issue: Change the permissions of the bedrock_server file to 755 to allow the server to start successfully.
Ensure the following configurations are in place for a properly functioning proxy:
We'll expand this section with more errors soon
bukkit.yml connection-throttle to -1
spigot.yml bungeecord to true
server.properties online-mode to false
IP forwarding to true on bungee Restart all related servers afterward.
Plugin/Mod Errors: If you encounter an error that doesn't halt the server's startup, it's likely due to a mod or plugin issue. Such plugins or mods might be disabled or functioning improperly. Check their configurations for any anomalies (instructions are usually available on the download site). Outdated or poorly developed plugins/mods can also cause issues. Review the settings, update to the latest version if available, or remove them if they consistently fail to work.
Timings URLs Not Created: Ensure that your paper.yml file has both history and interval set to the recommended values, and that the timings URL is configured to the default one: https://timings.aikar.co/
Missing Required Core Mod or Plugin (Java): This error suggests that a mod or plugin requires another core mod/plugin that is not present. To fix this, either remove the dependent mod/plugin or install the required one. The console or download site usually indicates which dependency is missing.
Server Overload: "Can't Keep Up" This error indicates a drop in TPS (ticks per second), causing lag. Identify the source of the lag by following our server optimization guide.
Incompatible Protocol Version (PMMP): This error means a plugin is outdated or incompatible with your PocketMine-MP version. Download plugins from Poggit and ensure you select the correct version for your server.
Failed Loading Error: This error, such as Failed loading /home/container/bin/php7/lib/php/extensions/no-debug-zts-20190902/opcache.so: /home/container/bin/php7/lib/php/extensions/no-debug-zts-20190902/opcache.so: cannot open shared object file: No such file or directory, can be disregarded as it does not impact server functionality.
Outdated Server: Update your server, downgrade your Minecraft client, or install a multi-version support plugin like [ViaVersion](https://www.spigotmc.org/resources/viaversion.19254/).
Outdated Client: Downgrade your server, update your Minecraft client, or add a multi-version support plugin like ViaBackwards (requires ViaVersion).
Invalid IP: Ensure you enter a valid IP address (comprising numbers and dots) in the server address field.
Banned by an Operator: Contact a server administrator to lift the ban. Use /pardon or /unban if you have console access, or /pardon-ip or /unban-ip if your IP is banned.
Server Whitelisted: Add your in-game name to the whitelist using whitelist add in the console. Alternatively, disable whitelist in server.properties by setting whitelist=false and restarting the server.
Bad Login: Avoid logging in too quickly and ensure compatibility between your Minecraft version and the server. Check your internet connection as it may also contribute to this error.
Authentication Servers Down for Maintenance: Wait if the authentication servers are indeed offline. If not, ensure your firewall isn't blocking the connection or consider changing online-mode=false in server.properties.
Failed to Verify Username / Invalid Session: Log out and log back into Minecraft. For non-premium versions, set online-mode=false in server.properties and restart the server.
Connection Refused (If It's You): Verify the IP and port, ensure your antivirus or firewall isn't blocking the connection, and check for network issues.
Connection Refused (If It's Not Just You): Examine the server console for errors and ensure compatibility with the chosen gametype.
Timeout Errors: Consider upgrading your hardware, closing other programs, pausing any downloads or improving bandwidth if you encounter io.netty.handler.timeout.ReadTimeoutException.
SocketException: Connection Reset: Check your internet connection and server console for related errors.
Server Returned HTTP Response Code: 503: This occurs when Minecraft.net is down. Monitor Minecraft news or Mojang’s status updates for information.
NullPointerException: Locate the Java crash log (e.g., hs_err_pid...txt on your desktop) to identify the cause of the issue.
Unable to Connect to World (Bedrock): Verify the IP, port, and server’s gametype compatibility. Check for console errors affecting the connection.
Authentication Error (Bedrock): Reload Minecraft, log out, and log back in using your Microsoft account. Wait if authentication servers are offline.
Failed to Open Curl Lib from Binary (Vanilla Bedrock): Rename or delete conflicting server files such as server.properties, or adjust the port settings.
Internal Server Error (PMMP): Identify the problematic plugin by reviewing the console logs and plugin configurations. Ensure plugin compatibility and stability.
Cannot Join Pocketmine Server: Repair your server’s configuration or replace it with a downloaded one. Alternatively, adjust the max-mtu-size in pocketmine.yml to 1450.
In the file manager, you might discover crash reports within a folder labeled crash reports. Inside, various reports are categorized by date. Locate the report from the day of the crash. Within this log, you'll uncover the sequence of errors leading up to the crash, along with system specifications. Familiarize yourself with the meanings of the following letters for this section: 'U' = Unloaded, 'L' = Loaded, 'C' = Constructed, 'H' = Pre-initialized, 'I' = Initialized, 'J' = Post-initialized, 'A' = Available, 'D' = Disabled, 'E' = Errored.
Here's an example:
| Status | ID | Version | Source | Signature |
| Loaded | Minecraft | 1.12.2 | minecraft.jar | None |
| Loaded | MCP | 9.42 | minecraft.jar | None |
| Loaded | FML | 8.0.99.99 | forge1122.jar | None |
| Loaded | Forge | 14.23.5.2847 | forge1122.jar | None |
If none of the fixes have resolved your issue, consider reinstalling (remember to create a backup first).
For unique joining issues, refer to the Minecraft help forum or reach out to Minecraft support. if you're still unable to resolve your error, initiate a live chat for assistance 👍.
Updated on: 29/06/2026