Would like to setup a full Monero node using a VPS. However the user guide link on getmonero.org is dead. Anybody with the correct link?
https://getmonero.org/knowledge-base/user-guides/ ---> https://getmonero.org/knowledge-base/user-guides/vps_run_node
Topic: Monero Support - page 20. (Read 82997 times)
actually, try loading the wallet normally, then save the keys file with save_watch_only, then try creating a watch only wallet with what you described above.
windows version?
yes your creating a new password for your new view only wallet.
have you tried this with different address viewkey combinations?
yes your creating a new password for your new view only wallet.
have you tried this with different address viewkey combinations?
Windows 7x64
I'm pretty sure first time i created wallet by mistake in v0.86 and tried to "import" it in v0.9.
But seems problem is somewhere else. I created another new wallet in 0.9 get it address and viewkey
and tried to create view only wallet in 0.9 but get the same error.
Code:
simplewallet --generate-from-view-key d92bc96312dffdf0c7ff75bff5f8a0f1480465f12829527503a30701d497f00e:44dRmx68MxQ9LGnYho7QroEPwdAgkmogZhy51UeuD14qWaq56iY4o2JDqfQATLt2UobFnLSFwDUE5RZPkgfs7Pb8K22wp5b:1234
I'm using v0.9 from your signature (download it a couple weeks ago and not aware if it was updated), but simplewallet actually says v0.8.8.7-7792255 if it matters.
as far as I know those binaries haven't been updated since they were posted. Sucks that it doesn't work - I can't see anything that would make it not work .. i was looking for extra spaces or whatever. Hopefully moneromoo or luigi111 follows this thread, as they would probably have the best insight. Although the best answer is to probably use new binaries, but they don't exist yet, but SOON! oh testnet fork, where art though.
windows version?
yes your creating a new password for your new view only wallet.
have you tried this with different address viewkey combinations?
yes your creating a new password for your new view only wallet.
have you tried this with different address viewkey combinations?
Windows 7x64
I'm pretty sure first time i created wallet by mistake in v0.86 and tried to "import" it in v0.9.
But seems problem is somewhere else. I created another new wallet in 0.9 get it address and viewkey
and tried to create view only wallet in 0.9 but get the same error.
Code:
simplewallet --generate-from-view-key d92bc96312dffdf0c7ff75bff5f8a0f1480465f12829527503a30701d497f00e:44dRmx68MxQ9LGnYho7QroEPwdAgkmogZhy51UeuD14qWaq56iY4o2JDqfQATLt2UobFnLSFwDUE5RZPkgfs7Pb8K22wp5b:1234
I'm using v0.9 from your signature (download it a couple weeks ago and not aware if it was updated), but simplewallet actually says v0.8.8.7-7792255 if it matters.
I'm trying to make view only wallet as descibed here https://getmonero.org/knowledge-base/user-guides/how%20to%20create%20a%20view%20only%20wallet
But get error.
I use v0.9 beta (Windows) and checked my viewkey and address twice.
It is test wallet and empty, so I copy entire command
For some reason simplewallet ask me for password. I thought entire reason behind view only wallet is that I don't need to enter wallet password.
But maybe that not password from the wallet I'm asked for. Anyway after entering password I get
And in simplewallet.log I found
But get error.
I use v0.9 beta (Windows) and checked my viewkey and address twice.
It is test wallet and empty, so I copy entire command
Code:
simplewallet --generate-from-view-key a353b6a4e8670358d91eb50cf92eb10a387559fdc2c1bf5b9782b4e6eaf5ef02:42FDb8mWjhMK1jTDtfiA42eXt7cktA6tAQZn1zmQ2AG5Lx8i7WhBMaEGKrPeuh1cW8gRS3StdyEbwbTvtpPLwMwQEj7pqF7:1234
For some reason simplewallet ask me for password. I thought entire reason behind view only wallet is that I don't need to enter wallet password.
But maybe that not password from the wallet I'm asked for. Anyway after entering password I get
Code:
Error: Failed to parse address
And in simplewallet.log I found
Code:
2015-Oct-22 16:12:28.868532 ERROR C:/msys64/bitmonero-build/src/simplewallet/simplewallet.cpp:1965 Failed to initialize wallet
windows version?
yes your creating a new password for your new view only wallet.
have you tried this with different address viewkey combinations?
I'm trying to make view only wallet as descibed here https://getmonero.org/knowledge-base/user-guides/how%20to%20create%20a%20view%20only%20wallet
But get error.
I use v0.9 beta (Windows) and checked my viewkey and address twice.
It is test wallet and empty, so I copy entire command
For some reason simplewallet ask me for password. I thought entire reason behind view only wallet is that I don't need to enter wallet password.
But maybe that not password from the wallet I'm asked for. Anyway after entering password I get
And in simplewallet.log I found
But get error.
I use v0.9 beta (Windows) and checked my viewkey and address twice.
It is test wallet and empty, so I copy entire command
Code:
simplewallet --generate-from-view-key a353b6a4e8670358d91eb50cf92eb10a387559fdc2c1bf5b9782b4e6eaf5ef02:42FDb8mWjhMK1jTDtfiA42eXt7cktA6tAQZn1zmQ2AG5Lx8i7WhBMaEGKrPeuh1cW8gRS3StdyEbwbTvtpPLwMwQEj7pqF7:1234
For some reason simplewallet ask me for password. I thought entire reason behind view only wallet is that I don't need to enter wallet password.
But maybe that not password from the wallet I'm asked for. Anyway after entering password I get
Code:
Error: Failed to parse address
And in simplewallet.log I found
Code:
2015-Oct-22 16:12:28.868532 ERROR C:/msys64/bitmonero-build/src/simplewallet/simplewallet.cpp:1965 Failed to initialize wallet
anyone know roughly the current block height on test net?
currently downloading the blocks.
currently downloading the blocks.
If you are making long-term cold storage wallets with simplewallet, I suggest saving the exact version of simplewallet you used on a USB stick or some other backup as well.
Then if you run into problems restoring in a future version, just drop your backup simplewallet in knowing that it will definitely restore the wallet and then you can send the XMR to a new wallet.
I had the same problem with the inline/incur bug a few months ago and this way saved me. For some reason when I replaced the words it was giving me an entirely different address, so I had to restore with the old version of simplewallet.
Then if you run into problems restoring in a future version, just drop your backup simplewallet in knowing that it will definitely restore the wallet and then you can send the XMR to a new wallet.
I had the same problem with the inline/incur bug a few months ago and this way saved me. For some reason when I replaced the words it was giving me an entirely different address, so I had to restore with the old version of simplewallet.
Why not add links to getmonero.org for all prior versions of simplewallet?
Yes it is fixed, I should also clarify that the funds wouldn't be lost, just a bit more of a hassle to recover if I didn't have the old simplewallet handy. I would have needed to go to github and compile an older tagged release. When I had the issue it was also from a wallet generated over 1 year ago.
If you are making long-term cold storage wallets with simplewallet, I suggest saving the exact version of simplewallet you used on a USB stick or some other backup as well.
Then if you run into problems restoring in a future version, just drop your backup simplewallet in knowing that it will definitely restore the wallet and then you can send the XMR to a new wallet.
I had the same problem with the inline/incur bug a few months ago and this way saved me. For some reason when I replaced the words it was giving me an entirely different address, so I had to restore with the old version of simplewallet.
Then if you run into problems restoring in a future version, just drop your backup simplewallet in knowing that it will definitely restore the wallet and then you can send the XMR to a new wallet.
I had the same problem with the inline/incur bug a few months ago and this way saved me. For some reason when I replaced the words it was giving me an entirely different address, so I had to restore with the old version of simplewallet.
Has this been fixed to your knowledge in the current release?
I would find it highly frustrating to have XMR lost because I did not save the simplewallet file as opposed to the mnemonics.
Yes, this was already fixed about half a year ago. However, medusa13 had a wallet that was (way) older than that.
See comment of fluffypony on github -> https://github.com/monero-project/bitmonero/issues/235
If you are making long-term cold storage wallets with simplewallet, I suggest saving the exact version of simplewallet you used on a USB stick or some other backup as well.
Then if you run into problems restoring in a future version, just drop your backup simplewallet in knowing that it will definitely restore the wallet and then you can send the XMR to a new wallet.
I had the same problem with the inline/incur bug a few months ago and this way saved me. For some reason when I replaced the words it was giving me an entirely different address, so I had to restore with the old version of simplewallet.
Then if you run into problems restoring in a future version, just drop your backup simplewallet in knowing that it will definitely restore the wallet and then you can send the XMR to a new wallet.
I had the same problem with the inline/incur bug a few months ago and this way saved me. For some reason when I replaced the words it was giving me an entirely different address, so I had to restore with the old version of simplewallet.
Has this been fixed to your knowledge in the current release?
I would find it highly frustrating to have XMR lost because I did not save the simplewallet file as opposed to the mnemonics.
If you are making long-term cold storage wallets with simplewallet, I suggest saving the exact version of simplewallet you used on a USB stick or some other backup as well.
Then if you run into problems restoring in a future version, just drop your backup simplewallet in knowing that it will definitely restore the wallet and then you can send the XMR to a new wallet.
I had the same problem with the inline/incur bug a few months ago and this way saved me. For some reason when I replaced the words it was giving me an entirely different address, so I had to restore with the old version of simplewallet.
Then if you run into problems restoring in a future version, just drop your backup simplewallet in knowing that it will definitely restore the wallet and then you can send the XMR to a new wallet.
I had the same problem with the inline/incur bug a few months ago and this way saved me. For some reason when I replaced the words it was giving me an entirely different address, so I had to restore with the old version of simplewallet.
the problem with my seed has been succesfully solved by fluffypony.
thank you all for your help and support.
lessons learned:
- write bitmonero version number on your seed too, it will help the devs to debug if there should be any problem and a lot of time passed
- keep something to identify your adress, best write the last 4 letters down with your seed on the same paper
- do not use (very) old versions, take the time to upgrade and migrate cold storages too from time to time.
- to have a picture from the seed + address helps, even if it is just to eliminate the doubts about yourself/your hand writing once aou are not able to restore from seed(do i really have the right seed/address?) i had a crappy video but you just need one good frame if you really need it
- if possible, write seed with an offline pc and print or use a writing machine so there is no doubt about every single character, handwriting is not the best way to go for everybody
- use .keys files as your main backup. use seed only as a second parachute
thank you all for your help and support.
lessons learned:
- write bitmonero version number on your seed too, it will help the devs to debug if there should be any problem and a lot of time passed
- keep something to identify your adress, best write the last 4 letters down with your seed on the same paper
- do not use (very) old versions, take the time to upgrade and migrate cold storages too from time to time.
- to have a picture from the seed + address helps, even if it is just to eliminate the doubts about yourself/your hand writing once aou are not able to restore from seed(do i really have the right seed/address?) i had a crappy video but you just need one good frame if you really need it
- if possible, write seed with an offline pc and print or use a writing machine so there is no doubt about every single character, handwriting is not the best way to go for everybody
- use .keys files as your main backup. use seed only as a second parachute
Glad to hear everything worked out well!
One little remark regarding the bolded part: If you are using an offline pc and print the seed etc., make sure you keep the printer offline after that as well. If you bring it online again, it could be an additional vulnerability. Another option is just buying a new, additional printer for printing your seed from the offline pc (printers aren't that expensive, around 50-60$). Drivers etc. could just be added to your boot USB. If anyone wants some help with this feel free to PM me. Currently I am a bit limited on time, but if I've got some more free time I'll probably write a guide about this.
i dont know if it was new, but:
- there was the incline/inline bug
- there was a typoo on my side with "oats" instead of "oars"
- even when both things were changed, the checksum was wrong.
that is at least my humble interpretation of it.
maybe to quote fluffy if i might:
it was the incline/incur bug
but the checksum prevented the correction from going through
I've already added a patch where the checksum can be bypassed for these cases in future
so its all good and everybody is fine and happy
i also checked an other wallet made with the same version win.x64.05082014 and all was fine, so it really depends on the words i guess (and on the version)
--> thats why there was the initiative to use names now for releases instad of numbers (as one of the victims i support this ofc, go for hercules
)
- there was the incline/inline bug
- there was a typoo on my side with "oats" instead of "oars"
- even when both things were changed, the checksum was wrong.
that is at least my humble interpretation of it.
maybe to quote fluffy if i might:
Quote
so its all good and everybody is fine and happy
i also checked an other wallet made with the same version win.x64.05082014 and all was fine, so it really depends on the words i guess (and on the version)
--> thats why there was the initiative to use names now for releases instad of numbers (as one of the victims i support this ofc, go for hercules
) yes i agree. there was definetely a lot of effort, since murphy was stronger than ever on this one
Was there a newly identified bug or just some confusion on your part?
yes i agree. there was definetely a lot of effort, since murphy was stronger than ever on this one
the problem with my seed has been succesfully solved by fluffypony.
thank you all for your help and support.
lessons learned:
- write bitmonero version number on your seed too, it will help the devs to debug if there should be any problem and a lot of time passed
- keep something to identify your adress, best write the last 4 letters down with your seed on the same paper
- do not use (very) old versions, take the time to upgrade and migrate cold storages too from time to time.
- to have a picture from the seed + address helps, even if it is just to eliminate the doubts about yourself/your hand writing once aou are not able to restore from seed(do i really have the right seed/address?) i had a crappy video but you just need one good frame if you really need it
- if possible, write seed with an offline pc and print or use a writing machine so there is no doubt about every single character, handwriting is not the best way to go for everybody
- use .keys files as your main backup. use seed only as a second parachute
thank you all for your help and support.
lessons learned:
- write bitmonero version number on your seed too, it will help the devs to debug if there should be any problem and a lot of time passed
- keep something to identify your adress, best write the last 4 letters down with your seed on the same paper
- do not use (very) old versions, take the time to upgrade and migrate cold storages too from time to time.
- to have a picture from the seed + address helps, even if it is just to eliminate the doubts about yourself/your hand writing once aou are not able to restore from seed(do i really have the right seed/address?) i had a crappy video but you just need one good frame if you really need it
- if possible, write seed with an offline pc and print or use a writing machine so there is no doubt about every single character, handwriting is not the best way to go for everybody
- use .keys files as your main backup. use seed only as a second parachute
Glad to hear that - fluffypony and smooth (among many others) both seem to put an enormous amount of time into supporting the community. I'm very appreciative of having such dedicated individuals.
All good suggestions for cold storage. Obviously just be careful with things like seed photos and whatnot - camera phones often are setup to dump photos to icloud, dropbox and other online services. Ideally an offline laptop w/ camera and/or printer would be used.
the problem with my seed has been succesfully solved by fluffypony.
thank you all for your help and support.
lessons learned:
- write bitmonero version number on your seed too, it will help the devs to debug if there should be any problem and a lot of time passed
- keep something to identify your adress, best write the last 4 letters down with your seed on the same paper
- do not use (very) old versions, take the time to upgrade and migrate cold storages too from time to time.
- to have a picture from the seed + address helps, even if it is just to eliminate the doubts about yourself/your hand writing once aou are not able to restore from seed(do i really have the right seed/address?) i had a crappy video but you just need one good frame if you really need it
- if possible, write seed with an offline pc and print or use a writing machine so there is no doubt about every single character, handwriting is not the best way to go for everybody
- use .keys files as your main backup. use seed only as a second parachute
thank you all for your help and support.
lessons learned:
- write bitmonero version number on your seed too, it will help the devs to debug if there should be any problem and a lot of time passed
- keep something to identify your adress, best write the last 4 letters down with your seed on the same paper
- do not use (very) old versions, take the time to upgrade and migrate cold storages too from time to time.
- to have a picture from the seed + address helps, even if it is just to eliminate the doubts about yourself/your hand writing once aou are not able to restore from seed(do i really have the right seed/address?) i had a crappy video but you just need one good frame if you really need it
- if possible, write seed with an offline pc and print or use a writing machine so there is no doubt about every single character, handwriting is not the best way to go for everybody
- use .keys files as your main backup. use seed only as a second parachute
ok my original wallet has:
-incline
-hoisting
-launching
i dont know if those are the only ones causing problems
bad luck?
to make it short:i can not restore the original wallet seed containing this words.
if i enter the original, it says failed verification.
if i change "incline" for "inline", it says failed verificatio
if i have the original, and change "hoisting" to "noisting" , i can restore but its empty (why is this possible anyway?)
seed has 25 words, one is the checksum right? maybe the above helps..
-incline
-hoisting
-launching
i dont know if those are the only ones causing problems
bad luck?
to make it short:i can not restore the original wallet seed containing this words.
if i enter the original, it says failed verification.
if i change "incline" for "inline", it says failed verificatio
if i have the original, and change "hoisting" to "noisting" , i can restore but its empty (why is this possible anyway?)
seed has 25 words, one is the checksum right? maybe the above helps..
Stay with "hoisting". Change "incline" to "inline". Change "launching" to "ourselves".
This is based on the instructions here: https://github.com/monero-project/bitmonero/issues/235
with this i get failed verification.
i now try noises instead of hoisting, because "noisting" works too. monermoo recommended this on IRC
but i feel this wont change anything..
no, it shouldn't. its just the first 3 letters that matter.
ok my original wallet has:
-incline
-hoisting
-launching
i dont know if those are the only ones causing problems
bad luck?
to make it short:i can not restore the original wallet seed containing this words.
if i enter the original, it says failed verification.
if i change "incline" for "inline", it says failed verificatio
if i have the original, and change "hoisting" to "noisting" , i can restore but its empty (why is this possible anyway?)
seed has 25 words, one is the checksum right? maybe the above helps..
-incline
-hoisting
-launching
i dont know if those are the only ones causing problems
bad luck?
to make it short:i can not restore the original wallet seed containing this words.
if i enter the original, it says failed verification.
if i change "incline" for "inline", it says failed verificatio
if i have the original, and change "hoisting" to "noisting" , i can restore but its empty (why is this possible anyway?)
seed has 25 words, one is the checksum right? maybe the above helps..
Stay with "hoisting". Change "incline" to "inline". Change "launching" to "ourselves".
This is based on the instructions here: https://github.com/monero-project/bitmonero/issues/235
with this i get failed verification.
i now try noises instead of hoisting, because "noisting" works too. monermoo recommended this on IRC
but i feel this wont change anything..
Jump to: