13 years ago
Mon Feb 21 2011, 07:05PM
Try to log into launcher "Error" nothing explained just that...
Try to connect to minecraft.net, 500 error....
Notch's shitty servers? I rest my case....
Managed to log into the client, can't log into the server just get "Failed to connect: Error"
Once again the fact that I have to connect THROUGH Notch's server to connect to this perfectly good and working one pisses me off so much.....
They apparently hired someone today to help fix the issue, surely it must a misconfiguration or lack of load balancing.
13 years ago
Mon Feb 21 2011, 07:33PM
I'm just saying, 10 million euro's at least in mojang's bank account, surely it ain't that f%$in difficult -_-
Am now getting 503 and FileNotFound exceptions...for the JoinServer.jsp link T__________T
EDIT Sorry double posted
All I can say to anyone connected to the server DO NOT DISCONNECT U WONT BE ABLE TO GET BACK ON lol
Well to be fair, its not "Notch's shitty servers" at this point, is "Amazon's shitty cloud thingie" that is the problem right now. They migrated the client logins to Amazon weeks ago, and its been nothing short of a disaster (just follow molstam on twitter, he's up all hours of the night and all weekend long restarting and fixing amazon's screw ups).
So, the _Amazon_ load balancer's just can't keep up with a million-plus login attempts a day, and when they do keep up, authentication instances on various servers keep locking up and failing. Keep in mind, the verification and load balance software is totally Amazon's baby. Notch/Mojang did not code Amazon's cloud structure.
To rectify this, Mojang (at great cost to them no doubt) are moving away from Amazon's service to a new as-of-yet unnamed host. They are probably just trying to have all their ducks in a row before attempting the move this time, seeing as how the last move _to_ Amazon broke things and didn't go smoothly at all. Part of that was on Mojang, sure, but Amazon totally sold them a bill of goods... and not only did not deliver the performance they outlined, but also did not provide proper support to Mojang's staff.
When you get to the level of hosting required by the MC authentication servers, you don't just randomly pick a host from a web ad, and pay by the month. You pick someone well established, and has a proven track record. The exact service requirements are negotiated ahead of time, and quarterly/yearly contracts signed. Its no easy feat to get out of one of those contracts without paying penalties. Mojang will have to prove via logs that the service did not meet the minimum specifications put forth in the contract language on the part of Amazon in order to be let out of the contract.
As for your last post, unfortunately, this is true. If you disconnect from any server, when you try to log into that server again (even without shutting down the client) it tries to authenticate again with Mojang prior to allowing you to log into the server, and it is failing. If you log out of a server, you are stuck till they get it working again. This IS a shitty method, one intended to reduce piracy I'm sure, but its causing actual money-paying customers headaches.
I'm sure Mojang will realize this at some point... the cost of maintaining the authentication servers, the cost of having employees do nothing but code said authentication backend software, and the cost of the support staff to maintain the authentication servers, the cost in man-hours opening and repying to trouble tickets by a support desk.... is that cost really justifying the few extra sales they get? Or is it costing them money/customers in the end?
13 years ago
Tue Feb 22 2011, 12:07AM
it all smells a little too much like how EA et al have gone where you get some crappy DRM that only affects the genuine paying customers like us and not the pirates at all.
i really hope Notch doesn't tighten up the DRM much more, but then again i dont fancy pirate players ruining our hard work here either. tough call
EDITED to lower the strength of a swearword. Sorry boss