Page Comparison

Clone the Node Tracker software
Configure zen.conf
Run the tracker and check your node on the tracking website

Description

Command

1

Install npm, upgrading it to the stable release

Code Block
sudo apt-get install npm -y && sudo npm install -g n && sudo n stable

The above may fail on some Debian 9 10/11 instances, in such cases, use the following to install npm and node js

Code Block
sudo apt-get install -y nodejs sudo npm install -g n && sudo n stable

2

Change directory (cd) to the user's home directory and clone the Node Tracker software

Code Block
cd ~/ && git clone https://github.com/HorizenOfficial/nodetracker.git

3

Change directory (cd) to where the software has been cloned

Code Block
cd nodetracker

4

Install the Node Tracker with npm

Code Block
npm install

5

Locate your node's public IPv4 and/or IPv6 address(es) and append them to the zen.conf file as external IP address(es) connected over port 9033 (default)

ONLY SUPER NODES ARE REQUIRED TO PERFORM EVERY COMMAND IN THIS STEP

SECURE NODES REQUIRE AT LEAST ONE EXTERNAL ADDRESS AND PORT APPENDED INTO ZEN.CONF

NOTE: Secure Nodes only require one type of IP, Super Nodes require both

NOTE: Replace <IPv4> with the public IPv4 of your node, remove <brackets>

NOTE: Replace <IPv6> with the public IPv6 of your node in compressed notation without leading zeros, remove <brackets>

Use the following link to ensure your IPv6 address is in compressed notation:

https://www.ultratools.com/tools/ipv6Compress

Create environmental variables for IPv4

Code Block
IPV4=<IPv4>

Append external IPv4 into zen.conf

Code Block
echo "externalip=$IPV4" >> ~/.zen/zen.conf

Create environmental variables for IPv6

Code Block
IPV6=<IPv6>

Append external IPv6 into zen.conf

Code Block
echo "externalip=$IPV6" >> ~/.zen/zen.conf

Append port into zen.conf - SECURE AND SUPERconf

Code Block
echo "port=9033" >> ~/.zen/zen.conf

6

Restart zend and check the address configuration

NOTE: The output of the 2nd command should display the address(es) entered in the previous step

Code Block
zen-cli stop && sleep 8 && zend && sleep 30

Code Block
zen-cli getnetworkinfo \| grep address

7

Configure the tracker by running the setup process, for this you will need the following details

Enter node type (secure or super)
Stake t_address (the t_address with 42 or 500 ZEN from step 7.2)
Email address - to receive alerts for any exceptions, downtimes or notifications related to your node
Fully-Qualified Domain Name (FQDN)
IP address version (ipv4, or ipv6)
Region code (choose NA, or EU), defaults to your node's nearest region
Optional node category - alphanumeric (used to help categorize nodes)
- Must have an entry to be able to generate an API sub key
- If using an optional verified stake address created with the Stake Tool enter the category associated with the API sub key

Code Block
node setup.js

8

Now test the Node Tracker installation and configuration

Code Block
node app.js

9

Leave the Node Tracker running in your terminal and check the status of your node on the tracking website, use the search box and enter the FQDN of your nodehttps://securenodes.zensystem.io/nodes/all << Secure Nodes

https://supernodes.zensystem.io/nodes/all << Super Nodes

Select your node and check the following values (top left of the detail page) are true and up respectively - example shown to the right

NOTE: The tracking server validates certificates in batches, you may only see a State of "up" and a Cert Valid of "not checked" or "false not found" until the tracking server runs a batch of certificate checks. You can proceed with further steps without waiting for a Cert Valid of "true"

10

If your node displays on the tracking site with "state: up", exit the tracker by pressing CTRL + c and continue to part 9

Part 7 Part 8 of 11 - Install and Configure the Node Tracker

Part 9

Insert excerpt

	Social Links
	Social Links
nopanel	true

Versions Compared

Old Version 71

New Version Current

Key

Part 7

Part 8 of 11 - Install and Configure the Node Tracker

Part 9