RPC error connection

0 votes
Hello,
I getting the following error trying to connect RPC-API "No connection could be made because the target machine actively refused it [ip]:6822", i missing something?
asked Oct 19, 2015 by alonsadeh

1 Answer

0 votes
answered Oct 19, 2015 by MultiChain
Hello,
this is my multichain.conf file

rpcuser=user
rpcpassword=password
anyone-can-connect=true
rpcallowip=ip
anyone-can-send=true
rpcport=8332
server=1
rpctimeout=30
testnet=0
addnode=10.0.90.147
addnode=10.0.90.130
maxconnections=50
rpcssl=0
allowreceivebyip=1
rpcallowip=10.0.0.24
am i missing something? still getting the same problem, can u help me please.
You have two values of rpcallowip in there, and the first is probably overriding the second. Also anyone-can-connect is a blockchain parameter, not a runtime parameter of an individual node, so it won't do anything in multichain.conf.
what is the full api url?
currently i getting 403 error.
It's just the node's IP address, with the appropriate port (defined by rpcport)
ok, i still get 403
i saw the rpc port runs nuder tcp6, might be the reason? if so, can i change it to tcp4?
i trying to access rpc from .net tcp4.
Did you try using multichain-cli first, and see if that connects OK?
yes i works on the server(ssh), i have telnet connection from my computer, i have tried it(multichain-cli chain1 getinfo) from .net call, and i getting 403 error.
OK, well I recommend trying to find a .net library that works with Bitcoin Core, and then using it with MultiChain. This will ensure all the authentication stuff is done correctly. For example: https://github.com/GeorgeKimionis/BitcoinLib
ok, i tried to run it with BitcoinLib....unfortunately i getting the same error.
any suggestions?
Try with just these lines in multichain.conf: rpcuser, rpcpassword, rpcallowip
After a series of attempts, the following worked for me. This could be the case of authentication - duplication of multichain.conf in ~/.multichain and its sub-folders results in multiple sets of rpcuser/password combinations. By default, there is a multichain.conf created in ~/.multichain/chain1/, which is the file when overridden with desired username pasword combinations allows connection through
...