<p>The problem is that you have 0 connections. Your node isn't connecting to other nodes on the network. It is able to connect to the DNS seeders and get node IPs to connect to, but something is preventing it from making the actual connection itself.</p>
<p>Make sure there isn't something preventing your node from making outbound connections to port 8333. This could be a firewall, an antivirus software, or even your Internet service provider.</p>

CC BY-SA 4.0
2020-07-07T14:33:55.940Z
2020-07-07T14:33:55.940Z
Ava Chow
<p>I am using Centos 7 and I installed the newest version of bitcoin core.
I just want to run a full node to download all the blocks.
According to their <a href="https://bitcoin.org/en/full-node#other-linux-daemon" rel="nofollow noreferrer">documentation</a>, the first time we start bitcoin core, it will start automatically to download the blocks.</p>
<p>This is my /.bitcoin/bitcoin.conf file:</p>
<pre><code>datadir=/.../blocks
server=1
txindex=1
rpcport=8332
rpcuser=&lt;something&gt;
rpcpassword=&lt;something&gt;
</code></pre>
<p>After I run <code>bitcoind -daemon</code>, <code>bitcoin-cli getblockcount</code> gives me <code>0</code>.</p>
<p>Is there anything wrong with the ports?</p>
<p>I tried <code>netstat -na | grep 8333</code>, and it gives me this:</p>
<pre><code>tcp        0      0 0.0.0.0:8333            0.0.0.0:*               LISTEN
tcp        0      1 &lt;***&gt;:40706     &lt;***&gt;:8333     SYN_SENT
tcp6       0      0 :::8333                 :::*                    LISTEN
</code></pre>
<p>And <code>netstat -na | grep 8332</code> gives me:</p>
<pre><code>tcp        0      0 127.0.0.1:8332          0.0.0.0:*               LISTEN
tcp6       0      0 ::1:8332                :::*                    LISTEN
</code></pre>
<p>Output of <code>bitcoin-cli getblockchaininfo</code>:</p>
<pre><code>{
  &quot;chain&quot;: &quot;main&quot;,
  &quot;blocks&quot;: 0,
  &quot;headers&quot;: 0,
  &quot;bestblockhash&quot;: &quot;000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f&quot;,
  &quot;difficulty&quot;: 1,
  &quot;mediantime&quot;: 1231006505,
  &quot;verificationprogress&quot;: 1.835803992430469e-09,
  &quot;initialblockdownload&quot;: true,
  &quot;chainwork&quot;: &quot;0000000000000000000000000000000000000000000000000000000100010001&quot;,
  &quot;size_on_disk&quot;: 293,
  &quot;pruned&quot;: false,
  &quot;softforks&quot;: {
    &quot;bip34&quot;: {
      &quot;type&quot;: &quot;buried&quot;,
      &quot;active&quot;: false,
      &quot;height&quot;: 227931
    },
    &quot;bip66&quot;: {
      &quot;type&quot;: &quot;buried&quot;,
      &quot;active&quot;: false,
      &quot;height&quot;: 363725
    },
    &quot;bip65&quot;: {
      &quot;type&quot;: &quot;buried&quot;,
      &quot;active&quot;: false,
      &quot;height&quot;: 388381
    },
    &quot;csv&quot;: {
      &quot;type&quot;: &quot;buried&quot;,
      &quot;active&quot;: false,
      &quot;height&quot;: 419328
    },
    &quot;segwit&quot;: {
      &quot;type&quot;: &quot;buried&quot;,
      &quot;active&quot;: false,
      &quot;height&quot;: 481824
    }
  },
  &quot;warnings&quot;: &quot;&quot;
}
</code></pre>
<p>Result of <code>bitcoin-cli getnetworkinfo</code>:</p>
<pre><code>{
  &quot;version&quot;: 200000,
  &quot;subversion&quot;: &quot;/Satoshi:0.20.0/&quot;,
  &quot;protocolversion&quot;: 70015,
  &quot;localservices&quot;: &quot;0000000000000409&quot;,
  &quot;localservicesnames&quot;: [
    &quot;NETWORK&quot;,
    &quot;WITNESS&quot;,
    &quot;NETWORK_LIMITED&quot;
  ],
  &quot;localrelay&quot;: true,
  &quot;timeoffset&quot;: 0,
  &quot;networkactive&quot;: true,
  &quot;connections&quot;: 0,
  &quot;networks&quot;: [
    {
      &quot;name&quot;: &quot;ipv4&quot;,
      &quot;limited&quot;: false,
      &quot;reachable&quot;: true,
      &quot;proxy&quot;: &quot;&quot;,
      &quot;proxy_randomize_credentials&quot;: false
    },
    {
      &quot;name&quot;: &quot;ipv6&quot;,
      &quot;limited&quot;: false,
      &quot;reachable&quot;: true,
      &quot;proxy&quot;: &quot;&quot;,
      &quot;proxy_randomize_credentials&quot;: false
    },
    {
      &quot;name&quot;: &quot;onion&quot;,
      &quot;limited&quot;: true,
      &quot;reachable&quot;: false,
      &quot;proxy&quot;: &quot;&quot;,
      &quot;proxy_randomize_credentials&quot;: false
    }
  ],
  &quot;relayfee&quot;: 0.00001000,
  &quot;incrementalfee&quot;: 0.00001000,
  &quot;localaddresses&quot;: [
    {
      &quot;address&quot;: &quot;&lt;***&gt;&quot;,
      &quot;port&quot;: 8333,
      &quot;score&quot;: 1
    }
  ],
  &quot;warnings&quot;: &quot;&quot;
}
</code></pre>
<p>I know the question is kind of dumb but please help me figure out what's wrong.</p>
<p>Edit:</p>
<p><code>bitcoind</code> always freezes at this:</p>
<pre><code>Loading addresses from DNS seed seed.bitcoin.sipa.be
2020-07-07T04:16:00Z Loading addresses from DNS seed seed.btc.petertodd.org
2020-07-07T04:16:00Z Loading addresses from DNS seed seed.bitcoin.sprovoost.nl
2020-07-07T04:16:11Z Loading addresses from DNS seed dnsseed.bluematt.me
2020-07-07T04:16:12Z Loading addresses from DNS seed dnsseed.emzy.de
2020-07-07T04:16:12Z Loading addresses from DNS seed dnsseed.bitcoin.dashjr.org
2020-07-07T04:16:23Z Loading addresses from DNS seed seed.bitcoinstats.com
2020-07-07T04:16:23Z Loading addresses from DNS seed seed.bitcoin.jonasschnelli.ch
2020-07-07T04:16:23Z 202 addresses found from DNS seeds
2020-07-07T04:16:23Z dnsseed thread exit
</code></pre>
<p>Is there anything wrong?</p>

