Multiple Cloud Node v2 Masternode How TO Guide on VPS IPv4

6 min readJul 6, 2019

This guide refers to an existing masternode installation and shows how to provide one or two additional master nodes. To setup one Masternode you can use this Guide: Cloud Node Masternode Setup
The software I use for this is WinSCP and Putty.

Alternatively, you can also use our Masternode Hosting Service, which saves time and a lot of money!

Website : https://www.cloudenode.xyz/
DISCORD : https://discord.gg/3sKckNz

1. Add IP addresses on VPS

After we have confirmed the query it looks like this

one added address, now we have 2 IPv4-Addresses

If you wish a third one repeat the step

second added address, now we have 3 IPv4-Addresses

Now we restart the VPS, then go to the networking configuration to update it on the VPS.

2. Updating network config

To do this, we log in to the VPS with WinSCP. The folder “/ etc / network /” contains the file “interfaces”. The old configuration we replaced with the new one (see above) and save the file. I typed # on each line

Edited interfaces file:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).#source /etc/network/interfaces.d/*#auto lo
#iface lo inet loopback#auto ens3
#iface ens3 inet dhcp
#iface ens3 inet6 autoauto lo
iface lo inet loopbackauto ens3
iface ens3 inet static
    address 78.141.221.143
    netmask 255.255.254.0
    gateway 78.141.220.1
    dns-nameservers 108.61.10.10
    post-up ip route add 169.254.0.0/16 dev ens3
auto ens3:1
iface ens3:1 inet static
    address 78.141.219.12
    netmask 255.255.255.255auto ens3:2
iface ens3:2 inet static
    address 95.179.178.167
    netmask 255.255.255.255

Start IP’s with this command

ifup ens3            for main IP
ifup ens3:1          if you have a second IP
ifup ens3:2          if you have a third IP

3. Startup files

Now we change the directory and go to the “CLOUDENODE.service” file. The service file is responsible for the automatic start after the server has been shut down or restarted. We must adapt these to the respective MN.

The path is: “/ etc / systemd / system”

Remove # infront of “#PIDFile=/root/.cloudenode/CLOUDENODE.pid”. We add behind -daemon “-pid=/root/.cloudenode/CLOUDENODE.pid”. Remove the “-” from ExecStop=-/usr… and save that file.

Edited file:

[Unit]
Description=CLOUDENODE service
After=network.target[Service]
User=root
Group=rootType=forkingPIDFile=/root/.cloudenode/CLOUDENODE.pidExecStart=/usr/local/bin/cloudenoded -daemon -pid=/root/.cloudenode/CLOUDENODE.pid -conf=/root/.cloudenode/cloudenode.conf -datadir=/root/.cloudenodeExecStop=/usr/local/bin/cloudenode-cli -conf=/root/.cloudenode/cloudenode.conf -datadir=/root/.cloudenode stopRestart=always
PrivateTmp=true
TimeoutStopSec=60s
TimeoutStartSec=10s
StartLimitInterval=120s
StartLimitBurst=5[Install]
WantedBy=multi-user.target

For every MN change cloudenode to cloudenode2 for second node and cloudenode3 for third node.

For second Node:

[Unit]
Description=CLOUDENODE service
After=network.target[Service]
User=root
Group=rootType=forkingPIDFile=/root/.cloudenode2/CLOUDENODE2.pidExecStart=/usr/local/bin/cloudenoded -daemon -pid=/root/.cloudenode2/CLOUDENODE2.pid -conf=/root/.cloudenode2/cloudenode2.conf -datadir=/root/.cloudenode2ExecStop=/usr/local/bin/cloudenode-cli -conf=/root/.cloudenode2/cloudenode2.conf -datadir=/root/.cloudenode2 stopRestart=always
PrivateTmp=true
TimeoutStopSec=60s
TimeoutStartSec=10s
StartLimitInterval=120s
StartLimitBurst=5[Install]
WantedBy=multi-user.target

Save this file as “CLOUDENODE2.service”

For third node:

[Service]
User=root
Group=rootType=forkingPIDFile=/root/.cloudenode3/CLOUDENODE3.pidExecStart=/usr/local/bin/cloudenoded -daemon -pid=/root/.cloudenode3/CLOUDENODE3.pid -conf=/root/.cloudenode3/cloudenode3.conf -datadir=/root/.cloudenode2ExecStop=/usr/local/bin/cloudenode-cli -conf=/root/.cloudenode3/cloudenode3.conf -datadir=/root/.cloudenode3 stopRestart=always
PrivateTmp=true
TimeoutStopSec=60s
TimeoutStartSec=10s
StartLimitInterval=120s
StartLimitBurst=5[Install]
WantedBy=multi-user.target

Save this file as “CLOUDENODE3.service”

For the nodes to be loaded at system startup, manually stopped or started with systemctl-commands, the system must know what to load. To do this, we enter the following commands one after the other and confirm each one with Enter:

