<p>You are trying to call the RPC interface incorrectly.  Your curl -</p>
<pre><code>$ curl --digest -u rpcusername:rpcpassword -X POST \ 
    127.0.0.1:8332/json_rpc \
    -d &quot;{\&quot;jsonrpc\&quot;:\&quot;2.0\&quot;,\&quot;id\&quot;:\&quot;0\&quot;,\&quot;method\&quot;:\&quot;getwalletinfo\&quot;}&quot; \
    -H 'Content-Type:application/json'
</code></pre>
<p>has an incorrect path <code>127.0.0.1:8332/json_rpc</code> you are posting to.  You should create your curl request with the following path - <code>127.0.0.1:8332/</code>.</p>
<p>Working example, printing verbosely with <code>-v</code></p>
<pre><code>$ curl -v --digest -u rpcusername:rpcpassword -X POST \
    127.0.0.1:8332/ \
    -d &quot;{\&quot;jsonrpc\&quot;:\&quot;2.0\&quot;,\&quot;id\&quot;:\&quot;0\&quot;,\&quot;method\&quot;:\&quot;getwalletinfo\&quot;}&quot; \
    -H 'Content-Type:application/json'
</code></pre>

CC BY-SA 4.0
2019-02-15T05:58:47.787Z
No luck Note: Unnecessary use of -X or --request, POST is already inferred.
BKCapri
CC BY-SA 4.0
2019-02-15T15:48:08.730Z
Yeah was just updating the call you posted in the comment section with the approriate URL.
PW Kad
CC BY-SA 4.0
2019-02-14T00:56:30.880Z
2021-08-05T09:57:37.377Z
2021-08-05T09:57:37.377Z
PW Kad
<blockquote>
<p>@GildedHonour Authentication is not optional. Configuring it yourself is optional, but bitcoind never accepts RPC connections without explicitly or implicitly configured username/password.</p>
</blockquote>
<p><a href="https://github.com/bitcoin/bitcoin/issues/10218" rel="nofollow noreferrer">https://github.com/bitcoin/bitcoin/issues/10218</a></p>
<p>Edit your <code>bitcoind.conf</code>, add RPC auth and it'll work.</p>

CC BY-SA 4.0
2022-05-17T08:49:52.193Z
2022-05-17T08:49:52.193Z
Kof
<p>Hi I have made a curl to my server but get no reply . What am a missing</p>
<pre><code> rpcuser=rpcusername
 rpcpassword=rpcpassword
 rpcauth=rpcusername:generatedkey
 daemon=1
 server=1
 rpcport=8332
 rpcbind=0.0.0.0:8332
 rpcallowip=0.0.0.0/0
 listen=1
 rpcconnect=0.0.0.0
 prune=10000
</code></pre>
<p>Whats strange is that it worked on another server. Why am I bot getting any reply. Bitcoin cli commands all work well . I get no reply not even the usual &quot;empty reply&quot;</p>
<hr />
<p>Ive used this</p>
<pre><code>curl --digest -u rpcusername:rpcpassword -X POST \
  127.0.0.1:8332/json_rpc \ 
  -d {\&quot;jsonrpc\&quot;:\&quot;2.0\&quot;,\&quot;id\&quot;:\&quot;0\&quot;,\&quot;method\&quot;:\&quot;getwalletinfo\&quot;}&quot; \
  -H 'Content-Type:application/json' 
</code></pre>
<p>also swapped it with the IP, still no reply.</p>