CC BY-SA 4.0
2020-07-07T03:51:18.417Z
What is the output for `bitcoin-cli getblockchaininfo`?
Raghav Sood
CC BY-SA 4.0
2020-07-07T03:54:02.747Z
@RaghavSood I just edited it in the question.
Bella
CC BY-SA 4.0
2020-07-07T03:56:34.130Z
can you run bitcoind without the daemon option? do you see any error?
vincenzopalazzo
CC BY-SA 4.0
2020-07-07T04:02:15.380Z
@vincenzopalazzo oh yea there's an error: `Error: Cannot obtain a lock on data directory /home/zmengaa/.bitcoin. Bitcoin Core is probably already running.` I think I also used another machine to run `bitcoind` a few days ago. Maybe that's the problem.
Bella
CC BY-SA 4.0
2020-07-07T04:04:51.523Z
I can delete the whole ./bincoin folder and run bitcoind again, is it gonna help? @vincenzopalazzo
Bella
CC BY-SA 4.0
2020-07-07T04:06:45.443Z
Maybe yes, but is the bitcoin core is already running, the bitcoin core should be print another error. I think that you run bitcoin with two different used (like sudo and you normal used). Before to cancel this directory you can run chmod 777 `/home/zmengaa/.bitcoin`
vincenzopalazzo
CC BY-SA 4.0
2020-07-07T04:20:24.927Z
I edited it in the post, should it be right? Do I just wait for it to continue or is there anything wrong? Thanks! @vincenzopalazzo
Bella
CC BY-SA 4.0
2020-07-07T04:23:58.413Z
Mh I posted the wrong command, I'm sorry, I think that you should use the recursive command, try to run this  run `sudo chmod - R 777`
vincenzopalazzo
CC BY-SA 4.0
2020-07-07T04:51:17.600Z
What is the result of `bitcoin-cli getnetworkinfo`? From the other info you have posted, it looks like you don't have any connections. Make sure there isn't anything preventing you from making outbound connections to port 8333.
Ava Chow
CC BY-SA 4.0
2020-07-07T05:50:49.293Z
I edited it. @AndrewChow But I'm not sure what the output means. Onion is not reachable, so do i need to do any setting about "tor" or something? Thanks!
Bella
CC BY-SA 4.0
2020-07-07T14:32:23.567Z
Unless you specifically want to be using tor connections, there's no need to setup tor stuff.
Ava Chow
<bitcoin-core><bitcoind>
Why is my bitcoin core not downloading any blocks?
Bella
# Why is my bitcoin core not downloading any blocks?

