In this tutorial, we are going to configure a brand new $5/month DigitalOcean server that will run one or multiple Helium miners. Note that by using the link above, you will be rewarded with a $100 credit bonus that is valid for two months, which is perfect to test the platform and also two months of free miner hosting!
I am not going to get into details about what Helium is and how to use it, but it’s an amazing project where people all around the world are getting together to build a HUGE LoraWAN mesh network to enable anyone to have access to an almost-free IoT network. To check more, go to https://www.helium.com.
This tutorial video
If this video helped you, please consider donating to:
- BuyMeACoffee – https://www.buymeacoffee.com/dspillere
- BTC – bc1qwn59fjhmz2wy376y6vltjj73a63j0nzaapu42f
- ETH – 0x2b4d4a660CddaE942C26821a5512c32023719476
- HNT – 14bnEtUmqPaCrXmjzQ8XasTJhz7hfyWY9gt2ByqUdvBJVVEczmr
Create a new DigitalOcean Server
After creating your DigitalOcean account, log in, and create a new Droplet like the gif below:
Once your droplet has finished provisioning, you will be able to connect to it using the provided IPv4 address and the password that you used on the previous step. For this tutorial, the server IPv4 is 18.104.22.168, remember this as we will use it in many future steps.
Let’s connect to the server using the terminal. If you are on Mac you can use iTerm, and if you are on Windows, I recommend checking out the Windows Terminal. If you have any questions, just fill out the comment form with your questions and I will do the best to help you out!
To connect to the server, on the terminal, type
ssh firstname.lastname@example.org (change the IP to your own server address), type yes and the password.
If you see root@helium-miner:~#, this means that you are connected! Type
apt update && apt upgrade to make sure we have all programs running on the latest version!
Good job, let’s move on to the next steps.
Let’s check if docker is working by typing
From the helium miner documentation: Before launching the Miner, you will want to configure ports on your network to forward two ports:
- 44158/TCP: the Miner communicates to other Miners over this port. The networking logic knows how to get around a lack of forwarding here, but you will get better performance by forwarding the port.
- 1680/UDP: the radio connects to the Miner over this port. You will not be able to forward packets or participate in Proof of Coverage without this.
This means that for the miner, we need to open ports 44158/TCP and 1680/UDP, to do so, type
ufw allow 44158/tcp and
ufw allow 1680/udp.
Running your container
It’s time to configure and install the miner. First of all, let’s create a folder where we will store all the miner files. On the terminal, type
mkdir ~/miner_data to create an empty folder where all the miner data will resid.
Create a file caller runMiner.sh with
nano runMiner.sh and type the following code block:
docker run -d \ --env REGION_OVERRIDE=EU868 \ --restart always \ --publish 1680:1680/udp \ --publish 44158:44158/tcp \ --name miner \ --mount type=bind,source=/root/miner_data,target=/var/data \ quay.io/team-helium/miner:miner-amd64_2020.08.21.0_GA
You need to change two lines on the block, the first is to make sure you are using the right REGION_OVERRIDE frequency to:
US915 | EU868 | EU433 | CN470 | CN779 | AU915 | AS923 | KR920 | IN865
As I am in Europe, I am going with EU868 (Europe, frequency 868Mhz).
The second part that you need to update is the last line, where you need to select the right docker image. You can get the latest version at https://quay.io/repository/team-helium/miner?tab=tags. For this server, make sure to use an amd64 image such as miner-amd64_2020.08.21.0_GA, which is the latest one (at the time I am writing this).
At this point, everything is ready to go! All you need to do is to start the miner using
sh runMiner.sh and it should start!!! The first thing docker will do is check if you have the images on your server, which you don’t, and download them. Then it will automatically start the miner, which will then start syncing with the blockchain!
To check if the image is running, type
docker ps, and the result should be something similar to this:
On your gateway, point it to our server 22.214.171.124 and you will be good to go!
Backup your swarm key
This step is extremely important! Once helium enables miners to actually mine HNT tokens, you will need to pay $50 to join the network, and if you lose the key, you will need to purchase a new one!
To back up the key, go to the miner folder
~/miner_data/miner, and inside you will find a file called swarm_key. Make sure you save this somewhere safe for future use. (If something goes wrong with the server, this is the only file that will enable you to recover your miner!)
Check if the blockchain is in sync
docker exec miner miner info height && curl https://api.helium.io/v1/blocks/height will compare the height of the blockchain we have on the server with the real one. Once the two numbers match, it means that our server is fully in sync and ready to roll!
As you can see in the image above, my server is yet not in sync as locally I have 455760 and the official block height is 465893.
Running multiple miners on the same server
To run a second miner, you need to open two new ports, 1681/udp and 44159/tcp with
ufw allow 44159/tcp and
ufw allow 1681/udp.
Create a new folder for the miner data with
mkdir ~/miner_data2, create a new runMiner2.sh and edit the file as suggested below:
docker run -d \ --env REGION_OVERRIDE=EU868 \ --restart always \ --publish 1681:1680/udp \ --publish 44159:44158/tcp \ --name miner2 \ --mount type=bind,source=/root/miner_data2,target=/var/data \ quay.io/team-helium/miner:miner-amd64_2020.08.21.0_GA
Then to run it, simply type
To test the block sync, use
docker exec miner2 miner info height && curl https://api.helium.io/v1/blocks/height