Raspberry PI – Secure port 80 with rate limiting

Since my Allsky camera is publicly available via Apache, secured with Let’s Encrypt and its own subdomain, I also wanted to harden the Raspberry Pi a little at network level – without risky experiments or unnecessary complexity. NAT provides basic protection for IPv4, but ports 80 and 443 in particular are publicly accessible. In addition, bots, scanners and automated requests generate unnecessary traffic.

My goal: a pragmatic firewall that allows real access, reduces bot noise and does not interfere with Let’s Encrypt. Here is the IPv4 part first – you can find an additional post about IPv6 here!

Activate automatic updates on the Raspberry Pi

Automatic updates on a Raspberry Pi are – in addition to other tweaks that I have presented here – particularly useful to ensure the security of the system. Regular updates close known security gaps and keep the operating system stable and up-to-date. Important security patches are installed automatically without manual intervention, which minimizes the attack surface for hackers and malware. In combination with email notifications, you are always informed when an update has been carried out or a problem has occurred. This ensures maximum security and reduces maintenance costs. And this is how it works:

Customize SSH port on a Raspberry Pi

The standard SSH port 22 is a popular target for attackers. If you want to additionally secure your Raspberry Pi, you can simply change the port for SSH access. In this guide, I will show you step by step how to do this.

Share Allsky camera via FRITZ!Box on the Internet

myFRITZ!LogoI use the indi-allsky software for my Allsky camera (more information here!). There have been very rare occasions when my camera has stopped responding – and of course you want to be able to look at last night’s images when you’re out and about. allsky-rodgau.de does offer a live image, but not such an extensive archive as the software. That’s why I found out how to access the camera from “outside”.