We are aware of you are getting a bad login sadly that's not us that's the friendly folks at mojang's problem
Thank you for letting us know. I was starting to get ticked off cause nether of my accounts could login.
https://help.mojang.com/customer/portal/articles/1218708-error-bad-login The only people who are assuming it's mojangs fault are people on forums. Wouldn't Mojang come out with a press release about it by now?
Well, considering that I am unable to connect to any server in online mode (including one hosted on my test server which is on the same network as my main machine), but yet I can connect fine when they are in offline mode, I don't see how it's a "problem in communication between your computer/network and the server that you are trying to connect to" as that article says is the issue. If it were only a small few people having this issue, then that might be a logical to think there was a connection issue... but with a significant number of people experiencing the same issue, it's obviously a Mojang problem. Also, while trying to connect to my own servers, I can access them fine via SSH, web, and any other protocols in use on the server, further disproving the contents of the article you linked. If Mojang is sending people here, then they obviously don't realize there is an issue, or they are simply trying to deny it. Regardless, they're sending people the wrong place. Given the evidence and by using logic and common sense, it's clear that it's a Mojang issue, and not a user issue.
Looks like it's fixed now, guys. Hip hip hooray. Time to throw a party. EDIT: Nevermind, lucky streak :\
Ah, it's probably good to note to the people who can't seem to log on that is is actually an easy way to do it. It just requires some time, patience and maybe a cup of coffee. The secret to logging on is simply to keep trying to log in even after getting the bad login message. It should get you on in under 5 minutes of time. Since this is a problem with minecraft versions <1.7, it means it's not a problem with your account, it's mojang. So, because of that, there is no need to change your password, reinstall skcraft or any of that silliness. ------------ Sort of a whole explanation of this on twitter. Spoiler Tim @Tim_Gras 8h@Dinnerbone @jeb_fix the whole bad login error! Its bothering me and everyone else... destroy that error fix it in 1.8 Expand Nathan Adams @Dinnerbone 8h@Tim_Gras It's not effecting 1.7 Expand Galaxy_2Alex @Galaxy2Alex 6h@Dinnerbone @Tim_GrasThat's not a valid argument: Due to all the changes to 1.7, many server are not updated. You can't drop 1.6 support! Expand Nathan Adams @Dinnerbone 6h@Galaxy2Alex @Tim_GrasWe're not dropping 1.6 support, that was in a reply to request we fix it for 1.8... it's "fixed" for 1.7 already Hide conversation So why exactly does it say "1." on t he bottom of this post ._.
First off, I never inferred it was a user issue. Secondly That's great that you can connect to a server in your personal network. That's not the issue. The issue is there is something wrong with the information transfer between the mojang and the play server. If it was only an issue with Mojang wouldn't it stop you the minute you logged into the launcher or even better wouldn't all servers be down? I can log into my mojang account fine, so calm your tits. The fact it only stops us when we connect through one of the server addresses/proxies shows that it isn't between the home network and mojang but the home network and the play server. Now I have some speculation it has to do with whatever the play server does to converse with the mojang account information servers. Since it's only happening on certain servers. Just to be clear, I'm not blaming SKCraft. Just whatever client or code that communicates with the play servers and mojang's account verification specifically. Any bit of simple diagnostic reasoning would tell you that that is where the problem occurs. Although I've only ran vanilla servers before so afaik it could be any reason. My point is you can't assume it is ONLY MOJANG.
Kura, If you can login no problem then there is no issue with the mojang login server I agree. The "bad login" message comes from an error in the server trying to authenticate the user with the mojang login servers. It is Mojang's fault as this was not previously an issue and is affecting all non 1.7 servers. If there is a problem with server side code then that is still mojang's fault as they were the ones that made that code (As there were no previous issues with Alice or other modded servers it isn't the mod devs. faults). What changed I have no clue. I know that they rewrote the networking systems in 1.7 but alice was working yesterday (and every other non 1.7 server). A temp. solution could be to put your server in offline mode (You need another form of authentication then!!!!)
The server says "bad login" because it's unable to connect to Mojang's server to ask if the information your client supplied it is valid. The specific Mojang server that handles multiplayer authentication gets overloaded every weekend and craps itself. From what I've been told Mojang hosts this server on Amazon's cloud hosting which is far too weak to handle the load the server is under on weekends. For such a popular game they should be hosting it on a dedicated box.
I have taken a look at the AWS and they should have plenty of power to host the servers. The issue is that it is pay for what you need. I.e. You pay for the amount of memory/cpu per hour. They need to upgrade that.
Wouldn't that just result in a huge bill from Amazon instead of the server getting overloaded? Or does Amazon cap it at a certain point and throttle the resources? My tweet to Mojang: https://twitter.com/Drift_91/status/404493323970150400
It's shameful that they haven't solved it after 1-2 days when it first began occurring. I blame Cobalt (their fancy, new, and very successful game).
If you look here: http://aws.amazon.com/ec2/instance-types/ And here(These are the prices, they should be hosting on linux):http://aws.amazon.com/ec2/pricing/ From what I gather this is how AWS works: 1. There are "Nodes", Basically amazing servers with TONS of ram and cpus 2. You choose what kind of specs you would like for one hour(You can obviously set it up for longer periods of time). 3. They create a virtual machine with those specs (This caps and secures your programs from others running on the same node) and put any data that they have from previous machines onto this one. 4. You can upgrade your resources by paying for more. To ditch AWS they have to setup a server (They ARN'T cheap) and make sure it has enough Up/Down stream with the rest of the world.
