Skip to main content

Timeline for Geth not syncing on testnet

Current License: CC BY-SA 3.0

11 events
when toggle format what by license comment
Sep 15, 2018 at 16:41 answer added user45979 timeline score: 0
Feb 2, 2018 at 1:49 answer added Michael Singer timeline score: 14
Jan 11, 2018 at 13:36 comment added codestruggle Ropsten also does not sync with parity
Jan 11, 2018 at 13:29 comment added codestruggle I am trying to sync via geth as well as parity but to no avail. In geth when I put --debug --verbosity 5, New dial task, Skipping dial candidate, Bumping findnode failure counter, Dial error task="dyndial 6ce05930c72abc63 13.84.180.240:30303" err="dial tcp 13.84.180.240:30303: getsockopt: connection refused" occur repeatedly,
Jan 9, 2018 at 17:54 comment added pabloruiz55 Haven't tried again. I ultimately gave up and went to sync on Rinkeby.
Jan 9, 2018 at 16:38 comment added Ismael Since yesterday I've tried to sync with different internet connections and it always show "dial tcp 52.169.14.227:30303: connectex: No connection could be made because the target machine actively refused it." when launching geth with --verbosity 6
Jan 6, 2018 at 18:38 answer added Roman Frolov timeline score: 2
Jan 6, 2018 at 17:16 comment added pabloruiz55 eth.syncing = false and current block = 0, I'll try increasing the cache.
Jan 6, 2018 at 17:13 comment added Chim Few weeks ago I had similar issues in syncing. Then moved to Parity. Works like a charm.
Jan 6, 2018 at 15:47 comment added Roman Kiselenko What the output of eth.syncing? Also try to setup larger cache, you've setuped cache=128.
Jan 6, 2018 at 14:51 history asked pabloruiz55 CC BY-SA 3.0