<story><title>You may not need Cloudflare Tunnel. Linux is fine</title><url>https://kiwiziti.com/~matt/wireguard/</url></story><parent_chain><item><author>fgonzag</author><text>Explain how you got a 64 core 192 GB RAM 24 TB server or workstation for 2k please</text></item><item><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></item><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>washadjeffmad</author><text>LGA 2011, DDR3, Easystore shucks or data center decomms (8x3TB was $200).&lt;p&gt;I got 48 vCPUs and 96GB DDR3 for &amp;lt;$300 in 2016 off eBay. It isn&amp;#x27;t the most powerful, but it was cheap.</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>fgonzag</author><text>Explain how you got a 64 core 192 GB RAM 24 TB server or workstation for 2k please</text></item><item><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></item><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>r3trohack3r</author><text>Not OP, but I have an R620 running in my garage I use for self hosting. It has 12 cores (Intel Xeon E5-2665), 96GB of RAM, 10x2.5&amp;quot; drive bays (came empty). The SSDs I use I shuck out of old external USB drives.&lt;p&gt;Together with a full standing rack on wheels, I bought them for $600 cash (plus U-Haul rental to get it home).&lt;p&gt;My trick is craigslist in a city with datacenters (PHX). There are resellers here who buy used hardware from local datacenters and resell them to smaller businesses. I&amp;#x27;ve had it running 24x7 for almost 3 years now and it is still going strong.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.reddit.com&amp;#x2F;r&amp;#x2F;homelab&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.reddit.com&amp;#x2F;r&amp;#x2F;homelab&amp;#x2F;&lt;/a&gt; has some good references for acquiring hardware for a home lab setup.</text></comment>