bitcoin core – Unable to begin BitcoinCore: Unable to begin HTTP server. See debug logs for particulars – Bitcoin Stack Change

0
97
bitcoin core – Unable to begin BitcoinCore: Unable to begin HTTP server. See debug logs for particulars – Bitcoin Stack Change


rpcbind=bitcoind

Within the query you referred to, “bitcoind” is meant to be the network-name of the pc on which bitcoin is working.

# native DNS title (container title utilized in my Docker Compose file)
rpcbind=bitcoind

Open a command immediate window and kind the command hostname to search out out the community title of your pc. If the hostname proven is squonk, double test it by utilizing the command nslookup squonk or equal (e.g. dig squonk or host squonk on Linux)

The clue in your log file is that this pair of strains

libevent: getaddrinfo: nodename nor servname offered, or not recognized
Binding RPC on handle bitcoind port 8332 failed.

Should you run bitcoind with the -help choice it tells you

  -rpcbind=<addr>[:port]
       Bind to given handle to pay attention for JSON-RPC connections. Don't expose
       the RPC server to untrusted networks equivalent to the general public web!
       This feature is ignored until -rpcallowip can also be handed. Port is
       non-obligatory and overrides -rpcport. Use [host]:port notation for
       IPv6. This feature might be specified a number of instances (default:
       127.0.0.1 and ::1 i.e., localhost)

You can then change the road within the configurartion file

rpcbind=squonk

Your extract from the log file omits the road earlier than

Binding RPC on handle 127.0.0.1 port 8332 failed.

However these few strains earlier than the above could inform you a couple of extra vital downside that’s the root reason for your difficulties.

LEAVE A REPLY

Please enter your comment!
Please enter your name here