Skip to main content

Connect to an Existing Network on Bare Metal

This guide describes how to connect to an existing network without the use of Docker, Docker-Compose or Kubernetes. Before starting make sure to have node,npm and the latest release of MultiChain available on your machine.

Table of Contents#

Get the repository#

Clone the Github repository of the components onto the designated machines.

Clone the repository:

git clone TruBudget

If you work with an existing checkout, make sure you have the latest changes:

git pull


To connect to an already existing Blockchain network adapt and set the following environment parameters:

export ORGANIZATION="YourOrga";export RPC_PORT=8000;export RPC_USER="multichainrpc";export RPC_PASSWORD="password";export RPC_ALLOW_IP="";export MULTICHAIN_DIR="/root"export EXTERNAL_IP = [external IP here];export P2P_PROD_HOST = [IP of prod instance of seed node];export P2P_PROD_PORT = [MultiChain port of prod instance of seed node];export P2P_TEST_HOST = [IP of test instance of seed node];export P2P_TEST_PORT = [MultiChain port of test instance of seed node];export API_PROD_HOST=[IP of seed API (prod)];export API_PROD_PORT=[port of seed API (prod)];export API_TEST_HOST=[IP of seed API (test)];export API_TEST_PORT=[port of seed API (test)];

Navigate into the blockchain directory and install the node packages defined in the package.json and start the Blockchain with:

cd blockchain/npm installnpm start > startup.log 2>&1 &

Since you are trying to connect to an already existing Blockchain network the node has to be approved by a master node. Before the approval, the startup.log should look similar to:

TrubudgetChain http 8080 7447 TrubudgetChain@>>> Args: -txindex,-port=7447,-autosubscribe=streams,TrubudgetChain@,,>> [MULTICHAIN_DIR]/.multichain/TrubudgetChain/multichain.conf rpcport=8000rpcuser=multichainrpcrpcpassword=passwordrpcallowip=  | Retrieving blockchain parameters from the seed node ...multichaind  | Blockchain successfully initialized.multichaind  | Please ask blockchain admin or user having activate permission to let you connect and/or transact:multichaind  | multichain-cli TrubudgetChain grant [redacted] connectmultichaind  | multichain-cli TrubudgetChain grant [redacted] connect,send,receivemultichaind  |MultiChain 2.0 alpha 2 Daemon (latest protocol 20002)>>> Multichain stopped. Retry in 10 Seconds...

After the node was approved by the master node, the startup.log should update to this:

>> MULTICHAIN_DIR/.multichain/multichain.conf rpcport=8000rpcuser=multichainrpcrpcpassword=passwordrpcallowip=
TrubudgetChain http 8080 7447 TrubudgetChain@>>> Args: -txindex,-port=7447,-autosubscribe=streams,TrubudgetChain@,,>> MULTICHAIN_DIR/.multichain/TrubudgetChain/multichain.conf rpcport=8000rpcuser=multichainrpcrpcpassword=passwordrpcallowip=
multichaind  | Retrieving blockchain parameters from the seed node ...multichaind  | Other nodes can connect to this node using:multichaind TrubudgetChain@ host has multiple IP addresses, so from some networks:multichaind TrubudgetChain@  | Node ready.


If you provisioned a Blockchain of the type "Connect to an existing network" set the following environment parameters:

export ORGANIZATION="YourOrga" (same as for the Blockchain configuration)export RPC_HOST=localhostexport RPC_PORT=8000export ORGANIZATION_VAULT_SECRET=secretexport ROOT_SECRET=root-secretexport RPC_PASSWORD="password"

Once Node.js is installed navigate into the api directory and run the following commands to start the API:

cd ../apinpm installnpm run buildnode dist > api.log 2>&1 &

You can then check the api log via

cat api.log

