<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Performance on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/performance/</link>
    <description>Recent content in Performance on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 31 Oct 2026 11:12:34 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/performance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Nginx on a Pi: why SSL connections keep timing out after adding SNI for multiple sites</title>
      <link>https://linuxeries.org/post/2026-10-31-nginx-on-a-pi-why-ssl-connections-keep-timing/</link>
      <pubDate>Sat, 31 Oct 2026 11:12:34 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-10-31-nginx-on-a-pi-why-ssl-connections-keep-timing/</guid>
      <description>&lt;p&gt;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.&lt;/p&gt;&#xA;&lt;p&gt;The usual culprit is the dance between &lt;strong&gt;SNI&lt;/strong&gt;, &lt;strong&gt;OpenSSL’s default cipher selection&lt;/strong&gt;, 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.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
