<p>well im late but i can tell.</p>

<p>it works, use following string</p>

<p>addnode IP:8333 add   but the Port you dont need to show, because everyone uses the same port, because thats the one he set as open on his router. the rpc port must only defined once at startupt. in addnode dont use it, because you could be bound on an IP too via the bind= command, then the server dont know what to do.</p>

CC BY-SA 4.0
2019-04-29T00:13:50.517Z
2019-05-04T07:53:31.487Z
2019-05-04T07:53:31.487Z
TrashPoet
<p>I'm trying to make to nodes on the same computer communicate. 
I set up two bitcoin folder with two bitcoin.conf files.
bitcoin.conf in the second node is the following:</p>

<p><code>rpcuser=bitcoinrpc 
rpcpassword=roiroiroiroiroi
addnode=127.0.0.1:18444
</code></p>

<p>while in the first node is just I've just set the rpcuser and rpcpasswords</p>

<p>Now I start the nodes with the following command</p>

<p>First node
<code>./bitcoin/src/bitcoind -regtest</code></p>

<p>Second node <code>./bitcoin/src/bitcoind  -regtest -rpcport=5444 -port=18888 -datadir=/Users/tommaso/.bitcoin/</code> </p>

<p>But they don't connect to each other.</p>

<p>Only if a run the command <code>./bitcoin/src/bitcoin-cli  -regtest -rpcport=5444 -datadir=/Users/tommaso/.bitcoin/ addnode "127.0.0.1:18444" "onetry"
</code> they finally connect</p>

<p>Why does addnode=127.0.0.1:18444 in bitcoin.conf doesn't work?</p>

CC BY-SA 4.0
2018-10-09T13:18:19.110Z
If you just have to make one connection, you might try using `connect` instead of `addnode`
JBaczuk
CC BY-SA 4.0
2018-10-09T13:59:35.943Z
Anyway addnode should work but just to be safe I have tried as well connect but it doesn't work neither.
Tommaso Bendinelli
CC BY-SA 4.0
2018-10-10T07:12:28.843Z
I have a Mac btw, this might help
Tommaso Bendinelli
CC BY-SA 4.0
2018-10-10T12:01:51.293Z
Try running bitcoind with `-debug` and `-printtoconsole` flags (and not `-daemon`) to see if you notice anything during startup
JBaczuk
CC BY-SA 4.0
2022-03-18T19:42:40.120Z
What is the resolution to this question?
JDOaktown
CC BY-SA 4.0
2022-03-31T05:48:06.357Z
Have you tried in Linux (instead of Mac)?
Cloud Cho
<network><regtest><bitcoin.conf>
addnode in bitcoin.conf doesn't work (Regtest mode)
Tommaso Bendinelli
# addnode in bitcoin.conf doesn't work (Regtest mode)

(Asked by: username_0 on 2018-10-09)

I'm trying to make to nodes on the same computer communicate.
I set up two bitcoin folder with two bitcoin.conf files.
bitcoin.conf in the second node is the following:

`rpcuser=bitcoinrpc
rpcpassword=roiroiroiroiroi
addnode=127.0.0.1:18444`

while in the first node is just I've just set the rpcuser and rpcpasswords

Now I start the nodes with the following command

First node
`./bitcoin/src/bitcoind -regtest`

Second node `./bitcoin/src/bitcoind -regtest -rpcport=5444 -port=18888 -datadir=/Users/username_0/.bitcoin/`

But they don't connect to each other.

Only if a run the command `./bitcoin/src/bitcoin-cli -regtest -rpcport=5444 -datadir=/Users/username_0/.bitcoin/ addnode "127.0.0.1:18444" "onetry"` they finally connect

Why does addnode=127.0.0.1:18444 in bitcoin.conf doesn't work?

**Tags:** network, regtest, bitcoin.conf

> **Comments:**
> **username_1**: If you just have to make one connection, you might try using `connect` instead of `addnode`  
> **username_0**: Anyway addnode should work but just to be safe I have tried as well connect but it doesn't work neither.  
> **username_0**: I have a Mac btw, this might help  
> **username_1**: Try running bitcoind with `-debug` and `-printtoconsole` flags (and not `-daemon`) to see if you notice anything during startup  
> **username_2**: What is the resolution to this question?  
> **username_3**: Have you tried in Linux (instead of Mac)?  

---

## 1 answers

### Answer by username_4 on 2019-04-29. Score: -1

well im late but i can tell.

it works, use following string

addnode IP:8333 add but the Port you dont need to show, because everyone uses the same port, because thats the one he set as open on his router. the rpc port must only defined once at startupt. in addnode dont use it, because you could be bound on an IP too via the bind= command, then the server dont know what to do.


---

