I was wondering why I kept getting the 503 error. Its bothersome to hear that having my account migrated makes it vulnerable. I just changed my password a few days ago, guess it won't hurt to do it again. Glad to know they caught it and are fixing it.
Under the circumstances this should not strictly speaking be necessary. As I understand the situation the exploit does not give them access to anything other than the account name. Password should still be secure, as they are just spoofing the username. It is still good practice to change the password often, but strictly speaking should be unnecessary this time.
Rollback Post to RevisionRollBack
This is my signature. There are many like it, but this one is mine.
My signature is my friend. It is my thoughts. I must master it as I must master minecraft.
I just bought silver status for MineZ and the servers shutting down basically erased it. I know I can't get on the servers but I went to the MineZ site and it said that I haven't bought silver or anything! What the heck that was my good $!
Ahh, man! This happened just when I finally got to port-forward my server! REALLY hope it's fixed soon...
That sort of thing happens to me regularly. Really annoying. Like the hours I wasted trying to sort out why our firewall was blocking traffic from a wireless site-to-site link, only to discover it was not the firewall but the computer I was targetting to test things was broken.... Doh!
any thoughts on how long it would take before we can log in again?
Don't ask that sort of thing with computers. No one knows the answer.
Any answer would be a guess, and probably not a very good one. The only time they'd be able to give a close guess would be after it's fixed.
Glad this happened now though, and not a few hours later. I was able to take my server off the net - would hate to have it vandalised by some jerk.
Is this why I'm getting Internal client error: java.io.IOException: Server returned HTTP response code: 503 for URL: (long ass crap here) atm? I mean it was working a little while ago
Is this why I'm getting Internal client error: java.io.IOException: Server returned HTTP response code: 503 for URL: (long ass crap here) atm? I mean it was working a little while ago
Yes. They disabled logons.
Also, good news apparently. Just spotted on xlson's Twitter that they've got it back online...
This happened when I was on my friends server where I am a admin and a hole heap of people started joining with the same kind of names and used our accounts to ban us and use world edit to crash the server
Yeah, and I even thought Team Avolition were the bad guys and steal all our accounts.
Under the circumstances this should not strictly speaking be necessary. As I understand the situation the exploit does not give them access to anything other than the account name. Password should still be secure, as they are just spoofing the username. It is still good practice to change the password often, but strictly speaking should be unnecessary this time.
My signature is my friend. It is my thoughts. I must master it as I must master minecraft.
But then anyone can log in as you, like in the exploit. So put up a temp world, client base stays, actual world stays safe.
This allows people with 'hacked' or 'non-paid-for' accounts to connect to smp. But when things like this happen, there are solutions....
That sort of thing happens to me regularly. Really annoying. Like the hours I wasted trying to sort out why our firewall was blocking traffic from a wireless site-to-site link, only to discover it was not the firewall but the computer I was targetting to test things was broken.... Doh!
Don't ask that sort of thing with computers. No one knows the answer.
Any answer would be a guess, and probably not a very good one. The only time they'd be able to give a close guess would be after it's fixed.
Glad this happened now though, and not a few hours later. I was able to take my server off the net - would hate to have it vandalised by some jerk.
well i hope it gets fixed
Yes. They disabled logons.
Also, good news apparently. Just spotted on xlson's Twitter that they've got it back online...
Good to hear, glad someone is keeping us updated.
Wha? I can still log on to servers with no errors...