<story><title>You may not need Cloudflare Tunnel. Linux is fine</title><url>https://kiwiziti.com/~matt/wireguard/</url></story><parent_chain><item><author>omnicognate</author><text>What&amp;#x27;s actually being done here is buried in a mass of analogies. AFAICT it&amp;#x27;s:&lt;p&gt;* Exposing a server running on the home network (behind NAT on a dynamic IP) to the internet.&lt;p&gt;* Doing so by renting a cheap VPS and using wireguard to forward traffic to the server at home.&lt;p&gt;I love wireguard and use it continuously. My phone has always on wireguard to my home network so all my phone traffic goes through my home router&amp;#x2F;dns, I can access the various private servers I have at home, get dns based ad blocking etc. I use an ISP that give me a static IP so it was easy to set up. It works like a dream.&lt;p&gt;That said when I want to run a public server I just rent a VPS and run it on that. I don&amp;#x27;t want anything I don&amp;#x27;t own initiating connections to anything on my home network in any way.</text></item></parent_chain><comment><author>perrygeo</author><text>&amp;gt; That said when I want to run a public server I just rent a VPS and run it on that&lt;p&gt;I have a setup similar to the OP and there&amp;#x27;s a really good reason for it: cost. For $2k in hardware (one time) and a VPS + electricity at $20&amp;#x2F;mo, I can run a 64 core, 192Gb, 24TB server. Let&amp;#x27;s call that $4400 over the course of 10 years. You would burn through that budget in roughly 1 month to get the same specs on AWS.&lt;p&gt;Obviously I&amp;#x27;m neglecting the impact and cost of network, if it&amp;#x27;s a hobby you can just reuse your existing connection but you can always buy a dedicated line (and adjust the cost calculation accordingly)&lt;p&gt;In terms of security, you can mitigate the surface area by running a reverse proxy on the VPS. I&amp;#x27;ve got nginx on the front line which does TLS then proxy_passes to my basement server at its wireguard IP address. So it&amp;#x27;s strictly limited to http, no direct database or ssh access.&lt;p&gt;I don&amp;#x27;t know if I&amp;#x27;d ever run a &amp;quot;real&amp;quot; website this way but it&amp;#x27;s great for hobbies and side projects.</text></comment>
<story><title>You may not need Cloudflare Tunnel. Linux is fine</title><url>https://kiwiziti.com/~matt/wireguard/</url></story><parent_chain><item><author>omnicognate</author><text>What&amp;#x27;s actually being done here is buried in a mass of analogies. AFAICT it&amp;#x27;s:&lt;p&gt;* Exposing a server running on the home network (behind NAT on a dynamic IP) to the internet.&lt;p&gt;* Doing so by renting a cheap VPS and using wireguard to forward traffic to the server at home.&lt;p&gt;I love wireguard and use it continuously. My phone has always on wireguard to my home network so all my phone traffic goes through my home router&amp;#x2F;dns, I can access the various private servers I have at home, get dns based ad blocking etc. I use an ISP that give me a static IP so it was easy to set up. It works like a dream.&lt;p&gt;That said when I want to run a public server I just rent a VPS and run it on that. I don&amp;#x27;t want anything I don&amp;#x27;t own initiating connections to anything on my home network in any way.</text></item></parent_chain><comment><author>BlueTemplar</author><text>These days, your ISP would (hopefully) give you at least a whole (static) &amp;#x2F;56, so you can always reserve some prefixes for your not-really-home networks ?&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.ripe.net&amp;#x2F;publications&amp;#x2F;docs&amp;#x2F;ripe-690#4-2-3--prefixes--longer-than--56&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.ripe.net&amp;#x2F;publications&amp;#x2F;docs&amp;#x2F;ripe-690#4-2-3--prefi...&lt;/a&gt;</text></comment>