https://blog.margrop.net/en/tag/reverse-proxy/ Recent content in Reverse-Proxy on Margrop Blog Hugo -- gohugo.io en-US Fri, 26 Jun 2026 12:30:00 +0800 https://blog.margrop.net/en/post/build-private-docker-registry-without-hassle/ Fri, 26 Jun 2026 12:30:00 +0800 https://blog.margrop.net/en/post/build-private-docker-registry-without-hassle/ <blockquote> <p><strong>TL;DR</strong></p> <p>My home server runs a single <code>registry:2</code> container that currently holds <strong>13 GB of cached blobs across 95 repositories</strong>. Every NAS, Proxmox node, Mac, and Windows machine on my LAN pulls through it. A cold start of <code>alpine:3.19</code> finishes in under a second, with zero traffic going out to the public Docker Hub.</p> <p>This isn&rsquo;t a one-line &ldquo;install Docker and run a container&rdquo; tutorial. I&rsquo;ll show you the <strong>production-grade deployment script I actually run</strong>, walk through the Docker v2 auth flow, and call out the four reverse-proxy pitfalls that turn every <code>docker login</code> into a 401 mystery. You&rsquo;ll leave able to: ① bring up an authenticated registry in 10 minutes; ② explain why the <code>WWW-Authenticate</code> header is sacred; ③ describe the whole thing to a non-technical family member without losing accuracy.</p> </blockquote> https://blog.margrop.net/en/post/nas-speedtest-subdomain-acceleration/ Fri, 24 Apr 2026 09:00:00 +0800 https://blog.margrop.net/en/post/nas-speedtest-subdomain-acceleration/ <blockquote> <p><strong>Short version</strong></p> <p>If your NAS is painfully slow when accessed from outside your home, and you control both your domain name and your reverse-proxy entry, putting <code>speedtest</code> into the subdomain can sometimes make a dramatic difference.<br> This is not magic and it is not guaranteed, but it often appears to hit a more permissive carrier policy path for “speed-test-like” traffic.</p> </blockquote> <p>This post was inspired by a discussion on the fnNAS forum. The original thread makes a very direct claim: some home broadband lines seem to throttle ordinary NAS access quite aggressively, but once the hostname contains <code>speedtest</code>, the connection can suddenly behave much better.</p> <p>I am not repeating the forum post word for word. Instead, I am turning the idea into a longer-lived technical note that answers three questions:</p> <ol> <li>Why this trick can work</li> <li>How to set it up with the least amount of moving parts</li> <li>When it will not work, or is not worth the effort</li> </ol>