electroneumd won't sync about electroneum

[santiky]

Same here using debian stretch. There are peers but without any block.

[CryptoSiD]

electroneumd.exe --add-exclusive-node 76.91.14.76:26967 (for linux use ./elctroneumd instead of electroneumd.exe)

Fixed the issue for me, once you added a good peer you can stop and restart the daemon without the --add-exlusive-node, it continue syncing

[santiky]

Thank you, works for me too.

[electroneumRepo]

If it's not syncing, remove the data directory - For you its C:\ProgramData\electroneum\

Then try again.

Can you confirm which operating system this is happening on so I can look into it further.

[CryptoSiD]

I tried removing c:\programdata\electroneum\ but it didn't work.
Also disabled firewall, ran as admin.

The issue is that I was only getting "bad" peers (invalid handshake)

As soon as I added a valid peer manually it started syncing

My OS is Windows 10 Pro Version 1709 (Build 16299.64)

[electroneumRepo]

Thanks for getting back to me.

Can I ask where you got the IP address for the valid peer

It seems a little weird that your daemon failed to connect to any of the seed servers

[CryptoSiD]

I asked on the electroneum.space discord (https://discordapp.com/invite/QBmtnsW) for good peers. (sync_info output)

[electroneumRepo]

Well glad to hear that you got it sorted :)

I'll now close this issue.

[rvrsh3ll]

update check
2017-12-18 12:52:23.888 7fd5831ca700 WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid ElectroneumPulse DNS checkpoint records were received
Error: Problem fetching info -- Error checking for updates

[gasiferox]

I´m stuck 13 days before syncing, what should I do to get fully sync?

[Unyxos]

Hey, are you using the v0.11.0.0-revert v3 version of the software? If not, that could explain the issue, you can find it on https://GitHub.com/electroneum/electroneum/releases Le 1 avr. 2018 à 09:33 +0200, gasiferox <[email protected]>, a écrit :

…

I´m stuck 13 days before syncing, what should I do to get fully sync? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[bitkevin]

may find answer here: #170