It has been a month since we sold our fully automated 56/64 Vega rigs with 14 cards on 3 mobos and 3 PSU’s, automated Arduino hard reset and custom made software reset tools. All true and devoted miners would ask – why? Well, it was not a FUD nor price drop which made us go that way, but there were a dozen of other reasons for and against the sale. Actually, it was not our intention to sell it at all, but we just wanted to test the market and raised the price 50% up, so in case someone buys – we’ll profit nicely. As all we know, Radeon RX Vega are quite rare on the market nowadays, almost impossible to find at all!!!
This tutorial will be quite short because the procedure for adding IP addresses is almost the same for all Linux distributions and it’s easy. However I must mention that I tested this on Ubuntu 16.04.
It’s not always easy or possible to setup port forwarding so you can access your home PC or any other device through public IP your internet service assigns you. Problem is also if your ISP rotate IPs so you always need to keep track of it. One option is to try to convince ISP to give you static IP but traffic routing on ISP side can be also behind NAT, which might be complicated to configure and guys from ISP tend to tell you forwarding is not possible.
So what can you do about that? Sometimes nothing. 🙂
Those who are running crypto currencies mining operation know about importance of good automation. There are plenty of software around that can help you achieve as much automation as possible for different crypto currencies. But sometimes soft reboot of mining software is not an option. Especially in highly beta ecosystem such as AMD RX Vega rigs with blockchain driver and Windows 10. Even after tweaking voltage and frequency for graphic cards, blockchain driver is unstable and many times leads to Windows bluescreen or freeze that requires manual restart of the rig.
Actually I won’t get into details with Varnish and Nginx configuration because it really depends on your particular case. But it should be pretty straight forward as installing default packages:
apt install varnish
apt install nginx
I’m using port 443 for SSL services, so Haproxy is using this one. It also uses http port 80 and redirect that to https. Everybody knows that Haproxy is stable and quick in jobs it does and that’s load balancing and proxying traffic. I our case we are going to use it for SSL termination and forward traffic to Varnish which is going to occupy port 6081 (default). And Nginx will use port 8080 because it’s final destination in our setup. Varnish should cache most of the web content and hopefully put our dedicated server’s CPU at ease most of the time and leverage quite slow CPU to large amount of RAM (128GB).
In case of traffic increase we can easily balance our traffic to other servers behind Varnish, because Varnish can play load balancing role as well.
So you’re trying to install Hitch for SSL termination on your Ubuntu 16.04 server? Or you might think it’s good idea because you have it working on some other Linux distribution like CentOS?
Think again. After 3-4 spent hours I found solution, installed some other SSL terminator. 😉 (Haproxy). This is where you can return to Google to look for other site if you’are looking for how to tutorial on Hitch with Ubuntu. However you might continue reading to see what kind of mess you might encounter.
If you used to mine Monero for the past 2 months, you surely noticed a rapid increase in nethash. Discussing this with other community members the most of us agree that this brutal increase of net hash is related to botnets. Botnet-masters have found the way to monetize their huge CPU power, surely much profitable way then using it for useless or even paid DDoS attacks. Now, the Monero community is getting concerned because it seems that more then a half of the network hashrate is coming from the botnet-like structures. There are no adequate measures to isolate botnets from the network, although some pools, tend to fight the pest.