The api.log should look similar to: (the log includes entries from before and after the node is approved by the master node, that's why you see errors here):

[2018-11-16T15:01:04.019Z] ERROR (TruBudget/5632 on d467a0e3104f): MultiChain connection/permissions not ready yet[2018-11-16T15:01:09.034Z] INFO (TruBudget/5632 on d467a0e3104f): MultiChain connection established[2018-11-16T15:01:09.040Z] ERROR (TruBudget/5632 on d467a0e3104f): failed to create organization stream[2018-11-16T15:01:14.046Z] ERROR (TruBudget/5632 on d467a0e3104f): failed to create organization stream[2018-11-16T15:01:19.054Z] DEBUG (TruBudget/5632 on d467a0e3104f): Created stream org:YourOrga with options {"kind":"organization","name":"org:YourOrga"}[2018-11-16T15:01:19.061Z] TRACE (TruBudget/5632 on d467a0e3104f):    addressFromWallet: "[redacted]"    privkey: "[redacted]"[2018-11-16T15:01:19.066Z] TRACE (TruBudget/5632 on d467a0e3104f): wrote hex string to chain: 282 bytes[2018-11-16T15:01:19.066Z] INFO (TruBudget/5632 on d467a0e3104f): Initializing organization address to local wallet address: [redacted][2018-11-16T15:01:19.067Z] DEBUG (TruBudget/5632 on d467a0e3104f): Publishing wallet address to org:YourOrga/"address"[2018-11-16T15:01:19.069Z] INFO (TruBudget/5632 on d467a0e3104f): organization address: [redacted][2018-11-16T15:01:19.072Z] DEBUG (TruBudget/5632 on d467a0e3104f): Created stream users:YourOrga with options {"kind":"users","name":"users:YourOrga"}[2018-11-16T15:01:19.073Z] INFO (TruBudget/5632 on d467a0e3104f): organization stream present[2018-11-16T15:01:19.076Z] INFO (TruBudget/5632 on d467a0e3104f): node registered in nodes stream


As stated above, the API logs are printed to api.log. For operational purposes it is useful to have an application that manages the process and takes care of log rotation (i.e. breaking the logs into smaller chunks). Luckily, there are several applications that are capable of doing exactly that. One of them is PM2, which we will describe here shortly.

PM2 is an application that handles node processes for you and restarts it after a crash. PM2 can be installed via the following command

npm install -g pm2

It offers a wide range of plugins called "Modules" that can be installed via PM2 directly. One of these modules is called "pm2-logrotate" which can be used to rotate logs (e.g. split them into chunks of certain size or create separate files for each day) and the command to install it is simply

pm2 install pm2-logrotate

You can set up pm2-logrotate (if needed) with the following command

pm2 set pm2-logrotate:<param> <value>


pm2 set pm2-logrotate:max_size 1K (sets max. file size to 1KB)pm2 set pm2-logrotate:compress true (compresses logs when rotated)pm2 set pm2-logrotate:rotateInterval '*/1 * * * *' (force rotate every minute, syntax similar to CRON)
cd apipm2 start dist/index.js

This is just an example. Please refer to the official documentation for more information.

Excel Export#

To enable the export of TruBudget data into Excel files, a separate service needs to be started. To start that service, first change the directory to the excel-export-service folder:

cd ../excel-export-service

Set Environment Variables#

The following environment variables need to be set:

  • Terminal Mac/Git Bash
  • Terminal Windows/Command Shell

Install Node Modules#

Install the node modules via

npm install

Start the Service#

npm start


The first step to deploy the frontend is to adapt and set the environment parameters. If you plan to deploy only one API set PROD and TEST parameters, so that it points to the single API.

cd ../frontend

Navigate into the frontend directory and copy the nginx.conf into the designated nginx directory with:

cp nginx.conf /etc/nginx/conf.d/default.conf

Install the node packages and start the production build:

npm installnpm run build

Once the build was successful copy the build sources into the html directory of nginx:

cp -R build/* /usr/share/nginx/html

The final step is to modify the nginx configuration, so that nginx points to the previous configured API instances.


Caution: It's possible that nginx was automatically started after installation. To check if this is the case run

ps aux | grep nginx

If you see matching entries, simply run

nginx -s stop

to stop all running processes.

To start the frontend, run the following command:


As soon as the step above is done, the frontend should be available on port 80. Make sure that port 80 is exposed and not blocked by any firewall.