I have problems making 2-factor auth (Google Authenticator) work for my Blockchain.info wallet.
In Account Settings->Security, I've set Two Factor Authentication to Google Authenticator and scanned the QR code to my Android Google Authenticator app. Also, I checked 'Never Remember Two Factor Login' box. The account is properly set up in the Android app, generating the codes. Login screen now asks for Google Authenticator code in addition to my password.
All is well? Not really, the login comes through with a correct password regardless of the code you put into a Google Auth field. You can put ANY numeric code or NO code at all, and it's still logging you in! Hmmm.. What's the purpose of 2-factor authentication then?
The problem here is the wallet is still cached in your browsers local storage. If the browser already has a local copy of the wallet validating the code with the server is surpufulous. When two factor authentication is enabled the local storage will now be properly cleared, you may need to clear your local storage manually though.
If trying to login with another browser the code would have to validate properly, it is just caching in your own browser which is allowing it to bypass validation.
Is bc.info support active/alive? I opened a case about missing funds almost a month ago and have still not heard anything...
Mon, Feb 25, 2013 at 9:26 PM
"Your request (#2166) has been received and is being reviewed by our support staff."
anyone else experience this?
I have responded to your ticket now.
Should I be concerned if my browser extension is preventing me from logging in, or is it just from moving servers around??? Safari with extension 1.9 on OS X 10.8.3. It let me login earlier today.
Please use one of the packaged extensions instead https://blockchain.info/wallet/browser-extension
Why don't you answer my ticket on zendesk?
I have added a tool to help you debug this issue. The server will now log the response of every callback and you can view the logs by entering the callback url on https://blockchain.info/api/api_receive
That's probably something whose root cause should be understood (and not just overlooked).
Ok I understand this problem better now. The outputs are in fact all unspendable. Before this 0.7/0.8 fork there had never been a very long chain of double spends confirmed in different branches, the code was not checking back far enough to the start of the fork.http://blockchain.info/unspent?active=12U63dueaNH1ANWLe2XWF6uUqNnstyNi6c%7C138bqSSnWz23fNHe6qUHRz8LfieqVmvkYr%7C149PQjaoTXLBkcX5wczcs947zcUbgTUdxp&format=html
-------Insufficient Funds Error
some users are still have issues with Insufficient Funds errors mostly due to the miners fee pushing the value of the transaction high than the amount available. Now a new dialog will popup with the option of automatically adjusting the transaction value: