How Set Up a Node for RipaEx

in news •  2 months ago

includes Cheat-Sheet for Quick Start at Bottom

Don’t forget to read:

Minimum requirements for running RIPA node (active nodes):

- at least 1 DEDICATED CPU core (no shared ones), x86 or x64 architecture (the higher the CPU clock speed, the better, recommendation 2 CPUs+)
 -  4 GB RAM (the more the better, recommendation 8GB+),
 -  Linux — Ubuntu 16.04 (this is optimal, and this guide is written for it)
 -  20GB free space (we recommend SSD/m.2, as opposed to traditional HDD drives, recommendation 40GB+)

Recommended VPS/Cloud providers:

-  Digital Ocean
 -  Vultr
 -  OVH

For this guide, we’ll use Digital Ocean, where you get $10 credit when you sign up ( Standard Cost: $5 pm for 1vCPU, 1Gb Ram, 25Gb SSD & 1Tb transfer) But all providers have similar deals.

1. Get yourself a server for your node

(for our guide we’ll use Digital Ocean)

We will create a droplet via DigitalOcean interface, for the Linux distro we will use Ubuntu 16.04.2 x64

Choose a plan, the $5 per month plan (1GB RAM/1CPU) should be sufficient.

We will choose New York #3 (your preferred location can be anything, but we avoid Singapore and Bangalore for possible latency issues).

Next, finalize and create your 1 droplet after entering a host name, click CREATE

Once your server instance is ready, you will receive all of the info in your email (username, password, and IP address).

Once you have received this info on our email, it will be used throughout this guide. (replace with your info when setting up your node):

username: root
password: xxx (sent in email)
IP: xxx.xxx.xxx.xxx (sent in email)
SSH port: 22 (this is default)

2. Connect to your newly created server instance via SSH

Windows: you can use any SSH client. For our example we will use Putty (an open-source client you can download here: PUTTY DOWNLOAD)
MAC OS: open Terminal ( To start Terminal, go to your Mac’s Applications folder => click on the Utilities folder => then click on Terminal).
Linux: depending on your distribution, you can usually also open it by pressing a combination of “Ctrl + Alt + T” keys.

For terminal in Linux / MAC OS you can connect with this command:
ssh user@<server-ip>
example for our instance of server in Linux / MAC OS would be:
ssh root@162.243.232.177

For our guide we’ll use Putty (Windows) — start it up:

Under Host Name (or IP address) input the IP your server provided in the email and click Open. To skip this step for future, you can click on Default Settings and Save to save this IP, so the next time you start, you can just click on Default Settings and load button. You can also give the session a name, like “RIPA_MAINNET”, save it, and load it in the future as needed for this particular server.

When first connecting to this server from your computer, you will see a security alert (rsa2 key fingerprint). Click on “Yes” to continue. This will be shown only the first time, after that it will be stored for future sessions.

Now the command line will be shown, asking you to provide the username that you received in your email, “root”. Type it in and press [enter]. After that, you will be prompted for your password*. Enter the one sent in your email and press [enter] to connect to your server. You will notice the cursor does not move when typing the password, just continue to put in password and press enter.

As a security feature, a lot of providers have a mandatory change of the password they first assign to your root user, in which case, you will be asked to first input your current password (from the email), and enter a new one (we strongly recommend 16+ char one with a mix of letters, numbers, special characters).

Save your root password as you can get locked out of your own server if you forget it. At this stage, you can do a test and type exit, and then reconnect to your server — follow the steps from the beginning of #2 to connect again.

3. Setting Up Regular User With Sudo Privileges

Now that we successfully connected and changed the password for root it is time to create a new regular user with sudo privileges (sudo privileges allow a user to run programs with the security privileges of another user).

How to add new regular user:

adduser < yourusername >
our example: adduser ripa
Enter a new password, enter it again, and press [enter] 6 times to accept all of the default values.

Now that we have successfully created user with the username ripa(you can choose whatever username you want except root of course), it is time to assign this regular user sudo privileges.

How to add sudo privileges to our newly created regular user:

usermod -a -G sudo < yourusername >
our example: usermod -a -G sudo ripa

