<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gluetun on homelab</title>
    <link>https://homelab.nbkelley.com/tags/gluetun/</link>
    <description>Recent content in Gluetun on homelab</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://homelab.nbkelley.com/tags/gluetun/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Gluetun VPN Service</title>
      <link>https://homelab.nbkelley.com/docs/services/gluetun-vpn/</link>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      <guid>https://homelab.nbkelley.com/docs/services/gluetun-vpn/</guid>
      <description>&lt;h1 id=&#34;gluetun-vpn-service&#34;&gt;Gluetun VPN Service&lt;a class=&#34;anchor&#34; href=&#34;#gluetun-vpn-service&#34;&gt;#&lt;/a&gt;&lt;/h1&gt;&#xA;&lt;h2 id=&#34;what-was-established&#34;&gt;What Was Established&lt;a class=&#34;anchor&#34; href=&#34;#what-was-established&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Gluetun&lt;/strong&gt; is a lightweight Docker container acting as a dedicated VPN gateway for other containers.&lt;/li&gt;&#xA;&lt;li&gt;Implements the &lt;strong&gt;sidecar pattern&lt;/strong&gt;: dependent containers (e.g., qBittorrent, nzbget, prowlarr) share Gluetun&amp;rsquo;s network namespace via &lt;code&gt;network_mode: &amp;quot;service:gluetun&amp;quot;&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;li&gt;AirVPN selected as the provider over ProtonVPN/Mullvad due to superior port forwarding support required for P2P services.&lt;/li&gt;&#xA;&lt;li&gt;Container-level VPN on the servarr VM is architecturally separate from the network-level UniFi VPN on Helms Deep (VLAN 2).&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;deployment-context&#34;&gt;Deployment Context&lt;a class=&#34;anchor&#34; href=&#34;#deployment-context&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Gluetun runs on the &lt;strong&gt;servarr VM&lt;/strong&gt; (&lt;code&gt;192.168.1.112&lt;/code&gt;) as part of the Servarr Docker Compose stack at &lt;code&gt;/docker/servarr/&lt;/code&gt;. It is configured via &lt;code&gt;.env&lt;/code&gt; file in that directory.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Servarr Stack - Gluetun VPN Troubleshooting</title>
      <link>https://homelab.nbkelley.com/docs/services/servarr-vpn-troubleshooting/</link>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      <guid>https://homelab.nbkelley.com/docs/services/servarr-vpn-troubleshooting/</guid>
      <description>&lt;h1 id=&#34;servarr-stack---gluetun-vpn-troubleshooting&#34;&gt;Servarr Stack - Gluetun VPN Troubleshooting&lt;a class=&#34;anchor&#34; href=&#34;#servarr-stack---gluetun-vpn-troubleshooting&#34;&gt;#&lt;/a&gt;&lt;/h1&gt;&#xA;&lt;blockquote class=&#39;book-hint &#39;&gt;&#xA;&lt;p&gt;&lt;strong&gt;Historical note:&lt;/strong&gt; This session was conducted on a machine at &lt;code&gt;192.168.1.30&lt;/code&gt; (hostname possibly &amp;ldquo;Varda&amp;rdquo; at the time, directory &lt;code&gt;~/home/nbkelley/docker/servarr&lt;/code&gt;). The current production Servarr stack lives on the &lt;code&gt;servarr&lt;/code&gt; VM at &lt;code&gt;192.168.1.112&lt;/code&gt;, directory &lt;code&gt;/docker/servarr/&lt;/code&gt;. See &lt;a href=&#34;https://homelab.nbkelley.com/docs/services/servarr/&#34;&gt;Servarr - Media Automation Stack&lt;/a&gt; for current configuration. The troubleshooting patterns documented here remain applicable.&lt;/p&gt;&lt;/blockquote&gt;&lt;h2 id=&#34;what-was-established&#34;&gt;What Was Established&lt;a class=&#34;anchor&#34; href=&#34;#what-was-established&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;This session documents the deployment and troubleshooting of the Servarr media automation stack (Sonarr, Prowlarr, qBittorrent) behind a Gluetun VPN container. The stack relies on &lt;code&gt;network_mode: service:gluetun&lt;/code&gt; to route all container traffic through AirVPN.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
