2
2
I have started bitcoin daemon with -regtest flag. The output was
Bitcoin server starting
But, when I run
bitcoin-cli -regtest generate 101
command, it shows
error: couldn't connect to server: unknown (code -1) (make sure server is running and you are connecting to the correct RPC port)
How this happens?
1
Try changing port number in bitcoin.conf. open file
nano ~/.bitcoin/bitcoin.conf
add new line
rpcport=18332;
save the file and restart bitcoind
1
Adding rpcport=18332 temporarily solve your problem. If you want to run mainnet or testnet at the same time when regtest is running, you wont be able to use them, it is because when you assign rpcport=xyz all bitcoin instances will try to interact through same rpcport when daemon is started but at one time only single daemon can access single port number.But in your case all three daemons tries to take rpcport as 18332.
Infact what you can do is, try to get connected to default rpc port for regtest by typing command:
bitcoind -regtest -daemon -rpcport=18443
Mainnet:8332
Testnet:18332
Regtest:18443`
Note:For bitcore v15 rpc port is same for testnet and mainnet where as in v16 rpc port is diffrent for all of them
From their docs, for testnet®test port is same. ie.18832. Is there a different port for regtest?! – Prayag k – 2018-03-23T05:57:45.677
@Prayagk For bitcore v15 rpc port is same for testnet and mainnet where as in v16 rpc port is diffrent for all of them – cryptoKTM – 2018-03-23T07:51:02.203
ok..that's new for me – Prayag k – 2018-03-23T08:21:37.683
2you can see which version you using with command getinfo – cryptoKTM – 2018-03-23T08:37:09.897
This is only the regtest RPC port then? – Willtech – 2018-03-21T11:58:23.503
This will effect all instances of
bitcoindthat are started, regardless of network. – Andrew Chow – 2018-03-21T19:53:51.090@Willtech I think it is – Prayag k – 2018-03-22T06:45:37.970