<p>If your bitcoin daemon isn't running because of a mistake in the configuration file then you won't be able to connect to that daemon.</p>
<p>If the daemon is started automatically, you should be able to check for error messages in the system log.</p>
<p>It should also be possible to start the daemon manually to see any error messages concerning the configuration file.</p>

CC BY-SA 4.0
2020-10-21T09:11:30.723Z
2020-10-21T09:11:30.723Z
RedGrittyBrick
<p>I have a problem with bitcoin node is that when I want to get out of the full node bitcoin server.</p>
<p>I ran this method and it does not work</p>
<pre><code>curl \
  --user myusername \
  --data-binary '{&quot;jsonrpc&quot;:&quot;1.0&quot;, &quot;id&quot;:&quot;curltest&quot;, &quot;method&quot;:&quot;getnewaddress&quot;, &quot;params&quot;:[]]' \
  -H 'content-type : text / plain; ' \
  http://ip server for node:8332/
</code></pre>
<hr />
<p>Answer edited to add:</p>
<p>Error message</p>
<pre><code>curl: (7) Couldn't connect to server
</code></pre>
<p>Config file</p>
<pre><code>erver=1 
aemon=1 
rpcallowip=ip exchange rpc
allowip=127.0.0.1 
rpcport=8332 
rpcuser=xxx 
rpcpassword=xxxxxx
wallet=/home/user/.bitcoin/wallets/coininx/wallet/dat 
walletdir=/home/user/.bitcoin/wallets
</code></pre>

CC BY-SA 4.0
2020-10-20T09:45:19.533Z
This question in my opinion is not clear, because your question show only the terminal command, you run the bitcoin node on your device? what is your bitcoind conf?
vincenzopalazzo
CC BY-SA 4.0
2020-10-20T10:03:53.600Z
What do you mean by *"it does not work"* - were there some error messages - if so what exactly.
RedGrittyBrick
CC BY-SA 4.0
2020-10-20T13:38:24.003Z
This is my config file for bitcoin

erver=1
aemon=1
rpcallowip=ip exchange
rpcallowip=127.0.0.1
rpcport=8332
rpcuser=xxx
rpcpassword=xxxxxx
wallet=/home/user/.bitcoin/wallets/coininx/wallet/dat
walletdir=/home/user/.bitcoin/wallets/
nick burcart
CC BY-SA 4.0
2020-10-20T13:39:39.633Z
and error messages :
curl: (7) Couldn't connect to server
nick burcart
CC BY-SA 4.0
2020-10-20T15:26:06.197Z
Is bitcoind running?
Pieter Wuille
CC BY-SA 4.0
2020-10-21T09:04:34.350Z
Does your config file really have `erver` not `server` and `eamon` not `daemon`?
RedGrittyBrick
CC BY-SA 4.0
2022-07-13T14:32:48.493Z
The first sentence in this question is very confusing. Could you perhaps read that again and fix it?
Murch
<bitcoin-core><bitcoind><client>
bitcoincore connect
nick burcart
# bitcoincore connect

(Asked by: username_0 on 2020-10-20)

I have a problem with bitcoin node is that when I want to get out of the full node bitcoin server.

I ran this method and it does not work

```
curl \
  --user myusername \
  --data-binary '{"jsonrpc":"1.0", "id":"curltest", "method":"getnewaddress", "params":[]]' \
  -H 'content-type : text / plain; ' \
  http://ip server for node:8332/

```

---

Answer edited to add:

Error message

```
curl: (7) Couldn't connect to server

```

Config file

```
erver=1 
aemon=1 
rpcallowip=ip exchange rpc
allowip=127.0.0.1 
rpcport=8332 
rpcuser=xxx 
rpcpassword=xxxxxx
wallet=/home/user/.bitcoin/wallets/coininx/wallet/dat 
walletdir=/home/user/.bitcoin/wallets

```

**Tags:** bitcoin-core, bitcoind, client

> **Comments:**
> **username_1**: This question in my opinion is not clear, because your question show only the terminal command, you run the bitcoin node on your device? what is your bitcoind conf?  
> **username_2**: What do you mean by *"it does not work"* - were there some error messages - if so what exactly.  
> **username_0**: This is my config file for bitcoin  erver=1 aemon=1 rpcallowip=ip exchange rpcallowip=127.0.0.1 rpcport=8332 rpcuser=xxx rpcpassword=xxxxxx wallet=/home/user/.bitcoin/wallets/coininx/wallet/dat walletdir=/home/user/.bitcoin/wallets/  
> **username_0**: and error messages : curl: (7) Couldn't connect to server  
> **username_3**: Is bitcoind running?  
> **username_2**: Does your config file really have `erver` not `server` and `eamon` not `daemon`?  
> **username_4**: The first sentence in this question is very confusing. Could you perhaps read that again and fix it?  

---

## 1 answers

### Answer by username_2 on 2020-10-21. Score: 1

If your bitcoin daemon isn't running because of a mistake in the configuration file then you won't be able to connect to that daemon.

If the daemon is started automatically, you should be able to check for error messages in the system log.

It should also be possible to start the daemon manually to see any error messages concerning the configuration file.


---

