Re: BiblePay - New Coin Launch

Quote from: bible_pay on August 03, 2017, 09:01:07 PM

Quote from: bee_irl on August 03, 2017, 08:49:51 PM

I am also not getting connections, even after adding the addnode to my biblepay.conf file:

Code:

server=1
rpcallowip=127.0.0.1
addnode=node.biblepay.org
addnode=97.99.69.33
generate=1

This is the result of telnet:

Code:

telnet node.biblepay.org 40000
Trying 97.99.69.33...
Connected to node.biblepay.org.
Escape character is '^]'.
Connection closed by foreign host.

This all happens instantly after I press enter. The connection is closed immediately.

IPtables and netstat:

Code:

iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Code:

netstat -plunt
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:40000 0.0.0.0:* LISTEN 30275/./biblepay-qt

I tried the command

Code:

addnode node.biblepay.org onetry

and I got this output in debug.log:

Code:

socket recv error Connection reset by peer (104)

Any advice?

Try clicking on Tools | Peers and ensure you have no peers banned, reset wallet, delete banlist.dat, and ensure you are on 1017.
Your config file is good enough - and your telnet appears to be working.

Its working for over 250 people - that leads me to believe it is something on your end that is interfering with the network.

I believe I see whats happening here -

Weve had such a large increase in users but when a new user is just getting started, their peers.dat file is still empty, so you only know about one node.

The node.biblepay.org was exceeding its connection limit, so I just added this to the config (if we have any other external node volunteers out there):
maxconnections=300

Now I see the connections are increasing; please try again.