systemctl enable /etc/systemd/system/CLOUDENODE.servicesystemctl enable /etc/systemd/system/CLOUDENODE2.servicesystemctl enable /etc/systemd/system/CLOUDENODE3.service

4. Duplicating Data Directories

For the following steps, copying the folders and files we stop the active node:

systemctl stop CLOUDENODE.service

Find the Default Data Directory. Please make sure that WinSCP shows hidden files and directories. If your data directory already contains a complete block chain and or/wallet, we want to move it rather than start from scratch. The first step is finding the default data directory “/.cloudenode”. Here is the path as follows: /root/.cloudenode

These files and folders are needed:

blocks            (folder)
chainstate        (folder)
1X2Coin.conf      (file)
masternode.conf    (file) 
peers.dat         (file)

Create one or twoe new folders in /root/ and named them .cloudenode2 and .cloudenode3. Copy and paste the obove listed files and folders in the new ones. Alternitiv you can use this command for folder 2:

mkdir /root/.cloudenode2 && cd .cloudenode && cp -ar -v blocks/ chainstate/ cloudenode.conf masternode.conf peers.dat /root/.cloudenode2 && cd && cd .cloudenode2 && mv cloudenode.conf cloudenode2.conf && cd

for folder 3:

mkdir /root/.cloudenode3 && cd .cloudenode && cp -ar -v blocks/ chainstate/ cloudenode.conf masternode.conf peers.dat /root/.cloudenode3 && cd && cd .cloudenode3 && mv cloudenode.conf cloudenode3.conf && cd

5. Updating conf files

We have to change and add some configuration on each config file. This are the changes:

For rpcport we used differend ports: 7071 for 1st, 7072 for 2nd and 7073 for 3rd Masternode. When we used the same port on each MN we get an errormessage from system.

Here is th new Config:

rpcuser= your rpcusername
rpcpassword= your rpcpassword 
rpcallowip=127.0.0.1
rpcport=7071 / 7072 / 7073
listen=1
server=1
daemon=1
#port=7070
logintimestamps=1
maxconnections=256
bind= your VPS-IP:7070
masternode=1
masternodeaddr= your VPS-IP:7070
externalip= your VPS-IP
masternodeprivkey= your privatekey
addnode=63.157.105.96
addnode=213.120.125.89
addnode=165.22.74.51
addnode=45.77.131.227
addnode=94.100.212.177
addnode=90.79.111.243
addnode=209.250.232.186
addnode=207.180.223.100
addnode=149.28.178.238
addnode=199.247.5.9

This files are locatet in /.cloudenode, /.cloudenode2 and /.cloudenode3. Edit files with your ip’s from vps, username’s, password’s and private keys.

When everything is done and saved then:

6. Start Masternodes

with this commands you can start and stop MNs

systemctl start CLOUDENODE.service   |1st MN
systemctl start CLOUDENODE.service   |2nd MN
systemctl start CLOUDENODE.service   |3rd MNsystemctl stop CLOUDENODE.service    |1st MN
systemctl stop CLOUDENODE.service    |2nd MN
systemctl stop CLOUDENODE.service    |3rd MN

after starting MNs should begin to sync with blockchain. When th blockchain is synced go to your Wallet, Open Tools -> Debug Console: and activate your MNs with following commands:

startmasternode "alias" "0" "MN1"
startmasternode "alias" "0" "MN2"
startmasternode "alias" "0" "MN3"

Here are some useful commands for each MN:

getinfo — It displays information such as wallet version, block height, balance etc.

cloudenode-cli getinfocloudenode-cli -conf=/root/.cloudenode2/cloudenode2.conf getinfocloudenode-cli -conf=/root/.cloudenode3/cloudenode3.conf getinfo

mnsync status — To check masternode sync status

cloudenode-cli mnsync statuscloudenode-cli -conf=/root/.cloudenode2/cloudenode2.conf mnsync statuscloudenode-cli -conf=/root/.cloudenode3/cloudenode3.conf mnsync status

masternode status — Used to check the masternode status

cloudenode-cli masternode statuscloudenode-cli -conf=/root/.cloudenode2/cloudenode.conf masternode statuscloudenode-cli -conf=/root/.cloudenode3/cloudenode.conf masternode status

Disclaimer:

Please note this is an unofficial release by members of the Cloud Node v2 Community and not the Cloud Node v2 Team itself. The content of these pages and associated media should be used as a guide and not official Cloud Node v2 information. Content published by the authors has been made for informational and educational purposes only. The authors do not make any representation or warranties with respect to the accuracy, applicability, fitness, or completeness of the content. The authors hereby disclaim any and all liability to any party for any direct, indirect, implied, punitive, special, incidental or other consequential damagaes arising directly or indirectly from any use of the content, which is provided as is, and without warranties.