Minecraft Error Messages

​

Multiplayer Errors

​

1. Connection refused: connect

• This means:
  • There is no Minecraft server online on the IP Address:Port you put in
  • The entire server (not just Minecraft) cannot be accessed
• You can try:
  • Confirm you’ve entered the correct server address/the server is configured correctly
  • Restarting the server, checking for errors

​

2. End of stream

• This means:
  • The server has stopped sending information back to the client for some reason.
• You can try:
  • Close and Reopen Minecraft and attempt to log in again.
  • Restart the server (if you have access to its console)
  • Check that both the server and your client has a clear connection

​

3. Failed to login: Bad Login

• This means:
  • You’ve attempted to log in too quickly after last attempt.
  • This may also apply to when a non-vanilla client attempts to connect to a vanilla server (or vice versa), but in this case generally indicates version number discrepancies.
  • This may also occur with unequal vanilla version numbers, though this has almost been entirely replaced with the Outdated Server or Outdated Client error messages.
• You can try:
  • Confirm that you are running the correct version of Minecraft for the server you wish to connect to. (Sometimes, server operators may not update the server straight away, but instead wait for their particular mods/server admin tools to catch up).
  • Check your network connection and your ping (lag) time. Your client may be getting kicked because the network is too slow to respond in time.

​

4. Failed to login: the authentication servers are currently down for maintenance

• This means:
  • The Minecraft server, running in online mode, could not contact the authentication server to confirm the identify of a player logging in
  • The server may show a log entry like com.mojang.authlib.GameProfile … lost connection: Disconnected
• You can try:
  • Play or do something else until the authentication servers return
  • Watch Mojang Status until the service status shows green
  • Set the server.properties to online-mode=false which disables authentication. Anyone can log in using any user name in this mode.

​

5. Failed to login: invalid IP

• This means:
  • The Mojang servers are unable to validate your IP address
• You can try:
  • Try again later
  • Watch Mojang Status until the service status shows green

​

6. Internal Exception: io.netty.handler.timeout.ReadTimeoutException

• This means:
  • The game could not keep up with the server, or that your computer cannot process the packets fast enough, causing you to fall too far out of sync with the server.
• You can try:
  • Getting a faster/clearer internet connection, a faster computer, or simply closing any programs that may be hogging your bandwidth/computer processing power. Remember to check the task tray on Windows - applications like Dropbox can consume a lot of bandwidth.

​

7. java.io.IOException: Server returned HTTP response code: 503

• This means:
  • The server cannot authenticate who you are because minecraft.net is down
• You can try:
  • Check the Minecraft Update News and the Mojang pages to check if there are planned outages (server maintenance, website updates etc)
  • Try again later
  • If this persists and there isn’t any reported outages, contact the server owner/administrator or a known operator (OP) and explain the situation

​

8. java.net.SocketException: Connection reset

• This means:
  • The server has shut down or is doing something very intensive.
  • This also occurs when the user’s internet connection dies or something in between the user and the server gets disconnected.
  • It is basically a very broad and common TCP/IP error. It means that something has happened to disconnect the connection in an abrupt and unexpected way.
  • Servers sometimes return this when in the process of shutting down or starting up, which may happen if the server does nightly backups/restarts. (Remember, your ‘night’ may be different to the server, especially if it is in another country!)
• You can try:
  • Try logging in again later.
  • If this persists, contact the server owner/administrator or a known Operator (OP) and explain the situation.

​

9. Outdated client!

• This means:
  • You’re connecting to a server on a newer version than the Minecraft you’re using
• You can try:
  • Change your Minecraft version to the one used by the server, using the Profile Editor in the Launcher

​

10. Outdated server!

• This means:
  • You’re connecting to a server on an older version than the Minecraft you’re using
• You can try:
  • Change your Minecraft version to the one used by the server, using the Profile Editor in the Launcher
  • Note: Sometimes, server operators may not update the server straight away, but instead wait for their particular mods/server admin tools to catch up, especially for pre-release versions