CC BY-SA 4.0
2019-02-12T09:46:42.010Z
Why are you binding to 0.0.0.0?
Claris
CC BY-SA 4.0
2019-02-12T14:25:35.547Z
Im testing, will that cause an issue ?
BKCapri
CC BY-SA 4.0
2019-02-12T15:35:37.040Z
What is the curl command that you are using?
Ava Chow
CC BY-SA 4.0
2019-02-12T16:04:57.870Z
Ive used this curl --digest -u rpcusername:rpcpassword -X POST http://127.0.0.1:8332/json_rpc -d "{\"jsonrpc\":\"2.0\",\"id\":\"0\",\"method\":\"getwalletinfo\"}" -H 'Content-Type:application/json' also swapped it with the Ip still no reply.
BKCapri
CC BY-SA 4.0
2019-02-14T00:52:04.993Z
Are you sure the chain is fully synced?  Also add `curl -v` the `-v flag is verbose and will help you a bit more when debugging.  Not an empty reply means that your `bitcoind` responded on the RPC port just didn't do anything because it was called incorrectly.
PW Kad
<bitcoind><client><json-rpc><bitcoin-cli>
Bitcoin curl no reply
BKCapri
# Bitcoin curl no reply

(Asked by: username_0 on 2019-02-12)

Hi I have made a curl to my server but get no reply . What am a missing

```
 rpcuser=rpcusername
 rpcpassword=rpcpassword
 rpcauth=rpcusername:generatedkey
 daemon=1
 server=1
 rpcport=8332
 rpcbind=0.0.0.0:8332
 rpcallowip=0.0.0.0/0
 listen=1
 rpcconnect=0.0.0.0
 prune=10000

```

Whats strange is that it worked on another server. Why am I bot getting any reply. Bitcoin cli commands all work well . I get no reply not even the usual "empty reply"

---

Ive used this

```
curl --digest -u rpcusername:rpcpassword -X POST \
  127.0.0.1:8332/json_rpc \ 
  -d {\"jsonrpc\":\"2.0\",\"id\":\"0\",\"method\":\"getwalletinfo\"}" \
  -H 'Content-Type:application/json' 

```

also swapped it with the IP, still no reply.

**Tags:** bitcoind, client, json-rpc, bitcoin-cli

> **Comments:**
> **username_1**: Why are you binding to 0.0.0.0?  
> **username_0**: Im testing, will that cause an issue ?  
> **username_2**: What is the curl command that you are using?  
> **username_0**: Ive used this curl --digest -u rpcusername:rpcpassword -X POST http://127.0.0.1:8332/json_rpc -d "{\"jsonrpc\":\"2.0\",\"id\":\"0\",\"method\":\"getwalletinfo\"}" -H 'Content-Type:application/json' also swapped it with the Ip still no reply.  
> **username_3**: Are you sure the chain is fully synced?  Also add `curl -v` the `-v flag is verbose and will help you a bit more when debugging.  Not an empty reply means that your `bitcoind` responded on the RPC port just didn't do anything because it was called incorrectly.  

---

## 2 answers

### Answer by username_3 on 2019-02-14. Score: 1

You are trying to call the RPC interface incorrectly. Your curl -

```
$ curl --digest -u rpcusername:rpcpassword -X POST \ 
    127.0.0.1:8332/json_rpc \
    -d "{\"jsonrpc\":\"2.0\",\"id\":\"0\",\"method\":\"getwalletinfo\"}" \
    -H 'Content-Type:application/json'

```

has an incorrect path `127.0.0.1:8332/json_rpc` you are posting to. You should create your curl request with the following path - `127.0.0.1:8332/`.

Working example, printing verbosely with `-v`

```
$ curl -v --digest -u rpcusername:rpcpassword -X POST \
    127.0.0.1:8332/ \
    -d "{\"jsonrpc\":\"2.0\",\"id\":\"0\",\"method\":\"getwalletinfo\"}" \
    -H 'Content-Type:application/json'

```

> **Comments:**
> **username_0**: No luck Note: Unnecessary use of -X or --request, POST is already inferred.  
> **username_3**: Yeah was just updating the call you posted in the comment section with the approriate URL.  

---

### Answer by username_4 on 2022-05-17. Score: 0

> @GildedHonour Authentication is not optional. Configuring it yourself is optional, but bitcoind never accepts RPC connections without explicitly or implicitly configured username/password.

<https://github.com/bitcoin/bitcoin/issues/10218>

Edit your `bitcoind.conf`, add RPC auth and it'll work.


---

