Topic: Litecoin Wallet Not Syncing (Read 1715 times)
Eventually it found one connection which led it to find 2 more - right now wallet is synced - so there was nothing wrong it seems as though it just couldn't find any peers to connect to.
It looks like it keeps contacting pelican.heliacal.net to get the peers list - it gets the same peers list and times out on each peer. Any suggestions? Is there a way to have it contact an alternative domain for peers?
Has anybody else experience their wallet not syncing. It was synced two days ago and after I shut it down and restarted it was never able to connect to another peer again. I'm on linux with the latest version of the litecoin client (0.6.3c Beta). I can see in the log files that it downloads peers but then there is a bunch of
....
trying connection 184.82.29.138:9333 lastseen=76.1hrs
connection timeout
trying connection 81.100.64.199:9333 lastseen=123.4hrs
connection timeout
trying connection 78.226.144.120:9333 lastseen=121.9hrs
connection timeout
trying connection 108.36.208.213:9333 lastseen=109.6hrs
connection timeout
trying connection 81.100.64.199:9333 lastseen=123.4hrs
.....
Also the IPs are repeated throughout the logs so searching for '184.82.29.138' for example shows multiple attempts so i'm not sure it's getting new peers lists. Since it was working previously and I haven't changed my router or network setup....i thought maybe the isp suddenly decided to block port 9333 but that seems unlikely. I've left it running for a day but no change.
Any ideas?
....
trying connection 184.82.29.138:9333 lastseen=76.1hrs
connection timeout
trying connection 81.100.64.199:9333 lastseen=123.4hrs
connection timeout
trying connection 78.226.144.120:9333 lastseen=121.9hrs
connection timeout
trying connection 108.36.208.213:9333 lastseen=109.6hrs
connection timeout
trying connection 81.100.64.199:9333 lastseen=123.4hrs
.....
Also the IPs are repeated throughout the logs so searching for '184.82.29.138' for example shows multiple attempts so i'm not sure it's getting new peers lists. Since it was working previously and I haven't changed my router or network setup....i thought maybe the isp suddenly decided to block port 9333 but that seems unlikely. I've left it running for a day but no change.
Any ideas?
Jump to: