Bitcoin Forum

Alternate cryptocurrencies => Altcoin Discussion => Topic started by: supercanada1 on June 14, 2015, 07:17:23 PM



Title: Any way to put altcoin blockchain and wallet on different server?
Post by: supercanada1 on June 14, 2015, 07:17:23 PM
As I know, the wallet must run on the same server of the blockchain so that the blockchain can rpc call to the wallet and get the data, is there any way  that I can put wallet and blockchain on different server?
I tried the conf of the wallet:
server=1
listen=1
daemon=1
rpcuser=username
rpcpassword=password
rpcallowip=*.*.*.*
rpcport=3910
port=3919
addnode=173.44.63.199

and I put php blockchain on another server, but it cannot connect.


Title: Re: Any way to put altcoin blockchain and wallet on different server?
Post by: MicroGuy on June 14, 2015, 11:13:30 PM
As I know, the wallet must run on the same server of the blockchain so that the blockchain can rpc call to the wallet and get the data, is there any way  that I can put wallet and blockchain on different server?
I tried the conf of the wallet:
server=1
listen=1
daemon=1
rpcuser=username
rpcpassword=password
rpcallowip=*.*.*.*
rpcport=3910
port=3919
addnode=173.44.63.199

and I put php blockchain on another server, but it cannot connect.

I don't think wildcards are allowed, try listing the IP address for the client. Also double-check the firewall and make sure it's open for the required ports.


Title: Re: Any way to put altcoin blockchain and wallet on different server?
Post by: mullick on June 15, 2015, 05:26:49 AM
As I know, the wallet must run on the same server of the blockchain so that the blockchain can rpc call to the wallet and get the data, is there any way  that I can put wallet and blockchain on different server?
I tried the conf of the wallet:
server=1
listen=1
daemon=1
rpcuser=username
rpcpassword=password
rpcallowip=*.*.*.*
rpcport=3910
port=3919
addnode=173.44.63.199

and I put php blockchain on another server, but it cannot connect.

I don't think wildcards are allowed, try listing the IP address for the client. Also double-check the firewall and make sure it's open for the required ports.
The asterisk was phased out around the same time the server and cli were split. You need to use cidr notation now. Example: rpcallowip=192.168.0.1/24

Or just a single ip per line

If its based off an older version of bitcoin the asterisks is allowed although highly discouraged. Anyone can connect and attempt to brute force your credentials