<p>Usually this type of conf file works :</p>

<pre><code>server=1
daemon=1
rpcuser=any_username
rpcpassword=any_password
</code></pre>

<p>if not then allow ip 127.0.0.1 in bitcoin.conf </p>

<pre><code>rpcusername=your_usename
rpcpassword=your_password
allowip=127.0.0.1
allowport=8332
</code></pre>

<p>This may help, you may also try allowing ip 0.0.0.0 if both of the above does not works</p>

CC BY-SA 3.0
2014-04-13T18:09:37.013Z
Good advice and the likely answer, it should be noted that allowip need not be set for localhost or 127.0.0.1 (as it is allowed by default)
Mark
CC BY-SA 3.0
2014-01-13T12:12:52.810Z
2014-01-13T12:12:52.810Z
Khan Shahrukh
<p>I am a bitcoin newbie. I am testing solo mining (I know it is not financial feasible in general). I installed bitcoind on Debian and it ran okay as far as I could tell. I've experienced a couple of problems. The size of the bitcoin data directory is still growing when I use:</p>

<pre><code>du -ks .bitcoin/
</code></pre>

<p>I ran</p>

<pre><code>./bitcoind getinfo
</code></pre>

<p>and got information like this:</p>

<pre><code>{
    "version" : 80600,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 225436,
    "timeoffset" : 0,
    "connections" : 9,
    "proxy" : "",
    "difficulty" : 4367876.00084220,
    "testnet" : false,
    "keypoololdest" : 1389424771,
    "keypoolsize" : 103,
    "paytxfee" : 0.00000000,
    "errors" : ""
}
</code></pre>

<p>When I ran</p>

<pre><code>./bitcoind getbalance
</code></pre>

<p>I got 0.000000000</p>

<p>The problem is sometime,</p>

<pre><code>./bitcoind getinfo
</code></pre>

<p>simply freeze and I have to use Ctrl-c to kill it.</p>

<p>Another problem is I cannot connect to bitcoind using</p>

<pre><code>./minerd --url http://127.0.0.1:8332 --userpass username:password
</code></pre>

<p>The result I got is:</p>

<pre><code>[2014-01-12 20:54:03] Binding thread 0 to cpu 0
[2014-01-12 20:54:04] Binding thread 1 to cpu 1
[2014-01-12 20:54:05] 2 miner threads started, using SHA256 'c' algorithm.
[2014-01-12 21:01:36] HTTP request failed: The requested URL returned error: 500
[2014-01-12 21:01:36] json_rpc_call failed, retry after 30 seconds
[2014-01-12 21:02:15] HTTP request failed: The requested URL returned error: 500
[2014-01-12 21:02:15] json_rpc_call failed, retry after 30 seconds
[2014-01-12 21:02:56] HTTP request failed: The requested URL returned error: 500
[2014-01-12 21:02:56] json_rpc_call failed, retry after 30 seconds
[2014-01-12 21:03:35] HTTP request failed: The requested URL returned error: 500
[2014-01-12 21:03:35] json_rpc_call failed, retry after 30 seconds
</code></pre>

<p>Again, I had to use Ctrl-c.</p>

<p>Any information is appreciated.</p>

<bitcoind>
bitcoind getinfo or getbalance freeze
Unplug
# bitcoind getinfo or getbalance freeze

(Asked by: username_0 on 2014-01-13)

I am a bitcoin newbie. I am testing solo mining (I know it is not financial feasible in general). I installed bitcoind on Debian and it ran okay as far as I could tell. I've experienced a couple of problems. The size of the bitcoin data directory is still growing when I use:

```
du -ks .bitcoin/

```

I ran

```
./bitcoind getinfo

```

and got information like this:

```
{
    "version" : 80600,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 225436,
    "timeoffset" : 0,
    "connections" : 9,
    "proxy" : "",
    "difficulty" : 4367876.00084220,
    "testnet" : false,
    "keypoololdest" : 1389424771,
    "keypoolsize" : 103,
    "paytxfee" : 0.00000000,
    "errors" : ""
}

```

When I ran

```
./bitcoind getbalance

```

I got 0.000000000

The problem is sometime,

```
./bitcoind getinfo

```

simply freeze and I have to use Ctrl-c to kill it.

Another problem is I cannot connect to bitcoind using

```
./minerd --url http://127.0.0.1:8332 --userpass username:password

```

The result I got is:

```
[2014-01-12 20:54:03] Binding thread 0 to cpu 0
[2014-01-12 20:54:04] Binding thread 1 to cpu 1
[2014-01-12 20:54:05] 2 miner threads started, using SHA256 'c' algorithm.
[2014-01-12 21:01:36] HTTP request failed: The requested URL returned error: 500
[2014-01-12 21:01:36] json_rpc_call failed, retry after 30 seconds
[2014-01-12 21:02:15] HTTP request failed: The requested URL returned error: 500
[2014-01-12 21:02:15] json_rpc_call failed, retry after 30 seconds
[2014-01-12 21:02:56] HTTP request failed: The requested URL returned error: 500
[2014-01-12 21:02:56] json_rpc_call failed, retry after 30 seconds
[2014-01-12 21:03:35] HTTP request failed: The requested URL returned error: 500
[2014-01-12 21:03:35] json_rpc_call failed, retry after 30 seconds

```

Again, I had to use Ctrl-c.

Any information is appreciated.

**Tags:** bitcoind


---

## 1 answers

### Answer by username_1 on 2014-01-13. Score: 1

Usually this type of conf file works :

```
server=1
daemon=1
rpcuser=any_username
rpcpassword=any_password

```

if not then allow ip 127.0.0.1 in bitcoin.conf

```
rpcusername=your_usename
rpcpassword=your_password
allowip=127.0.0.1
allowport=8332

```

This may help, you may also try allowing ip 0.0.0.0 if both of the above does not works

> **Comments:**
> **username_2**: Good advice and the likely answer, it should be noted that allowip need not be set for localhost or 127.0.0.1 (as it is allowed by default)  

---