Now it is time to disconnect and reconnect as the newly created user (in our case ripa and not as root. Type exit and press [enter]. Your Putty session will close. Reopen Putty after it disappears.

4. Connecting Using Your New User

Connect to your server, but now instead of logging in as root, we will login with new user. Type your username and press enter, followed by the password of that user:

For terminal in Linux / MAC OS you can connect with this command:
ssh yourusername@<server-ip>
example for our instance of server in Linux / MAC OS would be:
ssh ripa@162.243.232.177

5. Installing the RIPA Node

Now that we have our node ready, it is time to install RIPA. First we will download the RIPA installer called “RIPA Commander” simply by executing these commands:

  1. Download the Ripa Commander:

wget https://raw.githubusercontent.com/RipaEx/ripa-commander/master/RIPA_commander_mainnet.sh -O ~/RIPA_commander_mainnet.sh

  1. Make it runnable:

chmod 700 ~/RIPA_commander_mainnet.sh

  1. Execute the file:

./RIPA_commander_mainnet.sh

Now the RIPAcommander installation script will open. At the first step, you will need to provide your user’s password (in our example, the password for user ripa).

Since this is your first time running this installer, it will check for all of the dependencies and updates the RIPA node needs to run — press [enter] to continue and be patient. It might take a while, so do not interrupt the process.

(installing prerequisites — don’t interrupt)

After this process finishes you will be asked to reboot your server — execute with the command:

sudo reboot

Don’t be alarmed by this message it simply states since you restarted your server, Putty has lost connection to it. Simply click on OK:

Now open putty again, reconnect with your user, and execute :
./RIPA_commander_mainnet.sh
Provide your password if asked to enter the menu.

You will now enter into RIPA commander menu.

There are a lot of options, and since this is our first installation, you will input number 1 and press [enter] to execute the Install RIPA process. Now the RIPA node installation will start — don’t interrupt, it might take a few minutes!

After the node installation is done, you will be asked if you want to set the secret passphrase of your delegate (the password you are using to access your delegate’s wallet). By pressing [enter] you will be prompted to enter it, and if you do not want to set it, you can press N and [enter].

If you pressed enter (and chose option Y), you will be prompted to enter your delegate passphrase — enter it (or copy from elsewhere and paste it with the right click in putty) and press [enter] to save it — you can also change it later with option 5 in the RIPA command center.
Now you will be asked if you are sure to save it to your config — [press enter] and your RIPA node server will start after that — voila, press [enter] to return to the RIPA command center.

6. Syncing Blockchain From a Snapshot

After you are done with the installation, you will be returned to the RIPA commander menu. To sync from a snapshot, we are going to use command 4. Rebuild Database.

A message will be shown:

Would you like to download the latest snapshot? (Y/n)
press ‘Y’ and ‘enter’ to download the latest official devnet snapshot.

Next, you will be asked:

Would you like to restore the snapshot now? (Y/n)
press ‘Y’ and ‘enter’ to restore from the snapshot you just downloaded. This will take a few minutes. Next you will see ‘Current snapshot has been restored’ and RIPA node will start. Press ‘enter’ to return to the menu.

7. Checking If You Are Synced

After this, we can check to see if your node is successfully synced to the blockchain (might take a minute or so to fully sync). Once back in the menu, press ‘L’ to view the log.

You should see messages like this “New block received” about every 8 seconds.

If you see this, your node is all ready and synced. Press ‘CTRL’ + ‘C’ to close the log and return to the RIPAcommander menu.

You can check to see if your node is running by pressing S + [enter]
(note that letters in RIPA command center are case sensitive so small s won’t work, same with other letters).*

Check the RIPA node logs by pressing L + [enter] — to exit log view press ctrl + C (to close the scrolling log text) and return to the RIPA command center.

You can stop the RIPA node process with K + [enter]— that will stop your node.

If you want to start it again press A + [enter] — this will start your node again

If your node is stuck, usually a simple R + [enter] will suffice (it will automatically kill and start RIPA node process).

0 + [enter] will exit the RIPA commander center and return you back to your home directory with a linux command prompt.

Play a bit and get accustomed to it — and remember, you can always enter RIPA comander with the command ./RIPA_commander_mainnet.sh (make sure you are in the correct directory where it is located, usually in home — you can get to your home directory by simply entering cd ~ )

BONUS: Cheat-sheet

(you can also perform a lot of the tasks without the need of RIPA commander):

Make sure you are in ripa-node directory by typing:
cd ~/ripa-node

After that you can perform a lot of tasks with simple commands (commands are written in bold):
 — — — — — — — — — — — — — — — — — — — — — — — — — —
Restarting your RIPA node: forever restart app.js
 — — — — — — — — — — — — — — — — — — — — — — — — — —
 — — — — — — — — — — — — — — — — — — — — — — — — — —
Real-time log of your RIPA node: tail -f ./logs/ripa.log
 — — — — — — — — — — — — — — — — — — — — — — — — — —
 — — — — — — — — — — — — — — — — — — — — — — — — — —
Killing your RIPA node process: forever stopall
 — — — — — — — — — — — — — — — — — — — — — — — — — —
 — — — — — — — — — — — — — — — — — — — — — — — — — —
Listing your forever processes (RIPA node): forever list
 — — — — — — — — — — — — — — — — — — — — — — — — — —
 — — — — — — — — — — — — — — — — — — — — — — — — — —
Updating your RIPA node : git pull
After updating, you need to restart the node: forever restart app.js
 — — — — — — — — — — — — — — — — — — — — — — — — — —

Still having issues? Join our Slack and a member of our team or one of the community members will be glad to help you out: https://ripaex.slack.com/

Remember to connect to us...

Website: www.ripaex.io
Bitcointalk ANN: bitcointalk.org/index.php?topic=3759172
Whitepaper: github.com/RipaEx/whitepaper/raw/master/eng/RipaEx_WP_EN.pdf
Facebook: www.facebook.com/ripaex
Twitter: twitter.com/ripaex
Gitter: gitter.im/RipaEx/RipaEx
GitHub: github.com/RipaEx/
Medium: medium.com/ripaex

Thanks to BoldNinja for the Original Ark Guide Adapted for Ripaex

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:
https://blog.ark.io/how-to-setup-a-node-for-ark-and-a-basic-cheat-sheet-4f82910719da

Awesome info...tq