Ethereum Stack Exchange is a question and answer site for users of Ethereum, the crypto value and blockchain-based consensus network. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got the dreaded "Could not unlock signer account" with the latest geth on a wallet.

It was an offline wallet but I made sure it was unlockable before sending funds to it, by trying it offline, on a private net. I wrote every step that was needed to get back the funds. It was working on 2015-09-18 when I created the wallet and I was able to move funds on a private net (with my own genesys block). So I know the wallet's file is correct. I'm 100% sure my password is correct. This is the kind of thing I quadruple-checked.

If I now start geth 1.3.5 using geth console, here's what I get:

> personal.unlockAccount(eth.coinbase)
Please unlock account ef..............
Passphrase: 
false

Or this:

> eth.sendTransaction({from:eth.accounts[0],to:"0x........",value:web3.toWei(4000,"ether"),gas:30000})
Unlock account ef.....
Passphrase: 
could not unlock signer account
    at InvalidResponse (<anonymous>:

This is very worrying.

I'm 100% sure my password is correct: it's not only written down, there are also explanation (like "name of my cat, 7 lowercase letters).

And, once again, I did try this wallet on a private network back in august and I could unlock it. The file ain't corrupted: it gives the correct shasum (which I also wrote down).

Basically I'm the paranoid type and I know I quadruple-checked this, I even wrote the date at which I've send ETH on a private chain using this wallet (by mining blocks myself I had ETH in that wallet on my private network).

Are my 40 K USD lost?

share|improve this question

Thankfully I solve it. This is maddening. Nothing short of mad.

The problem is that the JSON info inside the wallet aren't all that make the wallet: the JSON file's name must be following a certain pattern too.

I had named the file:

UTC--2015-09-17T23-25-16.989362153z--0xef........

Instead of:

UTC--2015-09-17T23-25-16.989362153z--ef........

So basically I had "0x" before the hexadecimal address.

And geth silently fails with "false" and "could not unlock signer account".

I really think it should check the "address" field inside the JSON file and, at least, report: "Filename of the wallet file doesn't correspond to wallet" or, maybe even better, not rely on the wallet's filename as metadata?

share|improve this answer
    
Glad you solved it! Suggest that you file your issue/suggestion to github.com/ethereum/go-ethereum/issues The details you provided will help them potentially implement it faster. – eth Mar 5 at 16:59

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.