Tls

Running a multi‑site reverse proxy on a Raspberry Pi is a classic hobby‑project. The Pi’s low power draw and cheap price make it a go‑to for hosting tiny web services, internal dashboards, or a personal API gateway. Throw TLS in there and you get confidentiality and integrity, but one small mis‑configuration can make every HTTPS request hang until the client gives up.

The usual culprit is the dance between SNI, OpenSSL’s default cipher selection, and the Pi’s limited CPU. Below I’ll walk through why this happens, how to spot it, and the practical tweaks that keep the Pi from blowing up the handshake.

These tags should help categorize the content and make it easier for readers to find related posts on your blog.

As the internet becomes an increasingly integral part of our lives, privacy and security concerns continue to grow. One of the most overlooked aspects of online communication is the Domain Name System (DNS). DNS is essential for translating human-readable domain names (like example.com) into IP addresses that computers can use to route requests. However, the traditional method of DNS queries is insecure, allowing potential eavesdroppers to track and intercept a user’s online activity. To address this concern, DNS over TLS (DoT) has emerged as an effective solution.