2

I have used the bitnode's own script to install a full node on an Ubuntu 16.04 Digitalocean droplet. I can verify that my node is up and running by checking the IP with port 8333 on Bitnode's check node. However I need a testnet node so I next added the following line to the config file:

testnet=1

It seems the above line produces the desired effect of turning the node into a testnet node and this can be verified through bitcoin-cli commands. But the node will no longer be accessible from Bitnode. Is Bitnode designed to only work with nodes on the main blockchain or am I missing a necessary step?

Improve this question

2 Answers 2

Reset to default
4
+50

Testnet is a distinct although largely similar protocol. Bitnodes would need to specifically support it for it to work with it. I can't find any evidence that bitnodes has any testnet support or a testnet edition.

Improve this answer
2
3

testnet is usually running on port 18333. did you check that port?

Improve this answer
2
  • 1
    I thought it was 18332.
    – MCCCS
    Feb 9, 2019 at 17:14
  • 1
    Sorry for the late response. Using port 18333 has no effect unfortunately and I still get "178.128.162.252:18333 is unreachable."
    – Majid Fouladpour
    Feb 10, 2019 at 15:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.