Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EXP wallet not connecting to peers #32

Open
bradklynsmith opened this issue Sep 16, 2017 · 2 comments
Open

EXP wallet not connecting to peers #32

bradklynsmith opened this issue Sep 16, 2017 · 2 comments

Comments

@bradklynsmith
Copy link

Have managed to get funds into wallet, but now can't connect to send.

System information

Version: `0.0.0`
OS & Version: windows/linux/osx
Node type: `exp/gexp(default)`

Please check the already existing issues to keep duplicates at a minimum.

Furthermore several work-arounds have been collected in the Mist-Troubleshooting-Guide.

If possible add the following to your report:

  • Screenshots

  • Check the console, of Mist (CTRL/CMD + ALT + i) and take a screenshot

  • Log files

    • go to menu -> accounts -> backup -> application data
    • zip and upload node.log and all other node.log.X files
@JazzMaster
Copy link

not a user problem. blockchain has been stuck at 747,644 for over a week. I was sync fine up until then. we need to keep up w vitalik codebase or we will be left in the dust like FTC. I dont like to say it but its the truth. Im on satellite and have no issues otherwise. close to 1K blocks behind now. telling us to Re-DL the client and stored data is going to lose people. Ive done it twice before but it didnt solve anything. I still got stuck until someone wedged the blockchain moving again.Im sure some of us would like to get paid into our wallets...

@JazzMaster
Copy link

the error I seem to be getting is similar to BAD PEERS detected, which means we are getting hacked somehow or some other chain is trying to wedge into ours. This has happened as a hack before on other coins. similar to a hard fork which wasnt supposed to happen. people get stuck on the old nodes for some reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants