Common Minecraft Errors
To find the cause of the crash, click on the Files tab, then on
crash-reports, and look at the
Description near the top along with the next line. If you see one of the errors below, read that section. Otherwise, contact support so they can help you interpret the crash report.
ServerHangWatchdog detected that a single server tick took 60.00 seconds
This normally happens when there are items all over the ground or too many mob entities. So try the following:
- Stop your server if it isn't already.
- Under the Files tab, click on
-1(this will let your server start even with high tick times).
- Restart your server and wait for it to finish starting
- Use the following command in the console to remove hostile mobs:
- Use the following commands in the console to kill extra items and xp orbs on the ground:
kill @e[type=experience_orb]for newer Minecraft versions)
- Log in to your server and use the commands again but with a slash in front of them:
/kill @e[type=experience_orb]). You will need to be an Op to use these commands in-game.
60000and restart your server, so that the server lets you know when it's having a problem like that again by crashing, and so mobs start spawning again.
Caution on the Kill Command
Make sure to type the kill commands EXACTLY as they are. Do NOT change "type" to something else.
If that does not work to fix the crashes, you may need to roll back your server to before the crashes started. But feel free to contact support to have them take a closer look.
Moved too fast
If your server's console is saying "moved too fast" often, then there is likely some lag during chunk generation. To take care of that, see our article on lag and exploration.
Another setting that might also fix this issue is to set the gamerule for disabling the elytra movement check. This helps quite a bit in the more modern versions of Minecraft. To do so, in the console, use the following command exactly as presented:
gamerule disableElytraMovementCheck true
Can't keep up! Is the server overloaded?
Can't keep up! Is the server overloaded? can be completely ignored if it only shows up once or twice. For instance, it will say that on server load, when someone joins, etc. It's usually from syncing information and just normal loading.
It's only a problem if it is continuously showing in the console. If it is, see our article on lag here.
When you try to connect to a Minecraft server, sometimes you'll get an error preventing you from doing so. The following are some of the possible errors. If you don't see your error here, contact support so they can help figure out your error.
Can't Resolve Hostname or Unknown Host
When you create your server, you had to also create a friendly address similar to
example.g.akliz.net. That is a domain address. Domain Name System (DNS) servers transfer that information between each other across the world. That can take some time. So if you are getting this error, that means your DNS server has not received this information yet. So you can either wait about 30 minutes for it to do so, or you can connect using the ip:port located at the top of Command Center. It will look something like this:
Connection Refused or "Old"
You will usually receive this error when the server is not done loading. This can happen often with modded Minecraft. Some modpacks can take up to 15 minutes to load.
To test if your server is done loading, you can either use a test command in the console and see if you get the correct response, or you can check your server list and see if the player count has shown up:
Failed to login, Bad Login, or Invalid Session
These errors typically indicate something wrong with the Minecraft login servers which authenticate the player names with registered Minecraft accounts or that the player is not logged into the Minecraft launcher properly. It is not a problem with our service. You’ll be able to connect as soon as Mojang fixes the login servers or as soon as you login to the Minecraft launcher again when it appears. You'll also want to make sure that your account has been migrated from Mojang to Microsoft.
The best way to keep track of Minecraft service uptime is to check out the official Minecraft status Twitter account.
Forcibly Closed, Time Outs, Connection Lag, and High Ping
Sometimes you'll get timeouts, high ping, or the error Forcibly Closed when you try to connect to a Minecraft server. Try the following to fix the issue:
- Make sure you have 6-8GB of RAM allocated to your Minecraft client or launcher
- Make sure you have migrated to the Microsoft login
- Restart your computer
- Restart your router
- Reinstall the modpack, if you're using one, by deleting the folder and then installing the modpack again. Make sure to install the exact same version as your server.
- Use a wired internet connection instead of wi-fi if possible (satellite and mobile hotspots usually don't connect very well).
- Connect using the ip:port instead of the friendly address
- Refresh your IP and DNS. To do so:
- Press the Windows Key, then type
- Right-click Command Prompt and click Run as administrator
netsh winsock resetand press Enter.
netsh int ip resetand press Enter.
ipconfig /releaseand press Enter.
ipconfig /renewand press Enter.
ipconfig /flushdnsand press Enter.
- Press the Windows Key, then type
- Create a firewall exception for Minecraft and Java.
- On the Windows Search Bar: Search for "Windows Firewall"
- Click on "Windows Firewall" or "Windows Defender Firewall"
- Click on "Allow an app through Windows Firewall"
- Click Change Settings (Have to be an Admin)
- Scroll down to Java(TM) Platform SE Binary (there will be more than one)
- Tick the 'Private' checkboxes for all of those
- Click Ok
- Change your DNS provider
- Disable any anti-virus or VPN software that is running (or try a VPN if you're not using one)
- Try an alternate connection (like a mobile hotspot or wifi, as a temporary test).
- Try an alternate computer
- Check the Game Settings page on your server for any special instructions the modpack/game may have. (For instance, some really old modpacks require offline mode.)
- Restart your server
- Reset Playerdata for the player who can't connect
- If you were able to connect before, try rolling back the server to when you were able to connect.
Did that work?
If the above does not work, contact support and make sure to provide us with both Ping and MTR test results, and we can pursue further solutions.
Packets Too Big
Try adding a mod to the server that might help fix the issue:
- 1.7 - 1.12 Forge Bigger Packets Please
- 1.16 Forge - XL Packets
- 1.16 Fabric - XL Packets Fabric
- 1.18/1.19 Forge/Fabric - Connectivity
Kicked for Flying
See this article for instructions to enable flight on your server.
Mismatched mod channel list or Failed to synchronize registry data from server
These errors usually mean that the modpack running on your server and the version running on your client aren't the same.
To check the version of the modpack installed on your server, click on the Gear icon, then click Game Settings. Scroll past the modpack description, and look for the Installed Version.
Checking the version installed on your client will vary based on which client you're using, but it's most often listed in the top-right corner of the modpack profile.
If these versions aren't the same, you'll need to either update your client (please check the support for your launcher of choice) or you'll need to update your server.
Custom or Edited Modpacks
If this is for a custom modpack or a modpack that has been edited, you'll need to make the same changes to both server and client. When editing a modpack or creating a custom one, please make sure to test only one mod at a time so you know which mod you changed is causing the connection issue.
If these versions are the same, please contact support.
Took too long to log in
This happens when your computer is not able to load fast enough. Check that your launcher, such as CurseForge, has 8gb of RAM set up in the Minecraft settings.
Updated 4 months ago