user109501: 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


user13866: 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.

109501: <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>
 13866: <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>
