Mt.gox claims page is up

[piuk]

'Too many connections' in /www/p/pl/platform-stable.dns.st/

lol

[1714907376]

1714907376

[1714907376]

1714907376

[1714907376]

1714907376

[1714907376]

1714907376

[Mark Oates]

I have submitted my account recovery with no problems.

<quote>Just lost 20 minutes because I was using my email as a login, instead of the login. You should probably make it clear that you want the LOGIN instead of the EMAIL (half the sites I use use the email as a login).</quote>I thought it was perfectly clear.

[TonyHoyle]

It took me a while to find something complex enough.. 16 characters of random upper/lower case and digits wasn't enough - had to go to 32.

Of course then I fatfingered the password storage app and lost it.  Sigh.  Lucky I've got nothing in the account.

[Justsomeforumuser]

Is there any kind of processing ETA?

There is obviously opportunity cost involved here with funds "in the air" in the MtGox accounts.

Given that 60.000 claims normally should be made, how many people are going to process these?

Since the provided proof will have to be cross-checked manually / by eye I assume, this literally means > 60.000 click-and-compares.

Should I prepare myself for July at the earliest or..?


Also I hope the password entry and storage format is compatible with all 256 possible characters. Would be truly ironic if the new superduper hardened password I chose ends up being stored wrongly, thus locking me out once confirmed..

[Findeton]

It works for me.

[imperi]

Is there any kind of processing ETA?

There is obviously opportunity cost involved here with funds "in the air" in the MtGox accounts.

Given that 60.000 claims normally should be made, how many people are going to process these?

Since the provided proof will have to be cross-checked manually / by eye I assume, this literally means > 60.000 click-and-compares.

Should I prepare myself for July at the earliest or..?

They can automate most of it. The more difficult cases will be done by hand.

[Justsomeforumuser]

They can automate most of it. The more difficult cases will be done by hand.

The way I understand it I have to remain the only claimant for 24h and then it should ideally be automated, whereas once more people contest it, it has to be checked properly?

-

Would that not just mean that whoever already cracked some passwords just has to be really fast again now, as someone who misses the first 30ish hour window might just end up getting time-automated-squeezed out?

[wumpus]

You need to provide more infos, especially if the account has non-zero balances.

As for the "password strength" we compute it based on length and randomness

I accidentally didn't provide more info, because the "submit" button was above "send more proof". Is there any address I can mail additional info to?

[itsybitsy]

I keep getting the "The password for this account is invalid, or this account is not currently under claim process." message.
My password is unique to Mt.Gox and stored in KeepPassX.
My account did not have an email address set and my password was not salted I guess (no "$1$something$" in front of it) looking at the accounts.csv.
Does this mean my account was compromised, the password changed and I am unable to retrieve it now?

[bracek]

mine was sent with no problems,
i went with "other" proof ,
wrote some text with account balances and actions info...

[klaus]

mine was sent with no problems,
i went with "other" proof ,
wrote some text with account balances and actions info...

me the same.

@MagicalTux

-> do we get further email if claim was succesfull ?

This means 'general if we get an email-confirmation' about the claim.

This means NOT how long it takes, its clear that its much work.

[clonedone]

Im having trouble making a request, it keeps telling me the new password is not secure enough, not matter how I try it, and now the page is not even loading. is this only going to be a certain time frame that we can recover our accounts, or will we have more time?

[NO_SLAVE]

The servers are under so much traffic they are essentailly locked.
61,000 users desperate to claim their btc or cash.

I got through, but it took about 15 minutes and several attempts.

also...the only other proof i am willing to provide is the balance. 
If this proof info gets hacked as well,  I dont want the bastards having any knowledge of my other accounts.

[lonestranger]

I filled out the form, hit 'Submit' and then got a server disconnect message after a long wait. Now I wonder if my info is lost in the ether or has made it into their system in which case subsequent attempts won't work or collide with what's already there. Internet blues.

[chuckypalumbo]

After this experience I'm completely done with Mt. Gox, what a damn joke! I still can't go in to confirm my information because it's overloaded. I just want my coins and I want off your exchange, this is insane.

[elggawf]

dont worry. its just a line of ~60.000 User - and YOU are the most important of all.

Huzzah!

[SgtSpike]

I got the email, can't get the confirmation page to come up though.  Too much server overload.

[Keefe]

You guys are lucky. I've been trying for 3 hours to just get the first page to load! My first attempt to load the page a few hours ago did work, but after trying to submit the first form, it went AWOL and never acknowledged the submission, and I got no email. Since then, the page has never loaded despite many attempts and much patience.

[arkados]

Maybe they should just rent Microsoft's update servers for a few hours, they are quite good load-ready 
Stop smashing the F5 button, they may run nginx on a special "DDoS protection service provider", too much is just too much.

[enmaku]

Not only is *.mtgox.com down for me but because their site is sort of half-assed accepting connections and squeaking just enough data through to keep the connection alive it's also brought down MY site which used the MtGox API for statistical analysis.

Of course Drupal doesn't make anything easy... I think I'm going to have to go in through the freaking database and try to edit my PHP blocks there

They really shouldn't have tried to open this to everyone at once. Stupid choice... Really stupid choice...

Edit: Managed to find the problematic block in the database and edit my PHP there - neither easy nor fun. Site is now back up with TradeHill's data and will probably stay that way even if Mt. Gox comes back up some time this week. Sorry MT, I just had to edit PHP with no line breaks in a database because you can't shut down your site when it's obviously broken, you've lost another one.