I am running my own server. Everything was fine last night and this morning. Both server and client are v1.6.4. Server is Ubuntu 12.04LTS on AWS small instance, client is OSX 10.8.4.
As of this afternoon, 9/10 times when I try to connect my client hangs on the Logging In screen. Once I was able to connect, but mostly I get:
2013-10-13 16:06:12 [SEVERE] Reached end of stream for /1.1.1.1 java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:150) at java.net.SocketInputStream.read(SocketInputStream.java:121) at java.net.SocketInputStream.read(SocketInputStream.java:203) at java.io.DataInputStream.readUnsignedByte(DataInputStream.java:288) at ey.a(SourceFile:178) at co.i(SourceFile:249) at co.c(SourceFile:17) at cp.run(SourceFile:94) 2013-10-13 16:06:44 [INFO] Disconnecting dhgwilliam /1.1.1.1:54595: Took too long to log in
Minecraft Sessions (Legacy) is reporting that it is down. I was assuming that the Legacy tag meant it wasn't relevant to my (brand spanking new) server, but after reading more it seems to me that this is related (where by "related" I mean "the cause"). Will disabling online-mode be an effective temporary workaround?
EDIT: I can confirm that disabling online-mode is an effective workaround, if you control your own server.
David Gwilliam
I am running my own server. Everything was fine last night and this morning. Both server and client are v1.6.4. Server is Ubuntu 12.04LTS on AWS small instance, client is OSX 10.8.4.
As of this afternoon, 9/10 times when I try to connect my client hangs on the Logging In screen. Once I was able to connect, but mostly I get:
2013-10-13 16:06:12 [SEVERE] Reached end of stream for /1.1.1.1
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:150)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at java.net.SocketInputStream.read(SocketInputStream.java:203)
at java.io.DataInputStream.readUnsignedByte(DataInputStream.java:288)
at ey.a(SourceFile:178)
at co.i(SourceFile:249)
at co.c(SourceFile:17)
at cp.run(SourceFile:94)
2013-10-13 16:06:44 [INFO] Disconnecting dhgwilliam /1.1.1.1:54595: Took too long to log in
Minecraft Sessions (Legacy) is reporting that it is down. I was assuming that the Legacy tag meant it wasn't relevant to my (brand spanking new) server, but after reading more it seems to me that this is related (where by "related" I mean "the cause"). Will disabling online-mode be an effective temporary workaround?
EDIT: I can confirm that disabling online-mode is an effective workaround, if you control your own server.