ECONNREFUSED issues on testnet node


#1

I am attempting to run a node on testnet, however, when I start the node my log is filled with failed attempts at connection and is not syncing the chain.

Started the node with:
./bin/hsd --daemon --no-auth

The debug.log is filled with entries like:

[D:2019-07-17T15:08:21Z] (net) Connecting to 172.104.177.177:13038.
[I:2019-07-17T15:08:21Z] (net) Adding loader peer (172.104.177.177:13038).
[D:2019-07-17T15:08:21Z] (net) Refilling peers (1/8).
[D:2019-07-17T15:08:21Z] (net) Connecting to 139.162.183.168:13038.
[D:2019-07-17T15:08:21Z] (net) Connecting to 172.104.214.189:13038.
[D:2019-07-17T15:08:21Z] (net) Connecting to 173.255.209.126:13038.
[D:2019-07-17T15:08:21Z] (net) Error: Socket Error: ECONNREFUSED (139.162.183.168:13038)
[D:2019-07-17T15:08:21Z] (net) Error: Socket Error: ECONNREFUSED (172.104.214.189:13038)
[D:2019-07-17T15:08:21Z] (net) Error: Socket Error: ECONNREFUSED (173.255.209.126:13038)
[D:2019-07-17T15:08:21Z] (net) Error: Socket Error: ECONNREFUSED (172.104.177.177:13038)
[I:2019-07-17T15:08:21Z] (net) Removed loader peer (172.104.177.177:13038).
[D:2019-07-17T15:08:24Z] (net) Connecting to 172.104.214.189:13038.
[I:2019-07-17T15:08:24Z] (net) Adding loader peer (172.104.214.189:13038).
[D:2019-07-17T15:08:24Z] (net) Refilling peers (1/8).
[D:2019-07-17T15:08:24Z] (net) Connecting to 139.162.183.168:13038.
[D:2019-07-17T15:08:24Z] (net) Connecting to 173.255.209.126:13038.
[D:2019-07-17T15:08:24Z] (net) Connecting to 172.104.177.177:13038.
[D:2019-07-17T15:08:24Z] (net) Error: Socket Error: ECONNREFUSED (139.162.183.168:13038)
[D:2019-07-17T15:08:24Z] (net) Error: Socket Error: ECONNREFUSED (172.104.214.189:13038)
[I:2019-07-17T15:08:24Z] (net) Removed loader peer (172.104.214.189:13038).
[D:2019-07-17T15:08:24Z] (net) Error: Socket Error: ECONNREFUSED (173.255.209.126:13038)
[D:2019-07-17T15:08:25Z] (net) Error: Socket Error: ECONNREFUSED (172.104.177.177:13038)

Are there additional commands needed to get started or ports to open etc?

My other questions is does the hs-airdrop utility work on testnet and will we need to use that same utility again once mainnet is running?


#2

copy/paste from reddit post at https://old.reddit.com/r/handshake/comments/cepuul/econnrefused_issues_on_testnet_node/

The network is young and it’s hard to find peers. Additionally, the seed nodes have not been 100% reliable this and last week.

Here is my hosts.json file, my hsd node is synced to testnet and connected to 6 peers: hosts.json

You can replace your own file with this at ~/.hsd/testnet/hosts.json and try restarting. Additionally, you can manually attempt to connect to nodes with the following command (example):

hsd-rpc addnode ak2hy7feae2o5pfzsdzw3cxkxsu3lxypykcl6iphnup4adf2ply6a@138.68.61.31:13038 add

As for hs-airdrop, the utility is designed for mainnet (for example, faucet addresses are all mainnet-formatted) and with some trickery you can derive the corresponding testnet address to create a testnet airdrop. Otherwise (for GitHub SSH/PGP airdrops) the tool should work correctly on testnet, but I haven’t tried it myself yet.


#3

I have used the testnet node hosted by HNScan to bootstrap my history https://hnscan.com/status


#4

@evan thanks for posting that!

And thanks @pinheadmz for posting the addnode command to use.

The hsd GitHub provides a list of supposedly good peers, but all of them were rejecting me. That list might need updating again with some known good peers.