​

11. This server responded with an invalid server key

• This means:
  • This is actually a measure to stop an exploit with modified servers, but has a bug which causes it to have false positives in half of the connections.
• You can try:
  • Attempt to log in again.

​

12. Took to long to log in

• This means:
  • The server cannot authenticate who you are because minecraft.net wasn’t responding
• You can try:
  • Try again later
  • Check the Minecraft Update News and the Mojang pages to check if there are planned outages (server maintenance, website updates etc)
  • If this persists and there isn’t any reported outages, contact the server owner/administrator or a known Operator (OP) and explain the situation.

​

13. User Not Premium

• This means:
  • “Free”/cracked/hacked Minecraft clients do not pass the minecraft.net authentication.
• You can try
  • If you want to play on multiplayer servers you have to buy the game.

​

14. You are not whitelisted on this server

• This means:
  • You have not been added to (or have been removed from) the list of people who are allowed to connect to the server.
• You can try:
  • Contacting the server owner/administrator or a known operator (OP) and explain the situation.

​

Crashes

​

1. Failed to check session lock, aborting

• This means:
  • Most likely, there is an active lock on part of the world (either the terrain itself, or more likely an NBT saved element such as a player or chest) that a third party editor has left locked (or that you didn’t close).
  • You may only see this in the crash log.
• You can try:
  • Delete session.lock in the world save folder (contact an admin if you aren’t one and explain the situation).

​

2. java.lang.NullPointerException

• This means:
  • Minecraft sometimes crashes on startup, even when you are playing vanilla.
• You can try:
  • Find the Java crash log (typically a file named hs_err_pid…txt on your desktop) and see if you can find the error stated in there in one of the answers here.
  • A common error is EXCEPTION_ACCESS_VIOLATION together with a problematic frame. Search the answers for that frame.
  • Rename the ~/.minecraft directory so Minecraft can’t find it, then start Minecraft again and start a fresh game. This will generate a new ~/.minecraft directory. Exit Minecraft and copy the saved games from the renamed ~/.minecraft/saves directory into the new one. (related)

​

3. Runtime Errors

• com.google.gson.JsonSyntaxException or com.google.gson.stream.MalformedJsonException
  • Minecraft uses an external package by Google to parse all the json formatting, which is what the NBT format is based on.
• This means:
  • Your world may be corrupted.
  • There is invalid JSON/NBT formatting in your save files; tag names are defined as a “variable” instead of a string.
• You can try:
  • Going through the save files and searching for the malformed formatting. (See this example code to clear using Javascript)
  • This means {Tag:{ ... }} instead of {"Tag":{ ... }}, with … representing its compounded tags/contents.
  • Restoring your save to a previous backup where the problem has not occurred, and removing any mods that may have caused this.

​

4. java.lang.OutOfMemoryError

• This means:
  • Your game has run out of memory.
  • Heavily modded clients require a lot more memory (and processing power) as it has more blocks loaded onto it.
• You can try:
  • Increasing the amount of memory that is allocated to java by upgrading your service from the clientarea.
  • Close down any programs that you don’t need (to free up memory)
  • Reduce the number of mods
  • Upgrade to the 64-bit version of Java (requires a 64-bit computer).

​

5. RuntimeException: No OpenGL context found in the current thread. or org.lwjgl.LWJGLException: Pixel format not accelerated

• This means:
  • Your graphics card or driver is unable to handle Minecraft.
• You can try:
  • It could be as simple as updating graphics drivers, but this doesn’t happen often.
  • If this error occurs after installing or updating the operating system, you probably have default graphics drivers that do not support OpenGL. Install the drivers provided by your graphics card manufacturer instead of the default drivers.
  • On Linux systems, the RuntimeException: No OpenGL context found in the current thread error is sometimes corrected by installing a package that contains the xrandr utility.
  • Otherwise, you may need to purchase a newer graphics card for your PC.