I'm running a testnet bitcoind node and I have been doing RPC calls on the default port 18332.
I have added this line to ~/.bitcoin/bitcoin.conf:
rpcport=19832
And restarted the bitcoind service. I even restarted the whole machine.
But for some reason it is still accepting RPC calls on port 18332, and trying the same on port 19832 gives "connection refused".
It is definitely using the settings in bitcoin.conf, for example if I change rpcuser
or rpcpassword
(and restart again) I have to use the new user+password in RPC calls, the old ones don't work anymore.
But somehow the port does change.
Am I doing something wrong? Is the setting called something else than rpcport=xxx
?
I know I can probably also define the port manually on the cmd line (using bitcoind -rpcport=xxx
or something) when starting bitcoind, but I want to have everything configured in bitcoin.conf (where it belongs) and have it all started automatically.
P.S. I am connecting on localhost, i.e. on the machine itself. I am also running the ufw firewall, and it is configured to accept connections on both 19832 as well as 18832 (so it's definitely not the firewall that's blocking things here).
(edit) FYI here's the complete bitcoin.conf file:
testnet=1
server=1
daemon=1
txindex=1
rpcuser=XXXXXXXXXXXXXXXXXXXXXXX
rpcpassword=XXXXXXXXXXXXXXXXXXX
rpcallowip=127.0.0.1
rpcport=19832
onlynet=ipv4
zmqpubrawblock=tcp://127.0.0.1:28332
zmqpubrawtx=tcp://127.0.0.1:28333
And here is how I perform RPC commands:
curl http://XXXXXXXXX:XXXXXXXXX@localhost:18332 -H 'content-type:text/plain;' --data-binary '{"jsonrpc":"1.0","id":"curltext","method":"getwalletinfo","params":[]}'
This works OK although note it connects to 18332. If I change localhost:18332
into localhost:19832
it doesn't work anymore (Connection refused).
In case my version is relevant, the result of getwalletinfo
contains "walletversion": 169900
.
bitcoind
itself? Could you also try to run just this conf file ? pastebin.com/mKWmKs00, also try with127.0.0.1
instead oflocalhost
in thecurl
command.sudo systemctl start bitcoind
orsudo systemctl restart bitcoind
. Tried your bitcoin.conf file (and changed the username and password to something new, so I'm sure this .conf file is used) and restarted the service, but unfortunately same result: it allows connection on 18332 (using new user&pasw) but not on 19832. Also tried127.0.0.1
instead oflocalhost
withcurl
but again no difference. Strange huh?systemctl cat bitcoind.service
.systemctl cat bitcoind.service
: pastebin.com/raw/JQS0yuJH Thanks a lot for your attempts to help. Just to be sure, you are also testing with testnet? (not mainnet?)