The issue here and now is not the "power" of the servers... Tobias himself confirmed they host in AWS and the load is distributed across multiple instances (i.e. theres not 1 login server, there's ~50). See: https://twitter.com/mollstam/status/381934116071309312 Also, just to clear up how the login and session process works: When you log in to MC, you connect to either the Legacy or Mojang login servers, which generate a session token that is then stored in your client and on the Session servers When you connect to a server, your client sends the session token to the server, which in-turn sends the token to the session server to verify it against what is stored in the Session database. If it matches, it lets you in... if it doesn't match, then you get the Bad Login error. False: If the server were unable to connect to the Session servers, you would receive an HTTP error (501, 500, etc.) or an error stating that it was unable to connect to the Session servers (depending on the Minecraft version and Server version). The "Failed to login: Bad Login" error means you have an invalid session token (usually as a result of logging on in another location or minecraft window). After some research, it appears that the issue we are experiencing now only affects servers that are running version 1.6.x and below. Granted, I'm still doing so me research in to this. My theory is that that Mojang has changed the way that Session tokens are generated and authenticated in 1.7, and somehow their legacy session support (not the same thing as legacy accounts) has been broken. As for why some people can connect and some people can't, it's because those people still connecting still have a valid token (haven't logged in to Minecraft in another window (i.e. launched and logged in to the vanilla client, then came back to the Alice client)) and haven't gotten a new, broken token from the session servers. Granted, this is all just theory at the moment. Regardless, you can all rest assured that we are looking in to the issue and will update you all as more information. EDIT: Just confirmed my theory - http://www.minecraftforum.net/forum-151/announcement-78-bad-login-errors-on-164-and-older/ (wondering how I missed this earler... meh, it's been a long day)
I appreciate this a lot more than what was said earlier. Much better. So Informative. Very Thanks. Wow.
Just being picky but it would be a 40x error if you can't connect. 50x is permission errors I beleive.
400 series errors are File/Folder errors (including permissions), and 500 errors are Server/Service errors. EDIT: and actually I meant to list error 503, not 501 or 500. -_-
I was linking to explanation of what was going on instead of repeating it in an irrelevant thread. Sorry if it seemed like I was being rude.
ok see i used to be in the same server farms as mojang and it allways had issues (EC2 (N. Virginia) ) and we moved to ( EC2 (Oregon)) and have no problems! also if i wanted a damm war on the feed to let people know ide ask for one !
As I've explained, this has nothing to do with the data center... it's a change to the way sessions are handled. Server farm has nothing to do with it. This is a forum, discussion will happen, and occasionally people will get pissed. No need to get mad about it becoming a "damm war on the feed."
EDIT: I read about this in another thread and I am now using MultiMC, please ignore this Uhm, I dunno what this was, I was always able to connect until now... I'm getting this:
