<p>testnet is usually running on port 18333. did you check that port?</p>

CC BY-SA 4.0
2019-02-09T17:14:17.080Z
I thought it was `18332`.
MCCCS
CC BY-SA 4.0
2019-02-10T15:21:08.800Z
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
CC BY-SA 4.0
2019-02-08T21:46:04.007Z
2019-02-10T14:16:37.423Z
2019-02-10T14:16:37.423Z
Rene Pickhardt
<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>

CC BY-SA 4.0
2019-02-11T10:50:14.827Z
This would explain the situation, thank you. Do you have reference on where the two protocols diverge?
Majid Fouladpour
CC BY-SA 4.0
2019-02-11T11:22:23.763Z
There are many small differences, mostly configured via settings in https://github.com/bitcoin/bitcoin/blob/master/src/chainparams.cpp#L182
G. Maxwell
CC BY-SA 4.0
2019-02-10T23:53:51.673Z
2019-02-10T23:53:51.673Z
G. Maxwell
<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>

<bitcoind><full-node><testnet><bitnodes>
Bitnodes for node on testnet
Majid Fouladpour
# Bitnodes for node on testnet

(Asked by: username_0 on 2019-01-18)

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](https://bitnodes.earn.com/). 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?

**Tags:** bitcoind, full-node, testnet, bitnodes


---

## 2 answers

### Answer by username_3 on 2019-02-10. Score: 4 | Accepted answer

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.

> **Comments:**
> **username_0**: This would explain the situation, thank you. Do you have reference on where the two protocols diverge?  
> **username_3**: There are many small differences, mostly configured via settings in https://github.com/bitcoin/bitcoin/blob/master/src/chainparams.cpp#L182  

---

### Answer by username_1 on 2019-02-08. Score: 3

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

> **Comments:**
> **username_2**: I thought it was `18332`.  
> **username_0**: Sorry for the late response. Using port 18333 has no effect unfortunately and I still get "178.128.162.252:18333 is unreachable."  

---

