Here is an example of someone attempting to log in on to my server, everyone keeps timing out. This seems out of no where, anyone know the possible issue? CB 1337 Code: 21.10 20:08:57 [Server] SEVERE at net.minecraft.server.ThreadLoginVerifier.run(ThreadLoginVerifier.java:34) 21.10 20:08:57 [Server] SEVERE at java.net.URL.openStream(URL.java:1010) 21.10 20:08:57 [Server] SEVERE at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436) 21.10 20:08:57 [Server] SEVERE java.io.IOException: Server returned HTTP response code: 504 for URL: http://session.minecraft.net/game/checkserver.jsp?user=ChapelGentry&serverId=e51202ab685e94ff 21.10 20:08:57 [Server] INFO Disconnecting ChapelGentry [/71.192.228.241:60448]: Failed to verify username! [internal error java.io.IOException: Server returned HTTP response code: 504 for URL: http://session.minecraft.net/game/checkserver.jsp?user=ChapelGentry&serverId=e51202ab685e94ff]
I think Bukkit is having trouble connecting to Minecraft.net's username verification service. Maybe it's down? Edit: Yep, it's down. Wait for a bit while the people at Mojang sort this mess out.
What's funny to me is that they are so close to a minecraft release as non beta and yet they still have not managed to with all of the money and resources they can possibly get hold of to once and for all sort out the stability issues with the login and username authentication servers. You would not be blamed for assuming that by now they should have a cloud setup with cluster server load balancing + a fall back server to prevent these issues. You also would not be blamed for having a rant about the fact they still fail every couple of months or sooner.
