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

Shows correct balance in wallet, says i have no eth on send screen #628

Closed
HoodPope opened this issue May 13, 2016 · 7 comments
Closed

Shows correct balance in wallet, says i have no eth on send screen #628

HoodPope opened this issue May 13, 2016 · 7 comments

Comments

@HoodPope
Copy link

Node type: geth/eth
OS: osx
Network type: main
Mist version: 0.6.2

Hey guys trying to send Eth out to someone, have more than 3x what i am trying to send but when i try to send it it says "we cant estimate your gas usage properly as you need at least 1 eth in your account"....this message is permanently displayed at the bottom of my send screen

any help would be great, thanks

@hughht5
Copy link

hughht5 commented May 17, 2016

I had this. Either you're not synced up or you have nothing in your etherbase account. I synced and moved 2ETH into the etherbase account and the issue dissapeared. I'm not sure which one solved it.

@HoodPope
Copy link
Author

thanks for reply....i def have eth in account and also have synced many times..

keep getting this message
“couldn’t connect to the node, did it crash in background"

any help would be great, thanks

@hiddentao
Copy link
Contributor

hiddentao commented May 18, 2016

While running the wallet, in a terminal shell type ps aux | grep geth and ensure that geth (i.e. the node) is running.

@luclu
Copy link
Contributor

luclu commented May 18, 2016

@HoodPope also please update to version 0.7.4.

@pharynx
Copy link

pharynx commented May 20, 2016

I have Ether stuck in my contract wallet, with the etherbase wallet as the owner and the same password as the etherbase, and always get 0.00 ETH as a balance when trying to send any amount from the contract wallet. Have lots of ETH in the main wallet ...

@luclu
Copy link
Contributor

luclu commented Jul 18, 2016

@pharynx you will need a small amount of Ether in your coinbase account to invoke the contract wallet transaction.
Also please make sure to update to 0.8.1 as the error messages were broken in earlier version and always fell back to the - often misleading - "wrong password" alert - regardless of the real error (#664).

@luclu luclu closed this as completed Jul 18, 2016
@lock
Copy link

lock bot commented Apr 1, 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 Apr 1, 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

5 participants