MC-37175Reconnect/Joining servers not working
When I leave a server and try to reconnect to that server it says logging in, but nothing happens. So when I want to join that server, I have to restart Minecraft.
Environment
Win 8.1
Linked Issues
Low
Created Issue:
Reconnect to servers not working
When I leave a server and try to reconnect to that server it says logging in, but nothing happens. So when I want to join that server, I have to restart Minecraft.
Environment
Win 8.1
Reconnecttoservers not workingReconnect/Joining servers not working
is duplicated by
relates to
![[Mod] CubeTheThird](../../../data/assets/gravatar/cubethethird.jpeg){kind=small}
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
duplicates
relates to
is duplicated by
By parent ticket I believe it's MC-37175, although it seems to be mislabeled as "Relates to" instead of "Duplicate of"
Though don't take my word for it, I'm not sure.
MC-37175
Use search function.
I tried to reproduce the suggested duplicate issue MC-37175. I disconnected and reconnected to a server several (10) times without any problem. This could indicate that this is completely different problem.
I now changed the player-idle-timeout setting in the server.properties file from 0 to 30. So far it seems to remove the problem with io.netty.handler.timeout.ReadTimeoutException
I'm not sure to which issue you are referring, but this one duplicates MC-37175, which is still open.
Would like to confirm this issue in 1.7.2 (Windows 7, 64 bit java).
I have had this state occur in 1.7.2 regularly within 4 disconnects of a vanilla server or assortment of vanilla servers. It looks from console output that the client isn't even starting the handshake with the new server and will not start any more until the client is reset.
Steps to Reproduce:
1. Log in to a server
2. Disconnect from server
3. Log into another or the same server
4. Repeat until you cannot connect to any servers (Usually within 4-5 times)
Expected Result: You can reliably reconnect to servers
Actual Result: You can no longer connect to any servers
Note: You can see this happen if you have access to the server console that you are trying to connect to, it will not have any prints that acknowledge your connection. During this time the client says "Logging in..." until it times out. Due to the fact that this doesn't throw a specific error detailing the nature of the disconnection, it is bound to cause mass confusion among your players. This state persists until reboot.
I have been told to post under this ticket but I don't know why. We have been updated to 1.7.2 automatically under Windows 7 and we cannot connect to any servers, always getting io.netty.handler.timeout.ReadTimeoutException (including localhost) whether we restart or not.
Version 1.7.2 is unplayable here, can we get back to 1.6.4??
Same here : 95% chances to get the error "io.netty.handler.timeout.ReadTimeoutException"
So i can't play minecraft anymore. Very, annoying...
So we are gone back to using 1.6.4 with the Edit Profile option in the launcher. Also 1.7.2 regularly freezes in Single player on a 32 bit Windows 7.
Lots of people having this and similar issues are still reporting on MC-34947, though its been marked as resolved. This has made the game unplayable for me since 1.7 came out
The server I play on I am currently in the Nether. Every time I join the server, I can walk to my nether portal to go to my base. Once I enter the portal I get kicked with the Internal Exception: io.netty.handler.timeout.ReadTimeoutException error. Once I can rejoin (sometimes immediately, sometimes after i restart Minecraft, sometimes it requires a server restart) I am still in the nether. The game literally can't be played as it is. I've been encountering this problem since the 1.7 snapshots. Occasionally I can get through portals, but can only travel so far or a random amount of time and i get kicked again.
For the love of god please fix this, or any indication that someone at Mojang is listening or gives any craps about this would be great. Numerous people have posted about it on MC-34947 (which has over 100 comments on it at this point), this ticket has several duplicates and comments. People are encountering this error with different circumstances but we are all getting the error.
Haven't been able to play MC properly since the last few 1.7 snapshots and currently in 1.7.2.