<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bitcoin on The Comfy Seat</title><link>https://beanbag.technicalissues.us/tags/bitcoin/</link><description>Recent content in Bitcoin on The Comfy Seat</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 08 Feb 2025 10:30:00 +0100</lastBuildDate><atom:link href="https://beanbag.technicalissues.us/tags/bitcoin/index.xml" rel="self" type="application/rss+xml"/><item><title>Proxying Bitcoin Core and LND with Tailscale and Nginx</title><link>https://beanbag.technicalissues.us/proxying-bitcoin-core-and-lnd-with-tailscale-and-nginx/</link><pubDate>Sat, 08 Feb 2025 10:30:00 +0100</pubDate><guid>https://beanbag.technicalissues.us/proxying-bitcoin-core-and-lnd-with-tailscale-and-nginx/</guid><description>&lt;p&gt;Recently I decided I wanted to run my own Bitcoin and Lightning node and I wanted it to be reachable on the public internet. I didn&amp;rsquo;t, however, want it to actually reside on the server that has the static public IPv4 and IPv6 addresses available. Thus, a reverse proxy was needed. This turned out to be a pretty simple thing to solve for thanks to the &lt;a href="https://nginx.org/en/docs/stream/ngx_stream_proxy_module.html"&gt;Nginx Stream Proxy module&lt;/a&gt; and &lt;a href="https://tailscale.com/linuxunplugged"&gt;Tailscale&lt;/a&gt;. Here&amp;rsquo;s the basic architecture:&lt;/p&gt;</description></item></channel></rss>