Matt0808
Career
- Joined
- Apr 19, 2012
- Messages
- 543
- Reaction score
- 207
Resolving Common Connection Problems
I have noticed a large number of users asking questions about errors they are getting when connecting to the server. This should help all users with errors in the future.
Multiplayer Errors
First we will be discussing errors that only happen when you are playing on and logging on/out of a server.
I have noticed a large number of users asking questions about errors they are getting when connecting to the server. This should help all users with errors in the future.
Multiplayer Errors
First we will be discussing errors that only happen when you are playing on and logging on/out of a server.
Connection refused: connect
There server you are trying to connect to is down. There is not much you can do except wait to fix this error as it is a server problem.
There server you are trying to connect to is down. There is not much you can do except wait to fix this error as it is a server problem.
You are not whitelisted on this server
The administrators of the server have put a whitelist on the server in question. A whitelist only allows certain users to connect if you are not on the list you cannot connect.
The administrators of the server have put a whitelist on the server in question. A whitelist only allows certain users to connect if you are not on the list you cannot connect.
User Not Premium
Free or hacked Minecraft clients do not pass the minecraft.net authentication, if you want to play on the servers you have to buy the game.
Free or hacked Minecraft clients do not pass the minecraft.net authentication, if you want to play on the servers you have to buy the game.
java.io.IOException: Server returned HTTP response code: 503
Server cannot confirm who you are with minecraft.net because minecraft.net is down. Another problem you can't do much about other then wait. This is a problem with the Minecraft server.
Server cannot confirm who you are with minecraft.net because minecraft.net is down. Another problem you can't do much about other then wait. This is a problem with the Minecraft server.
Failed to login: Bad Login
Logging in too quickly after last attempt or when someone has logged in to your account while you are still logged in. 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.
Logging in too quickly after last attempt or when someone has logged in to your account while you are still logged in. 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 unequalvanilla version numbers, though this has almost been entirely replaced with the Outdated Server or Outdated Client error messages.
End of stream
Server has stopped sending information back to the client. Again, you can't do much to fix this.
Server has stopped sending information back to the client. Again, you can't do much to fix this.
Took to long to log in
minecraft.net wasn't responding so the server cannot authenticate you. This can sometimes be fixed by restarting your internet or computer. If that doesn't work, once again be patient and wait.
minecraft.net wasn't responding so the server cannot authenticate you. This can sometimes be fixed by restarting your internet or computer. If that doesn't work, once again be patient and wait.
Outdated server!
If you use a pre-release version or a version that has just been released, servers are unlikely to support it until plugins have been updated for it. For example when you login with 1.8 but the server is still running on 1.7.
If you use a pre-release version or a version that has just been released, servers are unlikely to support it until plugins have been updated for it. For example when you login with 1.8 but the server is still running on 1.7.
java.net.SocketException: Connection reset
Either the server has shut down or is doing something very intensive, try logging in again later. 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. Try restarting your internet and/or computer.
Either the server has shut down or is doing something very intensive, try logging in again later. 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. Try restarting your internet and/or computer.
Outdated client!
You're connecting to a server on a newer version than the minecraft you're using, this either means you didn't hit the update button or they are running a pre-release server. For example you're running on a 1.7 client and the server is running 1.8. Try updating your client to the version of the server.
You're connecting to a server on a newer version than the minecraft you're using, this either means you didn't hit the update button or they are running a pre-release server. For example you're running on a 1.7 client and the server is running 1.8. Try updating your client to the version of the server.
This server responded with an invalid server key
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. Try reconnecting to the server. If that doesn't work contact an administrator.
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. Try reconnecting to the server. If that doesn't work contact an administrator.
Failed to check session lock, aborting
You may only see this in the crash log. 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. 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).
Internal Exception: io.netty.handler.timeout.ReadTimeoutException
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 fix this by getting a faster/clearer internet connection, or a faster computer, or simply closing off any programs that may be hogging your bandwidth/computer processing power.
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 fix this by getting a faster/clearer internet connection, or a faster computer, or simply closing off any programs that may be hogging your bandwidth/computer processing power.
Runtime Errors
An error that can occur at any point while playing the game.
java.lang.NullPointerException
This is not an error message, but rather a crash message. Minecraft sometimes crashes on startup, even when you are playing vanilla. This typically means that one or more Block IDs conflict with each other. This normally occurs on heavily modded clients or modpacks, such as Tekkit or Feed The Beast.
This is not an error message, but rather a crash message. Minecraft sometimes crashes on startup, even when you are playing vanilla. This typically means that one or more Block IDs conflict with each other. This normally occurs on heavily modded clients or modpacks, such as Tekkit or Feed The Beast.
RuntimeException: No OpenGL context found in the current thread.
org.lwjgl.LWJGLException: Pixel format not accelerated
If the player is given this message when starting Minecraft, it means that they do not have a graphics card that can handle Minecraft. It could be as simple as updating graphics drivers, but this doesn't happen often and users getting this error should get a new graphics card and/ or computer if too old and slow.
org.lwjgl.LWJGLException: Pixel format not accelerated
If the player is given this message when starting Minecraft, it means that they do not have a graphics card that can handle Minecraft. It could be as simple as updating graphics drivers, but this doesn't happen often and users getting this error should get a new graphics card and/ or computer if too old and slow.
java.lang.OutOfMemoryError
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 stop this error by increasing the amount of memory that is allocated to java, close down any programs that you don't need (to free up memory) or reduce the number of mods/upgrade to the 64-bit version of Java in order to allocate Problems
low on RAM you can always buy a new stick of RAM, they are about $11 per GB.
Please remember to visit this thread (click the link) if you have any issues or need any help in the future!
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 stop this error by increasing the amount of memory that is allocated to java, close down any programs that you don't need (to free up memory) or reduce the number of mods/upgrade to the 64-bit version of Java in order to allocate Problems
low on RAM you can always buy a new stick of RAM, they are about $11 per GB.
Please remember to visit this thread (click the link) if you have any issues or need any help in the future!
Last edited:
