<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nginx on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/nginx/</link>
    <description>Recent content in Nginx on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 06 Jun 2026 09:36:31 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/nginx/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming Exposed Services in Your Homelab with a Reverse Proxy</title>
      <link>https://linuxeries.org/post/2026-06-06-taming-exposed-services-in-your-homelab-with-/</link>
      <pubDate>Sat, 06 Jun 2026 09:36:31 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-06-06-taming-exposed-services-in-your-homelab-with-/</guid>
      <description>&lt;h2 id=&#34;introduction-to-reverse-proxies&#34;&gt;Introduction to Reverse Proxies&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen this go wrong when people expose their homelab services directly to the internet - it&amp;rsquo;s a security risk waiting to happen. Exposing multiple services can make them vulnerable to attacks and unauthorized access. One way to mitigate this risk is to use a reverse proxy, which acts as an intermediary between your services and the internet. In practice, this means you can expose a single IP address and port to the internet, while keeping your services hidden behind the reverse proxy.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
