Skip to content
This repository has been archived by the owner on Sep 5, 2020. It is now read-only.

"Wrong Password" Message - using "Correct" password #155

Closed
keepdoing2 opened this issue Feb 10, 2016 · 6 comments
Closed

"Wrong Password" Message - using "Correct" password #155

keepdoing2 opened this issue Feb 10, 2016 · 6 comments

Comments

@keepdoing2
Copy link

OK.... let me start by saying there is a zero % chance I am typing in the wrong password. I wrote down my password in 3 separate places. I have checked all three, and they all match what I am typing in. Also, since setting up the wallet, I have "Sent" money(Eth) several times using the password, so it was working.

Suddenly the password isn't working and I am a bit frieked out.

How can I get my access back to my Eth????

Also..... what started this is I wanted to upgrade to the latest .9 version (I am running .8) and I thought I would throw my Eth on a different outside wallet for the upgrade, since I wasn't sure what would happen, never having done an upgrade. That is when I found out that my password wasn't working.

Question 1: WTF is up with my Password!?!??!
Question 2: Can I retrieve my Eth using the UTC file(?) - or any other method?
Question 3: How does the upgrade work? Do I just download and run the .9 version and it will overwrite things?

I have also tried just entering it with a blank password field. No luck.
I have also restarted the node. I even shut down and rebooted the entire computer. No luck.

Help appreciated.

@frozeman
Copy link
Contributor

Hey.

I had already two other instances where people said passwords were not working and it turned out they either:

  1. forgot it
  2. had a different keyboard layout or caps lock
  3. used a different "standard" password of their own.

I'm not saying you have no point here, but its very likely that you have one of the above problems.

Apart from that you can simply download the 0.3.8 version again and run it, it uses the same data folder, so you can simply switch between these two versions.

Please close, if you find your password..

@keepdoing2
Copy link
Author

I think I can safely rule out options 1. 2. 3. listed above. I was very meticulous setting up the accounts (I should note that I set up 2 accounts, and am having problems with both of them). I wrote down the passwords in multiple places. I've successfully used those written passwords to send funds before. Add to this the fact that BOTH account passwords aren't working tells me it is something else. And I am using laptop with no change in keyboards, and yes I checked caplock.

In an earlier post #131 I saw you made a comment to someone with a similar problem, where you suggest:

"This might be an issue with the connection with the underlying node. So restarting should always fix it. If you really need to recover your funds, you can simply start geth from the command line and follow the tutorials https://ethereum.gitbooks.io/frontier-guide/content/sending_ether.html"

But above you are saying to "download the 0.3.8 version again."

Before I do anything stupid, or irreversibly overwrite something I shouldn't, I want to make sure what I should consider as the best path. I'm dealing with about 400 Eth here, which won't break me but I'd rather not lose it if I don't have to. The only thing I am certain about right now is that I am typing my password correctly. I should add that my node appears to be syncing correctly, but then again, there have been a few times it has locked up upon loading, so I am wondering if data corruption has occurred, best way to deal with that possibility etc.

Thanks for your help.

@keepdoing2
Copy link
Author

OK - here is another interesting thing that may or may not have anything to do with this. Let me go through the process, because I did just notice something wierd in the NOTE field.

  1. I click on Account
  2. I click on SEND
    3)The FROM field is already correctly filled out, so I enter in the correct outgoing address in the SEND field
  3. I enter the amount
  4. In the NOTE field, something wierd happens when I start typing. I can type two (2) characters, and all looks fine, but once I type the 3rd character, it auto-adds an "0x". For example, if I type "AAA", I end up with "0xAAA". Also, off to the right I see a small text filed that is in orange, with an orange Shield Symbol (with x in middle of Shield), that says, "The data seems not to be executabe, that means this transaction will use all the gas you provide."

The "0xAAA" I am typing shows up as a light blue. If I backspace through that message, then the error message at right goes away, however when I start typing again in the NOTE field, the text is now red, AND the "0x" is again automatically inserted at the beginning of anything I type - but the orange Shield and Error message referenced earlier stays gone.

I don't remember seeing this before. Don't know if it will mean anything to you or not.

@keepdoing2
Copy link
Author

OH MY GOD!!!

I am an official idiot. I do not believe it. You were absolutely correct. I had my password written down on 3 separate places, in a file on a flashdrive etc. But the very very 1st place I wrote it down, on a scratch sheet of paper I copied it to all the others from..... well, I copied it wrong off that.

I am SOOOO sorry to have frieked anyone out. I feel so utterly stupid. But huge lesson learned by me, and lesson for any others out there. I am one of the most nitpicky meticulous people in the world, and yet my eyes betrayed me. Lesson learned: Triple check everything you write down/copy for accuracy.

Frozeman - my apologies. (although the wierd NOTE comments above still stand if it means anything to you). Closing case.

@frozeman
Copy link
Contributor

You're now officially the 3. one having the same "solution" :)

The NOTE filed is not for notes, its a data filed, which only accepts HEX (0xABCDEF0123456789)

@frozeman frozeman reopened this Feb 10, 2016
@lock
Copy link

lock bot commented Mar 29, 2018

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked and limited conversation to collaborators Mar 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants