Server Errors & Troubleshooting
Server Errors & Troubleshooting
15 ArticlesUnable to Place Command Blocks
Sometimes, Minecraft servers don't generate their files properly when you start your server for the first time, causing certain bugs to occur that you may not notice. A common example of this is being unable to place command blocks, despite the configuration being correct. This guide will help you resolve this issue. ::ProseNote{title="Important" description="This guide includes deleting server files. For the purpose of this guide, please ensure you do not include your world folder, plugins folder or server.properties file, unless you are okay with deleting them. If you are unsure of how to enable command blocks, you can follow our guide here." appearance="default"} :: Resetting Server Files on Your Server If you still find yourself unable to place command blocks, you will need to regenerate your server files. You can follow these steps: 1. Login to your server's control panel and Stop your server. 2. Navigate to the Files tab. 3. Tick the checkbox next to the files you wish to delete and click on Delete. If you wish to keep your world and plugins folder, do not tick the checkbox next to these folders. 4. A window will appear; click on Delete if you wish to proceed with deleting your server files. ::ProseNote{title="Important" description="Please note that this will permanently delete your files. This action cannot be reversed, so please make sure that you have a backup of all your server files and that you understand what you're about to do before proceeding to prevent any loss of server data." appearance="default"} :: 5. Start your server to redownload the default server files. Your server should regenerate the main server files, and you should still have your world and all plugins. If you have followed these steps and you still cannot place command blocks, follow them again; however, delete the plugins and world folder this time after taking a backup. --- If you require any further assistance, please contact our support at: https://shockbyte.com/billing/submitticket.php
My Minecraft Server Won't Start
If your server isn't starting, it could be caused by a variety of issues. The steps below should allow you to find and resolve the issue. 1. Check your console for any errors. This is always the first step if something goes wrong. Errors in your console will most often be able to tell you what's going wrong. 2. Check your Files tab for a Crash Reports folder. If there is a folder, view the latest crash report, as this may also be able to tell you what went wrong. If you are having trouble reading your Crash Report, reach out via a Support Ticket for further assistance. 3. Temporarily rename your plugins directory and restart your server. This will load your server with no plugins, so if this resolves the issue, you will know one of your plugins is causing the problem. To find which specific plugin is the issue, you can disable individual plugins one by one (by renaming the .jar at the end to .jar.disabled) and start your server each time until you find the specific plugin causing the issue. 4. Stop your server, navigate to the Config tab and rename your World temporarily. If this resolves the issue, there is likely world corruption or an invalid block/chunk on your original world that is causing your server to crash. If this is the case, we recommend investigating your Crash Reports for any information regarding the corrupted world or chunk and following our guide on fixing World Corruption here. One other common cause is excessive item entities. If an item duper was left on by mistake, and spawned in tens of thousands of items, the server will crash. --- If you require any further assistance, please contact our support at: https://shockbyte.com/billing/submitticket.php
Minecraft Server Cant Keep Up
If you’ve been facing lag or performance problems with your server, there’s a good chance that your console will be displaying warnings that look similar to this. If you see these messages, it means that your server may be suffering from server-side lag. This can be caused by a lot of different reasons; however, we have a few tips to help you solve it. This guide will teach you how to identify and reduce server-side lag. --- What is Server-Sided Lag? Server lag affects every player on the server, regardless of their internet connection or their PC performance. Server lag is usually measured when a server’s Ticks per Second (TPS) begins to drop. You can view your server’s TPS by using the command for a Spigot/Paper server. Alternatively, you can run a Spark Profiler on your server for a more in-depth profile of your server performance. Spark is supported on servers that run plugin or modded server types such as Paper, Spigot, Forge, etc. --- General guidelines for TPS rates 20 TPS: Your server is running perfectly fine and experiencing no issues. 19-20 TPS: Minor lag; however, your server is still fine, with no noticeable lag. 17-19 TPS: The server is beginning to struggle. The lag is minor and mostly unnoticeable. It isn’t a cause for concern. 17 TPS and below: You will see noticeable lag and issues within your server. When your server’s TPS drops, the lag becomes apparent to all players on the server. Many simple interactions, such as eating food, consuming potions, and breaking blocks, will take dramatically longer to complete. Basic mechanics, such as the day/night cycle, will begin to stutter. In short, the game becomes harder to play. --- Causes for Server-Sided Lag There are many factors to keep in mind when trying to find sources of server-side lag. For example, how much RAM your server has, how your server is configured, and potential in-game causes are the main reasons to look out for. --- Not having enough RAM Your server could be performing poorly simply because it does not have enough RAM. When the Minecraft engine runs out of RAM, it will try to unload data stored in RAM and write it to the Disk. It then has to read the necessary data from the disk into RAM. This process takes a lot of time and CPU usage. Every mod, plugin, and player needs unique data to be loaded into RAM. So when there is no RAM available, your server will experience lag because of the reshuffling of data between disk and RAM. We have a guide on choosing what size plan is best suited for your server here. If you are looking to upgrade your server, you can read more on how to do so here. --- Server Configurations Configurations in your config files, such as and , affect task-load on your server. There are also settings particular to certain server versions, such as for Java 1.15 or 1.16+, and for Bedrock servers. You can read more on adjusting your View Distance here. Not only are there specific settings you can change, but there are also different Server Types, such as Paper, which are built around the goal of optimization. For those who aren’t looking for a modded experience, we highly recommend using Paper as the server type due to their implemented performance optimizations and proven stability. --- In-Game Causes There is a multitude of events that occur in-game that can cause your server to stutter or fall behind. Things to minimize or monitor the use of are as follows: Too many Entities: Large mob farms can cause serious lag, especially if the mobs are constantly colliding with each other and jittering about. We have a guide for reducing entity lag here. Too many Item Entities: Farms or item dupers that generate thousands of item entities can also cause major lag. This often happens when item dupers are left running and flood the server with dropped items. Lighting updates: Many Redstone components cause lighting updates. Keep Redstone circuits well-lit will reduce the number of lighting updates. Avoid having too many flashing lamps. Large fluid updates: Large amounts of moving lava or water can cause lag on your server. Hoppers: Any hoppers without a container above them will constantly look to draw in item entities. They will also check their own inventory constantly, check inventories above them and check if it’s pointing into an inventory and if it can push items into that inventory. This, especially in large quantities, can add up and cause a lot of stress on a server. Entities with duplicate UUIDs: This occurs more commonly in modded servers but can be caused by in-game bugs. You will see errors in the console regarding ‘entity already exists with UUID’. The only way to fix this is to use the command to remove the entity. Generating new terrain: Chunk generation is another very heavy task that has the potential to overload your server if a player is moving too quickly, via a boat, minecart, horse, or by flying. --- Reducing Server-Side Lag Reducing server lag depends on the server type you are using. Therefore, we highly recommend you check out our specific guides for each server type and other general ways to reduce lag. You can find them below. How to Reduce Lag on a FabricMC Server How to Troubleshoot Lag on a Forge Server Optimizing spigot.yml to Reduce Lag Optimizing bukkit.yml to Reduce Lag Optimizing paper.yml to Reduce Lag How to Pre-Generate Your Minecraft World using WorldBorder Plugin How to Automatically Restart Your Minecraft Server Using Plugins to Reduce Lag on Your Minecraft Server --- If you require any further assistance, please contact our support at: https://shockbyte.com/billing/submitticket.php
How to Agree to Your Minecraft Server's EULA
Sometimes, when booting up a Minecraft Java Edition server, you will get the error message: Minecraft’s EULA (End-user license agreement) impacts all servers and clients, including Bukkit, Spigot, and Forge servers. The full EULA can be found here. Please also note that, as per our Terms of Service, if your server is found to be in violation of Mojang's EULA, your server may be suspended until you have removed the violating content from your server. --- How To Agree To Your Server's EULA You can agree to your server EULA within the file. 1. Make sure that your server is stopped using the Stop button 2. Navigate to the Files tab. 3. Locate and open the file. 4. Fully read the EULA before changing to . 5. Click on Save & Exit. 6. Start your server. You should now be able to start your server without experiencing any additional EULA related issues.
Troubleshooting "Set PluginClassLoader as Parallel Capable"
If you're receiving the error and your server isn't starting, this would suggest you have installed a plugin from an untrusted source. Nulled, cracked, or pirated software very often contains back doors or malicious code that can cause damage to your server. Installing software from untrusted 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 like Modrinth, Spigot, or BukkitDev should resolve your issue. If you're not sure which plugin is causing the issue, you can disable or delete plugins one by one until you find the plugin causing the issue.
Troubleshooting Every Minecraft Server Issue
Minecraft server errors are almost always caused by software, meaning the plugins, mods or worlds on your server. This guide explains how to troubleshoot any issue and find the cause of your problem every time. --- Troubleshooting a Minecraft Server 1. Check your console for any errors This is always the first step if something goes wrong. Errors in your console will usually be able to tell you what's wrong. You can also refer to your error logs located in the folder in your server's directory for full logs of the past and present. 2. If your server crashed, check to see if any crash reports were generated If your server has crashed recently, it is likely that it will generate a crash report. If you are unsure of how to, feel free to read our guide on how to locate and read crash reports. 3. Temporarily rename your plugins directory and restart your server This will load your server with no plugins, so if this resolves the issue, you will know a plugin is causing the problem. If this is the case, you can usually rule out world corruption from being a potential cause, which is great to know. If you're running mods on your server, generate a backup before you try this same method out with the mods folder. 4. Temporarily rename all your world folders and restart your server Generate a backup of your server, then rename each world directory before restarting your server. If the server was not starting, but starts without problem after changing the world folder name, this would indicate world data corruption is at play. Feel free to refer to our guide on the topic here if your world is experiencing corruption. If option 3 or 4 resolves the issue, then you will know it is caused by either a plugin, world corruption, or an invalid block/chunk. If it's caused by a plugin, you can disable individual plugins one by one (by renaming the at the end to something like ) until you find the specific plugin causing the issue. If the issue is world or chunk-related, you should check out our article on fixing world corruption here. For more assistance with troubleshooting your server, feel free to check out our other troubleshooting articles here, or contact our 24/7 support team for additional help.
Troubleshooting Common Java Error Exit Codes
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 | | ----- | ----- | ----- | | | 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. | | | 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. | | | 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! | | | 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. | | | 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. |