Server Errors & Troubleshooting
Server Errors & Troubleshooting
15 Articlesjava.lang.IllegalArgumentException: ChunkNibbleArrays should be 2048 bytes not: 0
If your server is crashing with the error , it means that your world has become corrupt. This error usually occurs when switching between server versions (such as between 1.12.2 and 1.13.2) or server types (such as between Forge and Spigot/Vanilla). It is especially likely when downgrading to a lower version or switching between vastly different versions. Luckily, we have a guide providing more information and steps on how to fix corrupted world chunks. So you can either fix the corrupted chunks manually, or you can generate an entirely new world.
How to Fix Ticking Entity Errors
What is a Ticking Entity? An entity is a dynamic, moving object in your Minecraft world, like mobs or minecarts. Each entity has data associated with it, such as its name, inventory, or time alive. Rarely, this data can be corrupted. If the server is incapable of fixing the data, it will crash with the Ticking Entity error. Ticking Entities errors can occur in Vanilla Minecraft; however, they are most common in larger modpacks. If your server is immediately crashing upon you trying to join, this is most likely due to a corrupt Ticking Entity located in the same chunk your character is trying to load in at. Your server will try to read the information of the chunk surrounding that player and will then crash because the entity inside of it is corrupted. Other players may be able to join if they are not in the same chunk, but the server will crash immediately upon any player entering the chunk with the corrupt entity. When a corrupt Ticking Entity is created in your server, it will permanently affect your world data. --- Ticking Block and Ticking World There are two other variations of this type of crash. These are ‘Ticking Block’ and ‘Ticking World’ crashes. A Ticking Block error is tied to a corrupted tile entity associated with a specific block. Ticking Block crashes are usually caused by things like modded crafting tables or machinery. A Ticking World error, on the other hand, is when an entity is corrupted. These are the most severe cases of this crash, as it is harder for your server to precisely locate the corrupted entity. --- Methods for Resolving the Error There are a few methods for resolving this error. Please follow the method best suited for your situation. --- Method 1: Restoring a Backup If you have a backup created of your server, you can simply restore your server to a previous state before the corrupt Ticking Entity appeared. This will resolve your server crashing and allow you to carry on as normal. You can learn how to restore Server Backups here. --- Method 2: Forge Configuration Forge servers have a toggleable config option, which, when enabled, automatically removes any problematic entities or blocks. Steps for locating this config will depend on which version of Forge you have installed. Please follow the appropriate instructions based on your version of Forge. 1. Access your server's control panel and navigate to the Files tab. 2. Navigate to the Forge configuration file. Depending on your Forge version, locate and edit the specified file: Forge 1.13 and newer: Open Forge 1.12.2 and older: Open 3. Once open, locate the lines and . Set both of these to true. 4. Save the changes, then Start your server. ::ProseNote{title="Note" description="Your server must be able to start up and run without crashing for this method to work. However, you do not have to join the server as a player to run this command." appearance="danger"} :: --- Method 3: CoFH Core A lot of popular modpacks will have CoFH Core installed, but if your server doesn’t, it is a very simple mod to add, and its commands are incredibly useful for dealing with corrupt Ticking Entities. If you need assistance with adding a mod to your Minecraft Forge server, please use our guide here. 1. Locate the corrupted mob in your Crash Report. You can do this by scrolling through your Ticking Entity Crash Report and looking for the section labelled . 2. In this area, look for the Entity’s name and copy it. 3. In your console, enter the command . 4. Alternatively, you can just use the command ; however, please note this will delete all mobs from your server. --- Method 4: Vanilla Method This method will only work if the corrupted Ticking Entity is considered a hostile mob. However, it is worth trying if you are unable to back up your server or use mods. 1. Go into your server settings and reduce your View Distance. 2. Change the game difficulty to ‘Peaceful’. 3. Save the changes and Restart your server. Once your server is started and you can successfully join without crashing, you can revert your View Distance and Difficulty back to normal and restart your server to resume normal gameplay. --- Method 5: World Editors The final, most effective method for fixing Ticking Entity errors is using software for Minecraft World editing to remove the chunk in which the corrupt Ticking Entity is stuck. Programs such as MCASelector or NBT Explorer can help you with this. Before attempting this method, we highly recommend you make a backup of your world folder in case you make a mistake and need to undo your edits. If you are interested in learning how to use NBT Explorer, we have a wonderful guide that can help you here. --- If you require any further assistance, please contact our support at: https://shockbyte.com/billing/submitticket.php
How to Fix Missing Mods (MissingModsException)
Some Forge mods are dependent on additional mods to run. This is because sometimes a mod requires a certain library, or is built as an addon to an existing mod rather than as a standalone mod. If an additional mod is required by any mods you have installed, it will be classed as a "Missing Mod" because it is not installed on your server. When there is a missing mod, your server typically won't start or will continue to crash until you have installed the required mod. When servers crash due to this error, generally a crash report will be produced. In the crash report, you will see "Missing Mods:", followed by a list of mods and their versions. Once you've located the missing mod, you can generally just Google it to find a download. Once you have uploaded the new required mods to the mods folder, restart your server and connect! ::ProseNote{title="Existing World" description="If you’re still experiencing this error and you are certain that the mods are installed, the issue might be that the world was generated before adding them. In that case, try switching to a new world. This is recommended after installing mods for the first time so they load correctly, especially those that affect world generation. See our guide on this here." appearance="default"} :: --- Missing Mods: Forge In some instances, the crash report will show a MissingModsException but indicate Forge as missing. Forge isn't a mod but a server type. This error indicates that you have a version of Forge that is not compatible with the mod(s) installed on your server. This either means that you need an older or newer version of Forge. You will want to look at line 6 and below of your crash report; it'll tell you which Forge version your server needs. You can either change your Forge version by editing your Server Type or by downloading the specific version required from https://files.minecraftforge.net. If downloading Forge manually, you can then follow our tutorial on How to Install Forge on your Minecraft Server.
How to Fix Connection refused: no further information (Windows 10/11)
The error message indicates that there is a connection issue when trying to connect to a Minecraft server. This could be caused by a few things, such as the server being offline, an incorrect IP address or an issue with a person's firewall. --- Common Causes Firstly, ensure that the server is online. When using a Shockbyte server, you can see from your server's control panel an online status indicator. Secondly, you may receive this error when the IP address you attempt to connect with is incorrect. Ensure when connecting to a Minecraft server that you enter both the IP & Port. If you are using a Shockbyte server, you can find the IP & Port on the home page of your server's control panel. Configuring Firewall - Windows 11 You may be experiencing this issue if Firewall has blocked the connection to Java programs. Navigate to your Firewall configuration to edit this. These are the steps for Windows 11. 1. Open Windows Start Menu, and search Windows Defender Firewall. 2. Click Allow an app or feature through Windows Defender Firewall. 3. Click Change settings. 4. Locate any apps or features that are named Java, and ensure they are enabled for both Public and Private. There may be multiple. 5. Once done, click Ok at the bottom and restart Minecraft. --- Configuring Firewall - Windows 10 For Windows 10 users, please follow these steps instead. 1. Open the Windows Start Menu, and search Windows Defender Firewall. 2. Once the new window opens, in the left-hand pane, select Allow an app or feature through Windows Defender Firewall. 3. Click Change Settings. 4. Find any app/feature with the name Java(TM) Platform SE binary (there may be multiple) and ensure both Public and Private are checked for each one, along with the left-most checkbox. 5. At the bottom of the window, click OK and close this page. 6. Restart Minecraft, and attempt to connect to the server. If you have followed these steps correctly, you should no longer experience the aforementioned error when attempting to connect to your server; however, should you continue to see this error, you can try using a different version of Minecraft on your server by changing your server type or contacting your internet provider to see if it is an issue with your network.
How to Find and Read a Minecraft Server Crash Report
If you’re ever running a server and it crashes, server crash reports are your best tool in finding what caused the crash, and can help you and anyone else trying to fix your server. When a server crashes, it will usually generate a crash report, which will contain all the information needed to find the cause of the crash, as well as the steps required to fix it. If your server crashed and made a crash report, you’ll see a message in the console, where the name of the file will be the date and time the server crash occurred. --- How to Find a Crash Report Crash reports can be found within your server files, which are accessible on your Shockbyte Panel. 1. Access your server's Control Panel and navigate to the Files tab. 2. Click on the folder in your server files called . Note: If this folder does not exist, it means the server has not generated it yet. The folder will only be created when the server stores a crash report inside of it. Alternatively, you can check the console log for more information or contact support for further assistance. 3. Click on the newest crash report to open it; the date and time are in the name of the crash report. The crash report will now open, where you will see the error that made your server crash. --- How to Read a Crash Report The quickest way to find the cause of a crash report is to look at the “Description:” part of the report. This will often describe what caused the crash. If you are having issues understanding what the description means, then you can always copy and paste it into Google, as this will often bring up pages where other people are having the same issue as you. Despite this, there are some common errors that you could have on your crash report: Ticking Entity - This most likely means that there is a corrupt entity in your world. This type of world corruption is most likely to be fixable without losing the whole world (but is much easier to fix by generating a new world). Ticking World - This most likely means that the entire world itself is corrupt; this is usually caused by changing your version of Minecraft (creating a new world should fix this). There are plenty of other crash reasons, and even more if you are running a modded server, so if you’re still having issues with your server, feel free to submit a ticket so that our Technical Team can take a look at your crash report for you. When making a ticket, we suggest uploading the crash report to a website such as pastebin, making it easier for us to read.
DirectLeaks Error
If you're receiving the error "Your Account on DirectLeaks has been Banned!" and your server isn't starting, this would suggest you have installed a plugin from an untrusted source. DirectLeaks is a website that hosts unauthorized downloads for premium Minecraft plugins. Nulled/cracked software like this very often contains backdoors or malicious code that can cause damage to your server. Installing software from unofficial sources is never recommended and is very risky. If you are receiving this error, removing any plugins that weren't downloaded from an official source (Spigot, BukkitDev) should resolve your issue.
BlackSpigot Error
If you're receiving the error and your server isn't starting, this would suggest you have installed a plugin from an untrusted source. BlackSpigot is a website that hosts unauthorized downloads for premium Minecraft plugins. Nulled/leaked software like this very often contains backdoors or malicious code that can cause damage to your server. Installing software from unofficial sources is never recommended and is very risky. If you are receiving this error, removing any plugins that weren't downloaded from an official source (Spigot, BukkitDev) should resolve your issue.