(Asked by: username_0 on 2020-07-07)

I am using Centos 7 and I installed the newest version of bitcoin core.
I just want to run a full node to download all the blocks.
According to their [documentation](https://bitcoin.org/en/full-node#other-linux-daemon), the first time we start bitcoin core, it will start automatically to download the blocks.

This is my /.bitcoin/bitcoin.conf file:

```
datadir=/.../blocks
server=1
txindex=1
rpcport=8332
rpcuser=<something>
rpcpassword=<something>

```

After I run `bitcoind -daemon`, `bitcoin-cli getblockcount` gives me `0`.

Is there anything wrong with the ports?

I tried `netstat -na | grep 8333`, and it gives me this:

```
tcp        0      0 0.0.0.0:8333            0.0.0.0:*               LISTEN
tcp        0      1 <***>:40706     <***>:8333     SYN_SENT
tcp6       0      0 :::8333                 :::*                    LISTEN

```

And `netstat -na | grep 8332` gives me:

```
tcp        0      0 127.0.0.1:8332          0.0.0.0:*               LISTEN
tcp6       0      0 ::1:8332                :::*                    LISTEN

```

Output of `bitcoin-cli getblockchaininfo`:

```
{
  "chain": "main",
  "blocks": 0,
  "headers": 0,
  "bestblockhash": "000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f",
  "difficulty": 1,
  "mediantime": 1231006505,
  "verificationprogress": 1.835803992430469e-09,
  "initialblockdownload": true,
  "chainwork": "0000000000000000000000000000000000000000000000000000000100010001",
  "size_on_disk": 293,
  "pruned": false,
  "softforks": {
    "bip34": {
      "type": "buried",
      "active": false,
      "height": 227931
    },
    "bip66": {
      "type": "buried",
      "active": false,
      "height": 363725
    },
    "bip65": {
      "type": "buried",
      "active": false,
      "height": 388381
    },
    "csv": {
      "type": "buried",
      "active": false,
      "height": 419328
    },
    "segwit": {
      "type": "buried",
      "active": false,
      "height": 481824
    }
  },
  "warnings": ""
}

```

Result of `bitcoin-cli getnetworkinfo`:

```
{
  "version": 200000,
  "subversion": "/Satoshi:0.20.0/",
  "protocolversion": 70015,
  "localservices": "0000000000000409",
  "localservicesnames": [
    "NETWORK",
    "WITNESS",
    "NETWORK_LIMITED"
  ],
  "localrelay": true,
  "timeoffset": 0,
  "networkactive": true,
  "connections": 0,
  "networks": [
    {
      "name": "ipv4",
      "limited": false,
      "reachable": true,
      "proxy": "",
      "proxy_randomize_credentials": false
    },
    {
      "name": "ipv6",
      "limited": false,
      "reachable": true,
      "proxy": "",
      "proxy_randomize_credentials": false
    },
    {
      "name": "onion",
      "limited": true,
      "reachable": false,
      "proxy": "",
      "proxy_randomize_credentials": false
    }
  ],
  "relayfee": 0.00001000,
  "incrementalfee": 0.00001000,
  "localaddresses": [
    {
      "address": "<***>",
      "port": 8333,
      "score": 1
    }
  ],
  "warnings": ""
}

```

I know the question is kind of dumb but please help me figure out what's wrong.

Edit:

`bitcoind` always freezes at this:

```
Loading addresses from DNS seed seed.bitcoin.sipa.be
2020-07-07T04:16:00Z Loading addresses from DNS seed seed.btc.petertodd.org
2020-07-07T04:16:00Z Loading addresses from DNS seed seed.bitcoin.sprovoost.nl
2020-07-07T04:16:11Z Loading addresses from DNS seed dnsseed.bluematt.me
2020-07-07T04:16:12Z Loading addresses from DNS seed dnsseed.emzy.de
2020-07-07T04:16:12Z Loading addresses from DNS seed dnsseed.bitcoin.dashjr.org
2020-07-07T04:16:23Z Loading addresses from DNS seed seed.bitcoinstats.com
2020-07-07T04:16:23Z Loading addresses from DNS seed seed.bitcoin.jonasschnelli.ch
2020-07-07T04:16:23Z 202 addresses found from DNS seeds
2020-07-07T04:16:23Z dnsseed thread exit

```

Is there anything wrong?

**Tags:** bitcoin-core, bitcoind

> **Comments:**
> **username_1**: What is the output for `bitcoin-cli getblockchaininfo`?  
> **username_0**: @username_1 I just edited it in the question.  
> **username_2**: can you run bitcoind without the daemon option? do you see any error?  
> **username_0**: @username_2 oh yea there's an error: `Error: Cannot obtain a lock on data directory /home/zmengaa/.bitcoin. Bitcoin Core is probably already running.` I think I also used another machine to run `bitcoind` a few days ago. Maybe that's the problem.  
> **username_0**: I can delete the whole ./bincoin folder and run bitcoind again, is it gonna help? @username_2  
> **username_2**: Maybe yes, but is the bitcoin core is already running, the bitcoin core should be print another error. I think that you run bitcoin with two different used (like sudo and you normal used). Before to cancel this directory you can run chmod 777 `/home/zmengaa/.bitcoin`  
> **username_0**: I edited it in the post, should it be right? Do I just wait for it to continue or is there anything wrong? Thanks! @username_2  
> **username_2**: Mh I posted the wrong command, I'm sorry, I think that you should use the recursive command, try to run this  run `sudo chmod - R 777`  
> **username_3**: What is the result of `bitcoin-cli getnetworkinfo`? From the other info you have posted, it looks like you don't have any connections. Make sure there isn't anything preventing you from making outbound connections to port 8333.  
> **username_0**: I edited it. @AndrewChow But I'm not sure what the output means. Onion is not reachable, so do i need to do any setting about "tor" or something? Thanks!  
> **username_3**: Unless you specifically want to be using tor connections, there's no need to setup tor stuff.  

---

## 1 answers

### Answer by username_3 on 2020-07-07. Score: 3 | Accepted answer

The problem is that you have 0 connections. Your node isn't connecting to other nodes on the network. It is able to connect to the DNS seeders and get node IPs to connect to, but something is preventing it from making the actual connection itself.

Make sure there isn't something preventing your node from making outbound connections to port 8333. This could be a firewall, an antivirus software, or even your Internet service provider.


---

