<p>That is the block count of testnet: <a href="https://live.blockcypher.com/btc-testnet/" rel="nofollow noreferrer">https://live.blockcypher.com/btc-testnet/</a>. The Docker script automatically generates a bitcoin.conf configuration and launches bitcoind. Somehow <code>testnet=1</code> got set in <code>bitcoin.conf</code> or bitcoind was run with -testnet at the command line.</p>

CC BY-SA 4.0
2020-05-23T09:19:40.530Z
Yes, this was indeed the problem, thanks for clarifying! Now downloading the main chain. Going very slow (for days now already), but enough threads on here how to speed that up. :-)
WaZZa
CC BY-SA 4.0
2020-05-23T15:05:13.410Z
For reference, downloading the entire blockchain on my Raspberry Pi over a 80/5mbps cable internet connection took a couple MONTHS. Too many nodes these days are bandwidth limited or pruning, significantly slowing a full download. My point? It takes patience to download it the first time.
Mike
CC BY-SA 4.0
2020-05-24T10:22:18.340Z
Ah, that's good to know. So I guess downloading should take a couple of weeks. Probably the 4 GB memory being the bottleneck. Anyway, thanks for your help, much appreciated!
WaZZa
CC BY-SA 4.0
2020-05-24T19:14:19.280Z
When bootstrapping my node CPU rarely wen above 25% and memory rarely above 75% on my 1.2ghz RPi 3B with 1Gig RAM. Unless I'm missing something, it appears the bottleneck is a lack of other nodes that have the full blockchain and allow you enough bandwidth to download. Just my $.02. Regardless, a long wait is likely
Mike
CC BY-SA 4.0
2020-05-14T20:14:44.883Z
2020-05-14T20:14:44.883Z
Mike
<p>Last week I bought a Synology (918+) and starting running a Bitcoin full node (<a href="https://hub.docker.com/r/kylemanna/bitcoind" rel="nofollow noreferrer">https://hub.docker.com/r/kylemanna/bitcoind</a>).</p>

<p>To check whether the Bitcoin node can be found by the network, I checked on bitnodes.io with my external ip. Unfortunately my Bitcoin node is not reachable. I have forwarded ports 8333 - 8334 on my router. Checking whether port is open on canyouseeme.org, it gives as reason 'Connection refused'.</p>

<p>Another thing which confuses me is the following: if I check the logs, it gives the following (snapshot):</p>

<pre><code>2020-05-14T11:01:13Z UpdateTip: new best=00000000000009b091d2696ccfceae650b7f7a4fd8a9fd1893598647b9a886b4 height=1744386 version=0x20000000 log2_work=72.438235 tx=56041013 date='2020-05-14T11:00:46Z' progress=1.000000 cache=3.7MiB(28196txo) warning='22 of last 100 blocks have unexpected version'                                                    
2020-05-14T11:03:14Z UpdateTip: new best=00000000000006d99735a74bae0c3bba509d56af9f8a01595099533c9bc34e6c height=1744387 version=0x20000000 log2_work=72.438236 tx=56041054 date='2020-05-14T11:03:13Z' progress=1.000000 cache=3.7MiB(28220txo) warning='22 of last 100 blocks have unexpected version' 
</code></pre>

<p>What my understanding is that <code>height</code> is the block height. How can this be <code>height=1744387</code> when we're currently around block height 630335? What am I missing here?</p>

<p>Please note that I am both new to running a NAS and a Bitcoin full node, so any help is appreciated!</p>

CC BY-SA 4.0
2020-05-14T13:31:35.860Z
Are you connected to the testnet?
chytrik
<bitcoind>
Bitcoin full node running on Synology not visible to network
WaZZa
# Bitcoin full node running on Synology not visible to network

(Asked by: username_0 on 2020-05-14)

Last week I bought a Synology (918+) and starting running a Bitcoin full node (<https://hub.docker.com/r/kylemanna/bitcoind>).

To check whether the Bitcoin node can be found by the network, I checked on bitnodes.io with my external ip. Unfortunately my Bitcoin node is not reachable. I have forwarded ports 8333 - 8334 on my router. Checking whether port is open on canyouseeme.org, it gives as reason 'Connection refused'.

Another thing which confuses me is the following: if I check the logs, it gives the following (snapshot):

```
2020-05-14T11:01:13Z UpdateTip: new best=00000000000009b091d2696ccfceae650b7f7a4fd8a9fd1893598647b9a886b4 height=1744386 version=0x20000000 log2_work=72.438235 tx=56041013 date='2020-05-14T11:00:46Z' progress=1.000000 cache=3.7MiB(28196txo) warning='22 of last 100 blocks have unexpected version'                                                    
2020-05-14T11:03:14Z UpdateTip: new best=00000000000006d99735a74bae0c3bba509d56af9f8a01595099533c9bc34e6c height=1744387 version=0x20000000 log2_work=72.438236 tx=56041054 date='2020-05-14T11:03:13Z' progress=1.000000 cache=3.7MiB(28220txo) warning='22 of last 100 blocks have unexpected version' 

```

What my understanding is that `height` is the block height. How can this be `height=1744387` when we're currently around block height 630335? What am I missing here?

Please note that I am both new to running a NAS and a Bitcoin full node, so any help is appreciated!

**Tags:** bitcoind

> **Comments:**
> **username_1**: Are you connected to the testnet?  

---

## 1 answers

### Answer by username_2 on 2020-05-14. Score: 1 | Accepted answer

That is the block count of testnet: <https://live.blockcypher.com/btc-testnet/>. The Docker script automatically generates a bitcoin.conf configuration and launches bitcoind. Somehow `testnet=1` got set in `bitcoin.conf` or bitcoind was run with -testnet at the command line.

> **Comments:**
> **username_0**: Yes, this was indeed the problem, thanks for clarifying! Now downloading the main chain. Going very slow (for days now already), but enough threads on here how to speed that up. :-)  
> **username_2**: For reference, downloading the entire blockchain on my Raspberry Pi over a 80/5mbps cable internet connection took a couple MONTHS. Too many nodes these days are bandwidth limited or pruning, significantly slowing a full download. My point? It takes patience to download it the first time.  
> **username_0**: Ah, that's good to know. So I guess downloading should take a couple of weeks. Probably the 4 GB memory being the bottleneck. Anyway, thanks for your help, much appreciated!  
> **username_2**: When bootstrapping my node CPU rarely wen above 25% and memory rarely above 75% on my 1.2ghz RPi 3B with 1Gig RAM. Unless I'm missing something, it appears the bottleneck is a lack of other nodes that have the full blockchain and allow you enough bandwidth to download. Just my $.02. Regardless, a long wait is likely  

---

