<p>Problem is here:</p>
<pre><code>2018-01-19 05:49:22 Binding RPC on address 0.0.0.0 port 7788 failed.
</code></pre>
<p>if you are using rpcallowip, you need to also use rpcbind. By default, the recent BTC versions are limited to 127.0.0.1 so there's no need to use rpcallowip or rpcbind if your BitcoinD and your app are running on same server.</p>
<p>So either you remove rpcallowip from config, or add rpcbind=0.0.0.0 and then restart bitcoind. Also, everytime you restart bitcoind, you need to load the wallet, as default loading of wallet is removed.  So if wallet is not loaded, walletnotify will not work.</p>

CC BY-SA 4.0
2022-04-07T09:08:23.263Z
2022-04-07T09:08:23.263Z
Gladiator9120
<p>Remember to restart bitcoind again after you make any change in bitcoin.conf file. It seems as if you set an rpcpassword in the conf but didnt restart the bitcoind service. You have everything set up properly i guess. </p>

CC BY-SA 4.0
2018-08-08T08:54:16.990Z
2018-08-08T08:54:16.990Z
edge
<p>Here's my bitcoin.conf:</p>

<pre><code>server=1
rpcallowip=127.0.0.1
rpcuser=userrunningbitcoind
rpcpassword=passwordofuserrunningbitcoind
rpcport=7788
walletnotify=/home/userrunningbitcoind/transaction.sh %s
</code></pre>

<p>And here's my transaction.sh, which I've tried running manually already. This works without issue on its own:</p>

<pre><code>#!/bin/sh
curl -d "txid=$1" http://127.0.0.1/api/process-payment
</code></pre>

<p>What else can I try to get walletnotify going?</p>

<p>EDIT:</p>

<p>I've additionally found this in my debug.log:</p>

<pre><code>2018-01-19 05:49:22 Binding RPC on address 0.0.0.0 port 7788 failed.
2018-01-19 05:49:22 No rpcpassword set - using random cookie authentication
2018-01-19 05:49:22 Generated RPC authentication cookie /home/userrunningbitcoind/.bitcoin/.cookie
</code></pre>

CC BY-SA 3.0
2018-01-16T11:22:33.703Z
It should be working, note that it will only trigger for transaction to addresses in your wallet. Have you made a transaction ?  To debug what is happening, you can see .bitcoin/debug.log
dark knight
CC BY-SA 3.0
2018-01-16T11:52:51.490Z
@darkknight I've made transactions to attempt to test it. The debug log is enormous, and seems to be filled with unrelated messages. How would I filter it appropriately?
Fibericon
CC BY-SA 3.0
2018-01-16T12:26:59.027Z
Search for transaction.sh in the log ...it should show up
dark knight
CC BY-SA 3.0
2018-01-16T12:49:19.813Z
grep -i "transaction.sh" debug.log returned no lines. Is it possible that my bitcoin.conf is being ignored?
Fibericon
CC BY-SA 3.0
2018-01-17T12:57:44.813Z
@Fibericon have you tried connecting to the RPC to see if the other settings have taken effect?
meshcollider
CC BY-SA 3.0
2018-01-18T06:16:07.027Z
How would I test this?
Fibericon
CC BY-SA 3.0
2018-01-19T08:22:38.697Z
@MeshCollider It's apparently not binding RPC. Please see my edit.
Fibericon
CC BY-SA 3.0
2018-01-19T10:26:53.873Z
Yeah if it is failing to bind the port its more likely a server issue, try a different port maybe
meshcollider
CC BY-SA 3.0
2018-01-19T10:29:47.363Z
@MeshCollider I tried a few different ports, but no dice.
Fibericon
CC BY-SA 3.0
2018-01-19T12:53:42.907Z
What about the default port? Maybe it's a permission issue
meshcollider
CC BY-SA 3.0
2018-01-19T14:39:21.637Z
@MeshCollider Looks like it defaults to 8332 (when I remove the port line in bitcoin.conf), but it still gives the same error in debug.log
Fibericon
CC BY-SA 4.0
2022-04-06T02:53:24.057Z
Have you tried curling it? `walletnotify=curl /home/userrunningbitcoind/transaction.sh %s`
m1xolyd1an
<bitcoind><wallet-notify>
Walletnotify not working
Fibericon
# Walletnotify not working

(Asked by: username_0 on 2018-01-16)

Here's my bitcoin.conf:

```
server=1
rpcallowip=127.0.0.1
rpcuser=userrunningbitcoind
rpcpassword=passwordofuserrunningbitcoind
rpcport=7788
walletnotify=/home/userrunningbitcoind/transaction.sh %s

```

And here's my transaction.sh, which I've tried running manually already. This works without issue on its own:

```
#!/bin/sh
curl -d "txid=$1" http://127.0.0.1/api/process-payment

```

What else can I try to get walletnotify going?

EDIT:

I've additionally found this in my debug.log:

```
2018-01-19 05:49:22 Binding RPC on address 0.0.0.0 port 7788 failed.
2018-01-19 05:49:22 No rpcpassword set - using random cookie authentication
2018-01-19 05:49:22 Generated RPC authentication cookie /home/userrunningbitcoind/.bitcoin/.cookie

```

**Tags:** bitcoind, wallet-notify

> **Comments:**
> **username_1**: It should be working, note that it will only trigger for transaction to addresses in your wallet. Have you made a transaction ?  To debug what is happening, you can see .bitcoin/debug.log  
> **username_0**: @username_1 I've made transactions to attempt to test it. The debug log is enormous, and seems to be filled with unrelated messages. How would I filter it appropriately?  
> **username_1**: Search for transaction.sh in the log ...it should show up  
> **username_0**: grep -i "transaction.sh" debug.log returned no lines. Is it possible that my bitcoin.conf is being ignored?  
> **username_2**: @username_0 have you tried connecting to the RPC to see if the other settings have taken effect?  
> **username_0**: How would I test this?  
> **username_0**: @MeshCollider It's apparently not binding RPC. Please see my edit.  
> **username_2**: Yeah if it is failing to bind the port its more likely a server issue, try a different port maybe  
> **username_0**: @MeshCollider I tried a few different ports, but no dice.  
> **username_2**: What about the default port? Maybe it's a permission issue  
> **username_0**: @MeshCollider Looks like it defaults to 8332 (when I remove the port line in bitcoin.conf), but it still gives the same error in debug.log  
> **username_3**: Have you tried curling it? `walletnotify=curl /home/userrunningbitcoind/transaction.sh %s`  

---

## 2 answers

### Answer by username_4 on 2022-04-07. Score: 0

Problem is here:

```
2018-01-19 05:49:22 Binding RPC on address 0.0.0.0 port 7788 failed.

```

if you are using rpcallowip, you need to also use rpcbind. By default, the recent BTC versions are limited to 127.0.0.1 so there's no need to use rpcallowip or rpcbind if your BitcoinD and your app are running on same server.

So either you remove rpcallowip from config, or add rpcbind=0.0.0.0 and then restart bitcoind. Also, everytime you restart bitcoind, you need to load the wallet, as default loading of wallet is removed. So if wallet is not loaded, walletnotify will not work.


---

### Answer by username_5 on 2018-08-08. Score: 0

Remember to restart bitcoind again after you make any change in bitcoin.conf file. It seems as if you set an rpcpassword in the conf but didnt restart the bitcoind service. You have everything set up properly i guess.


---

