Post
Topic
Board Bitcoin Technical Support
Re: Rapid disconnections when connecting to Node
by
pereira4
on 02/11/2019, 02:14:14 UTC
The socket recv error Connection reset by peer (104) message happened to me while having Comodo Firewall enabled. So do this:


1) Close Comodo Firewall
2) Delete "chainstate" folder
3) Delete "peers.dat"

It will take a while as it generates the fresh files. I told you to delete those to generate them from scratch just in case. While it syncs be sure to disable ALL posible firewalls (and this may include going into the actual router setup, not only on your linux file) and watch the log again.

Edit: I see it's a Pi.

Well other things to try, discard it's an I/O error... can you plug another HDD and try a fresh install there?

And are you using an VPS?

And another thing to try.. can you try with 0.17? Some things changed since 0.18 so maybe you have something wrong in your config, for instance:

The rpcallowip option can no longer be used to automatically listen on all network interfaces. Instead, the rpcbind parameter must be used to specify the IP addresses to listen on. Listening for RPC commands over a public network connection is insecure and should be disabled, so a warning is now printed if a user selects such a configuration. If you need to expose RPC in order to use a tool like Docker, ensure you only bind RPC to your localhost, e.g. docker run [...] -p 127.0.0.1:8332:8332 (this is an extra :8332 over the normal Docker port specification).