[SOLVED] Error Decrypting Wallet using Blockchain.info API

[unclemantis]

I am giving the API a shot and trying to get my balance using the following url

https://blockchain.info/merchant/my-guid/balance?password=my-password

and chrome downloads a file called "balance"

in this file are the words


{"error":"Error Decrypting Wallet"}


What's the deal? My GUID and my PASSWORD are correct. Using My Wallet service works fine, it is the API that I am having issues with.

Thoughts?

[1713507039]

1713507039

[1713507039]

1713507039

[1713507039]

1713507039

[1713507039]

1713507039

[unclemantis]

I just went to http://www.everpassword.com/aes-encryptor and i pasted in the contents of my wallet backup. I entered the password I use on blockchain.info and it is not decrypting! I know this service works, i have used to well in the past.

I just did a test and http://www.everpassword.com/aes-encryptor is working just fine.


I can log into the wallet no problem but I can't use the API nor recover my wallet backup! WTF!?

[Maged]

Try doing an integrity check on the wallet's web interface. It's an option somewhere...

[unclemantis]

Try doing an integrity check on the wallet's web interface. It's an option somewhere...

That was the first thing I tried. Sorry that I did not mention that.

I sent a message to blockchain.info owner last night. it has been 11 hours and no reply yet.

UGH!

[unclemantis]

Tried again just a little while ago. Same error.


{"error":"Error Decrypting Wallet"}


I think I am going to go find another wallet service.

Blockchain.info you can still redeem yourself but right now I need to find a wallet service that works for development. Time is money

[unclemantis]

106 views and no one can help?

[gbl08ma]

I just tried with one of my Blockchain wallets, and it worked fine.

1st troubleshooting idea: are you sure you're putting the lengthy and random identifier on the URL, and not the wallet nickname?

2nd troubleshooting idea: if the password contains spaces or other special characters, they may need to be encoded to conform with the specification for URLs. Some browsers do the conversion automatically, for others you'll need to encode it yourself using a service like http://meyerweb.com/eric/tools/dencoder/

[unclemantis]

I just tried with one of my Blockchain wallets, and it worked fine.

1st troubleshooting idea: are you sure you're putting the lengthy and random identifier on the URL, and not the wallet nickname?

2nd troubleshooting idea: if the password contains spaces or other special characters, they may need to be encoded to conform with the specification for URLs. Some browsers do the conversion automatically, for others you'll need to encode it yourself using a service like http://meyerweb.com/eric/tools/dencoder/

so the blah-blah-blah-blah that i am using with the /wallet url  is not what I am supposed to be using?

Where is this identifier that you are speaking of?

[gbl08ma]

Yes, the identifier you should be using is something like abcaa314-6f67-6705-b384-5d47fbe9d7cc. So that's not the problem.

[unclemantis]

I am using something like this

a1701279-fe40-0352-035d-561dbe74f353

and not this is not the guid i am using

[gbl08ma]

Well, the API worked right for me. I have double encryption enabled (but not two-factor authentication).

I recommend that you double-check for typos (as well as accidental spaces) on the URL you're using to access the API.

It looks like the typo isn't in the guid, because then it wouldn't return "Error Decrypting Wallet" but "GUID Invalid". So the only reason I see for it not to work on your side is that you're passing the wrong password to the API.

[unclemantis]

Well, the API worked right for me. I have double encryption enabled (but not two-factor authentication).

I recommend that you double-check for typos (as well as accidental spaces) on the URL you're using to access the API.

It looks like the typo isn't in the guid, because then it wouldn't return "Error Decrypting Wallet" but "GUID Invalid". So the only reason I see for it not to work on your side is that you're passing the wrong password to the API.

it could be the password. i am using a pretty strong one generated by lastpass

[unclemantis]

{"balance":0}

encoded my password worked!

Thank you!