In a previous blog post (Fail2ban + Tarpit), I explained how to setup a Tarpit for Fail2ban to…
Category: Sysadmin
In my previous guide on dehydrated, the bash client for let’s encrypt, I’ve only touched on the DNS-01…
Dehydrated was firstly known as letsencrypt.sh but because letsencrypt is a trademark, they decided to rename the project,…
I went through my google analytic log and updated the referrer blacklist for Nginx. As before, it’s available…
This website is hosted on my own dedicated server (a kimsufi) and like every server, it’s getting regularly attacked.
To identify those attacks, I needed to add a layer of security to ban recurrent attempt, this layer is Fail2ban. It’s a widely known and recognized python script that analyses your log file to ban repetitive failed authentication.
In the last revision of transmission, I couldn’t get the user/password for the RPC of transmission work.
To resolve this problem, I decided to use Nginx as reverse proxy to provide an SSL connection and also a way to secure the access to the RPC and the web interface.
I compiled myself transmission and it’s installed in /usr/local/. In case you are using the packaged version of Debian/Ubuntu you need to change the /usr/local/ by /usr/.
I just discovered lately Bittorrent Sync and found it to be an amazing way to replace dropbox or any other Cloud Storage since I’m owning a server and a raspberry pi.