harry.sufehmi.comharry.sufehmi.com | life is a struggle – information wants to be free

harry.sufehmi.com life is a struggle – information wants to be free Menu Skip to content Search for: How to run Proxmox with only a single public IP address 10/12/2020 Etc sufehmi IPv4 address is becoming rarer by each day. In some cases, it can be pretty hard to get multiple IPv4 address for your Proxmox server. Thankfully, Proxmox is basically a Debian Linux OS with Proxmox layer on top of that. So that gives us quite a lot of flexibility. This tutorial will help you to create a fully functional Proxmox server running multiple containers & virtual machines, using only a single IPv4 address. These are the main steps : Create port forwarding rules Make sure it’s executed automatically everytime the server is restarted Setup a reverse-proxy server : to forward HTTP/S requests to the correct container / virtual machine Setup HTTPS For CT (container) / VM (virtual machine) that contains webserver, point 3 is important – because there’s only one public IP address, so there’s only one port 80 and 443 that’s facing the Internet. By forwarding port 80 and 443 to a reverse-proxy in a CT, then we’ll be able to forward incoming visitors, by hostname / domain name, to the correct CT/VM. 1. CREATE PORT FORWARDING RULES Modify the following to match your host’s interface name & CT/VM’s internal IP addresses, then copy-paste to terminal : ###### All HTTP/S traffic are forwarded to reverse proxy iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 80 -j DNAT --to 10.10.50.1:80 iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 443 -j DNAT --to 10.10.50.1:443 ###### SSH ports to each existing CT/VM iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 22101 -j DNAT --to 10.10.50.1:22 iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 22102 -j DNAT --to 10.10.50.2:22 iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 22103 -j DNAT --to 10.10.50.3:22 iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 22104 -j DNAT --to 10.10.50.4:22 Then we save it : iptables-save > /etc/iptables.rules 2. EXECUTE IPTABLES AT SERVER RESTART Edit /etc/network/interfaces file, find your network interface name that’s facing the Internet (in my case, vmbr0) – then add the pre-up line as follows : auto vmbr0 pre-up iptables-restore < /etc/iptables.rules 3. SETUP REVERSE-PROXY In a CT, install Nginx. Then for each domain, create a configuration file like this, for example: /etc/nginx/sites-available/www.my_website.com : server { listen 80; server_name www.my_website.com; location / { proxy_pass http://10.10.50.2:80; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } } To activate it (assuming you’re using Ubuntu) link it to /etc/nginx/sites-enabled/ , then restart Nginx : ln -s /etc/nginx/sites-available/www.my_website.com /etc/nginx/sites-enabled/www.my_website.com /etc/init.d/nginx restart note : as noted before, all HTTP/s traffic will have to go through this reverse-proxy. You may wish to tune this Nginx installation accordingly. 4. SETUP HTTPS It’s very easy with Let’s Encrypt once you’ve done point 3 above. Do the following on the reverse-proxy CT : sudo apt-get update ; sudo apt-get install -y certbot python3-certbot-nginx sudo certbot --nginx sudo /etc/init.d/nginx restart Reference: https://gist.githubusercontent.com/basoro/b522864678a70b723de970c4272547c8/raw/a985657453f72683040fbe38b1db6b1989618116/proxmox-proxy Leave a comment Installing HTTrack on Ubuntu from Source 9/11/2020 Etc sufehmi Today I needed to have the latest version of HTTrack installed to make a (static) mirror of a website that I managed After a few attempts, this is how you compile & install HTTrack from source on Ubuntu : wget "http://download.httrack.com/cserv.php3?File=httrack.tar.gz" mv cserv.php3\?File\=httrack.tar.gz httrack.tar.gz tar xzvf httrack.tar.gz cd httrack-3.49.2/ ### the following is the key to a successful install apt-get install zlib1g-dev libssl-dev build-essential ./configure && make && make install One comment so far Cutting a Table out of a mysqldump output file 9/11/2020 Open-Source , Teknoblogia sufehmi I was restoring the backup of a MySQL 5.x server into MySQL 8.x server – and found out that it corrupt the MySQL 8.x ‘s mysql table Which stores the usernames and passwords. So I had to delete the mysql table from the backup, before trying to restore it again Turn out it’s pretty easy, just will take some time since it’s a pretty big backup : # search for beginning of 'mysql' table cat backup.mysql | grep -n Current Database: `mysql` # 155604:-- Current Database: `mysql` # search for ending of 'mysql' table tail -n +155604 backup.mysql | grep -n "Current Database" # 1: -- Current Database: `mysql` # 916:-- Current Database: `phpmyadmin` # cut that table out head -155603 backup.mysql > new.mysql tail -n +$(( 155603+916 )) backup.mysql >> new.mysql # voila ! View all 6 comments Crontab runs on different timezone : here’s the fix 9/11/2020 Open-Source , Teknoblogia , Ubuntu crontab , timezone , Ubuntu sufehmi A few days ago I got reports that a server is running its cron jobs at strange times. Logged in, and indeed it was. A huge backup was running during peak hours. Saying that it disrupt people’s work is an understatement. To my surprise, the explanation for this issue can not be found straightaway. Took some googling to find the cause. And even more time to find the correct solution. So to cut the chase – /etc/localtime was a link to /usr/share/zoneinfo/America/NewYork Changed it to /usr/share/zoneinfo/Asia/Jakarta – and voila, now the cronjobs are running at the correct times. Hope it helps View all 3 comments XCTB – X Compression Tool Benchmarker 7/11/2020 In English , Open-Source , Teknoblogia bash , bzip2 , gzip , lrzip , pbzip2 , pigz , plzip , rzip , xz sufehmi I deal with a lot of big files at work. While storage capacity is not infinite indeed. So it’s in my interest to keep the file sizes as low as possible. One way to achieve that is by using compression. Especially when dealing with log files, or database archive, you can save a ton of space with the right compression tool. But space saving is not the only consideration. You also need to weighs in other factors. Such as : File type : different tool will compress different type of file differently CPU multi-core capabilities Compression speed Compression size Decompression time But there are so many great compression tools available in Unix / Linux. It can be really confusing to choose which one to use even for a seasoned expert. So I created X Compression Tool Benchmarker to help with this. Features : Test any kind of file : just put the file’s name as the parameter when calling the script. Then it will be tested against all the specified compression tools. Add more compression tool easily : just edit the compressor_list & ext_file variable, and that’s it Fire and forget : just run the script, and forget it. It will run without needing any intervention CSV output : ready to be opened with Libre Office / Excel, and made into graphs in seconds. Here’s a sample result for a Database archive file (type MySQL dump) : The bar chart on top of this article is based from this result. As you can see, currently this script will benchmark the following compression tools automatically : pigz – gzip – bzip2 – pbzip2 – lrzip – rzip – zstd – pixz – plzip – xz The result, for each different file types, may surprise you ...