BitShares Forum
Main => General Discussion => Topic started by: Mateusz on February 16, 2015, 09:28:37 pm
-
Hello, in August last year I downloaded the Bitshares X software and registered my account. After that I backed up the JSON wallet file on external thumb dive. Recently I wanted to access my account and therefore I downloaded the latest Bitshares software version 0.6.1. After installation I tried to import the wallet but received an error notification: (...) Error: invalid password (20001). Since I wrote the password down in my notebook I was sure that the password is right, but the software keeps rejecting it. What are my options in order to regain access to my account or retrieve or break the password to the backup file?
-
I had a similar issue. Please read this thread:
https://bitsharestalk.org/index.php?topic=14121.msg184243
-
can you install the 'old' softare and import the old backup?
-
Positive! That worked. I've just downloaded version 0.5.3, imported the wallet file, updated to version 0.6.1 and now all is syncing again. You guys need to fix that. By the way the GUI in earlier versions was much neater and easier to use. Thanks!
-
Positive! That worked. I've just downloaded version 0.5.3, imported the wallet file, updated to version 0.6.1 and now all is syncing again. You guys need to fix that. By the way the GUI in earlier versions was much neater and easier to use. Thanks!
Which menu did you use when you previously got the "invalid password" error? Were you using the "File -> Import Wallet" menu or were you on the "Keys" page and trying to import wallet keys? Does importing the old backup file still fail every time if you try again on 0.6.1 ?
Also, do you know what BTS version the original backup file was created with?
-
I'm having the same problem with 0.6.1
I exported on the 14th january 2015, although I'm not certain which version I was using (very likely the then current version).
-
After installing version 0.6.1 I used the "File -> Import Wallet" menu multiple times trying to import the JSON backup file. Each and every time it failed resulting in Error: invalid password (20001) notification, although the password was correct. The JSON backup file was created using Bitshares X software version 0.4.7.
-
I'm having the same problem with 0.6.1
I exported on the 14th january 2015, although I'm not certain which version I was using (very likely the then current version).
After installing version 0.6.1 I used the "File -> Import Wallet" menu multiple times trying to import the JSON backup file. Each and every time it failed resulting in Error: invalid password (20001) notification, although the password was correct. The JSON backup file was created using Bitshares X software version 0.4.7.
Is there anything potentially weird about your passwords? Any special characters, non-english letters, or spaces ?
Edit: Also can you check that the top part of your backup JSON has a part labeled "master_key_record_type" with exactly this formatting:
[
{
"type": "master_key_record_type",
"data": {
"index": -1,
"encrypted_key": "b7fab8babebf3c18027fa498460c7a64b3d3abe211b1f6440b8b5483a6c0271b8930ecf1945a7467eae73aef1e5c6922536f89f615058293f24f79f48e6742edec249d4518b9336c993393bbc5e3f538",
"checksum": "bae28fc07bbcbc3f629de4879cd1f75fbfc660efb68ded09c191d9d85fe2890eb8905ec11090d5f8e6992fd6b5ec6c695e05a7c76780dd8478072c6831347679"
}
},
{
"type": "property_record_type",
...
Only the "encrypted_key" and "checksum" values should be different from above.
-
Hi,
I did have this problem. I doubt the problem is selection of characters in passwords. I managed to work-around by launching an earlier version of the software - that I have put in my Trash for safe-keeping (and don't want to launch), created on Friday 12th December 2014, 113,364,444 bytes (sorry!).
This version allowed me to import my wallet with my funny password. I then shut down, renamed that app, and installed the current version. Relaunched, re-synced and re-exported my wallet json.
The json I was trying to import, that the new software gave me Error: invalid password (20001). for, does have exactly this formatting.
[
{
"type": "master_key_record_type",
"data": {
"index": -1,
"encrypted_key": "b7fab8babebf3c18027fa498460c7a64b3d3abe211b1f6440b8b5483a6c0271b8930ecf1945a7467eae73aef1e5c6922536f89f615058293f24f79f48e6742edec249d4518b9336c993393bbc5e3f538",
"checksum": "bae28fc07bbcbc3f629de4879cd1f75fbfc660efb68ded09c191d9d85fe2890eb8905ec11090d5f8e6992fd6b5ec6c695e05a7c76780dd8478072c6831347679"
}
},
{
"type": "property_record_type",
...
Without actually describing my password, it would seem certain that there is nothing wrong with our jsons or our passwords, but there is a problem with the recent 0.6.1 import.
-
I'm having the same exact problem on v0.6.1!
-
Anyone with this problem--what operating system are you using?
-
Anyone with this problem--what operating system are you using?
Windows......10 lol
But I reverted to v0.5.3 and it works fine.
-
Same, windows 7.
-
Hey. I have the same problem. I'm trying to restore a wallet backed up in version 0.4.24, but I get the same error. I am dead sure of the password, which does have special characters (nothing outside of what you can type on your standard english keyboard though. no spaces). I checked and the master key record type structure is correct. Using 0.4.24 doesn't work either, it still gives me the same error.... same with 0.5.3
-
Hey. I have the same problem. I'm trying to restore a wallet backed up in version 0.4.24, but I get the same error. I am dead sure of the password, which does have special characters (nothing outside of what you can type on your standard english keyboard though. no spaces). I checked and the master key record type structure is correct. Using 0.4.24 doesn't work either, it still gives me the same error.... same with 0.5.3
If the password won't even work on the old versions, it sounds like either your password really is wrong or there is a separate issue from what everyone else in this thread is experiencing.
In any case, I will think about if we can maybe add an option to force the backup to restore even if it thinks the password is wrong.
-
Hey. I have the same problem. I'm trying to restore a wallet backed up in version 0.4.24, but I get the same error. I am dead sure of the password, which does have special characters (nothing outside of what you can type on your standard english keyboard though. no spaces). I checked and the master key record type structure is correct. Using 0.4.24 doesn't work either, it still gives me the same error.... same with 0.5.3
If the password won't even work on the old versions, it sounds like either your password really is wrong or there is a separate issue from what everyone else in this thread is experiencing.
In any case, I will think about if we can maybe add an option to force the backup to restore even if it thinks the password is wrong.
I'm totally locked out. Tried so many of the versions and all I get is invalid/wrong password. BTW I prefer the 5.0/5.3 splash screens. I don't know for sure but it looks like a malicious individual is the culprit for my password being wrong. Nobody I know personally knew my password, or even what bitshares is, but I found this website video.b1.org up to something. Is there anything I can do?
-
Hey. I have the same problem. I'm trying to restore a wallet backed up in version 0.4.24, but I get the same error. I am dead sure of the password, which does have special characters (nothing outside of what you can type on your standard english keyboard though. no spaces). I checked and the master key record type structure is correct. Using 0.4.24 doesn't work either, it still gives me the same error.... same with 0.5.3
If the password won't even work on the old versions, it sounds like either your password really is wrong or there is a separate issue from what everyone else in this thread is experiencing.
In any case, I will think about if we can maybe add an option to force the backup to restore even if it thinks the password is wrong.
I'm totally locked out. Tried so many of the versions and all I get is invalid/wrong password. BTW I prefer the 5.0/5.3 splash screens. I don't know for sure but it looks like a malicious individual is the culprit for my password being wrong. Nobody I know personally knew my password, or even what bitshares is, but I found this website video.b1.org up to something. Is there anything I can do?
Are you getting this error on backup import or just trying to login? If you are just trying to login, you might be able to try this workaround: https://bitsharestalk.org/index.php?topic=15163.msg198062#msg198062