user87047: 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?

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

user52021: 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.

87047: <p>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 <a href="https://bitnodes.earn.com/" rel="nofollow noreferrer">check node</a>. However I need a testnet node so I next added the following line to the config file:</p>

<pre><code>testnet=1
</code></pre>

<p>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?</p>
 81940: <p>testnet is usually running on port 18333. did you check that port?</p>
 52021: <p>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.</p>
