MultiChain Developer Q&A - Recent questions tagged connection-issues

Unable to open a connection using Lucid Ocean C# Library

Mon, 12 Jul 2021 11:18:42 +0000

Good Day,

I am trying to work on a Hello world web application using LucidOcean.Multichain assembly using C# in Microsoft Visual Studio 2017. I am just trying to make a connection from the server to the server.

Following is my sample code taken from Multichain Developers website

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

MultiChainConnection connection = new MultiChainConnection()

{

Hostname = "xxx.xxx.xx.79",

Port = 7349,

Username = "multichainrpc",

Password = "F4oMLnguUvNYyT6ZUjKQY7r7auGCYzgB8NncZDdZS8QE",

ChainName = "ChainName",

BurnAddress = "1XXXXXXWzyXXXXXXg2XXXXXXcTXXXXXXXqFAPD",

RootNodeAddress = "1WNtXcjb8L9c96JnQbwsQKFPBxgnm1AJK5zd5F"

};

MultiChainClient _Client = new MultiChainClient(connection);

JsonRpcResponse<string> response= _Client.Wallet.GetNewAddress();

When I run the daemon command, resulting information gives me two ports to work with,

First port is 7349 given in the following lines

Other nodes can connect to this node using:
multichaind ChainName@169.254.88.79:7349

If I use 7349 as a port, code throws following exception

The underlying connection was closed: The connection was closed unexpectedly

Second port is 7348 taken from following lines

Listening for API requests on port 7348 (local only - see rpcallowip setting)

If use 7348 as a port, code throws following exception

Unable to connect to the remote server, No connection could be made because the target machine actively refused it 169.254.88.79:7348

Please advise what port I should use and what could be the problem prohibiting the connection?

Can't type the grant command on the first server.

Thu, 22 Apr 2021 03:09:21 +0000

I cant type the "multichain-cli chain1 grant connect" command on the first server. it says listening for API request on port ____. I need help

Connect to the multichain

Mon, 25 Jan 2021 18:11:21 +0000

Hi I have a front end application to manage assets. And have a separate digital ocean machine to handle the multichain. Have tried to connect the front end application from local and which points to digital ocean machine.

Have added the param rpcallowip=192.168.0.7 in the multichain.conf file and restarted the blockchain. But not able to connect from the local machine through the front-end application. but when I added the param as

rpcallowip=0.0.0.0/0 am able to connect. can you please help me to fix this?

Thanks

addnode strategy

Wed, 25 Nov 2020 21:44:16 +0000

Dear MC team,

I have a network with about ten miners (in round-robin style) and some full back nodes.
I have to face the following matters:
- periodically some miner are switched off for maintenance
- the miners must be addressed by host name because their address could change

I cannot use a connect command because I'm not sure which of the miner is up and running at one moment.
Besides even if the connect command is succesful, if the server is switched off then the connected node will be unplugged from the network.

My idea is to add a crontab command (executed every day or on a periodical basis) as the following:
multichain-cli <chain_name> addnode $(dig +short miner_1_hostname):<port> add
multichain-cli <chain_name> addnode $(dig +short miner_2_hostname):<port> add
... and so on

I used 'dig +short hostname' because in MC 2.0.1 using addnode hostname instead of ip address seems to cause a crash.

Could you please comment my solution?
Thanks
Fabio

VM won't connect to multichain on another VM

Thu, 23 Jul 2020 13:56:07 +0000

I followed the get started tutoial and set up my own blockchain on an Azure linux VM, I set up another VM and when I ran the multichaind mychain@IP:Port command it gives this

Error : can not connect to mychain@IP:Port make sure Multichain is unning on port.

my first vm's ip adress is : 20.188.57.6, my second's IP is 20.188.59.71. But the IP they give me to connect with is different from the public one.

Another question is : do all of my nodes have to be in the same network as my root node or I can connect from other networks?

Connection failure between nodes?

Wed, 04 Mar 2020 15:36:13 +0000

What happens if the connection between a node and the network is broken.

However, the node does not notice the disconnection and continues working for 2 day. After 48 hours the node can reconnect to the network. What happens now with the transactions and different lengths of the blockchain?

Couldn't initialize permission database for blockchain X (on Mac OSX)

Sun, 18 Mar 2018 15:10:32 +0000

Had this problem before on Mac OSX with v1, and still persists with v2...maybe I am missing something...

compiled and installed and connected successfully to a chain, running commands etc..then I stopped the chain and deleted the folder for the chain details. Now when I try to connect to the chain again fresh it gives this

multichaind tagcash@tagcash.com:3000 &

MultiChain 2.0 alpha 2 Daemon (latest protocol 20002)
ERROR: Couldn't initialize permission database for blockchain tagcash. Probably multichaind for this blockchain is already running. Exiting...

So I check if multichain is running - nothing there:

ps -x |grep multichain
78928 ttys000    0:00.00 grep multichain

I deleted the .multichain directory in home folder, and then ran the connect command again..it creates a new tagcash folder inside .multichain folder, with these files:

multichain.conf
permissions.db
permissions.log

The permissions.log shows only this:

2018-03-18 23:17:44.445    Initialize: Cannot initialize semaphore

Kinda stuck now. Any ideas?

Connect to bitcoin nodes or network with multichain?

Thu, 07 Sep 2017 13:18:59 +0000

How to connect to bitcoin network with multichain?
I have tried with the following command but I got this error :
username@remoteweb:~$ multichaind bitcoin@seed.bitcoin.sipa.be -daemon

MultiChain 1.0 Daemon (protocol 10008)

MultiChain server starting
ERROR: The protocol version (10002) for blockchain bitcoin has been deprecat
ed and was last supported in MultiChain 1.0 beta 1

Issue when creating streams

Tue, 07 Mar 2017 02:28:02 +0000

Hi everybody.

I'm running through the setup and install guides just to get a feel for Multichain, however I'm running into an issue when trying to create a stream.

Note: I've created my chain on 2 x docker ubuntu servers using the instructions here:

https://medium.com/@kiran.anantha/running-multichain-in-docker-containers-8ec30ea866a0#.ooly9why2

paired with the getting started instructions here:

http://www.multichain.com/getting-started/

Everything is fine up until step 6 of the getting started instructions.

From within the first server I try the command: "multichain-cli create type=stream stream1 false" - but get a return of "error: couldn't connect to server".

I've looked at other issues relating to "error: couldn't connect to server" but not sure I know enough yet to work out the relevance of those issues to mine.

Is there something I'm doing wrong? Is there something in the guide that needs to be updated?