Caddy on Geeky Schmidthttps://geekyschmidt.com/tags/caddy/Recent content in Caddy on Geeky SchmidtGeeky Schmidthttps://geekyschmidt.com/images/papermod-cover.pnghttps://geekyschmidt.com/images/papermod-cover.pngHugoenCopyright ©2002-2026, Nicholas Schmidt; all rights reserved.Tue, 18 Aug 2026 13:00:00 +0200From Local Disk to SeaweedFS: Bypassing a GoToSocial Fileserver Bug with Self-Hosted S3 Storagehttps://geekyschmidt.com/post/2026-08-18-seaweedfs/Tue, 18 Aug 2026 13:00:00 +0200https://geekyschmidt.com/post/2026-08-18-seaweedfs/<p>GoToSocial had a bug serving 0-byte images. I could have patched Go source code. Instead, I bypassed the entire fileserver and offloaded 92,000 files to SeaweedFS. Sometimes the best fix is an architecture pivot, not a code change.</p> <hr> <h2 id="the-problem">The Problem</h2> <p>GoToSocial v0.22.1 has a confirmed bug where it uses <code>mmap</code> to serve media. On certain configs, this produces <code>EINVAL</code> errors during <code>close()</code>, resulting in HTTP 200 responses with 0-byte bodies. Caddy logs unexpected EOF because the connection drops mid-stream. The bug doesn&rsquo;t care whether the file exists — the codepath itself is broken.</p>