<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: overnight.technology</title>
    <description>The latest articles on DEV Community by overnight.technology (@overnighttechnology).</description>
    <link>https://dev.to/overnighttechnology</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4253436%2Fa013f454-6b38-4885-ad5e-259098d80ed4.png</url>
      <title>DEV Community: overnight.technology</title>
      <link>https://dev.to/overnighttechnology</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/overnighttechnology"/>
    <language>en</language>
    <item>
      <title>Testing Stripe webhooks on localhost without leaving the URL open to everyone</title>
      <dc:creator>overnight.technology</dc:creator>
      <pubDate>Thu, 19 Nov 2026 11:05:50 +0000</pubDate>
      <link>https://dev.to/overnighttechnology/testing-stripe-webhooks-on-localhost-without-leaving-the-url-open-to-everyone-36g</link>
      <guid>https://dev.to/overnighttechnology/testing-stripe-webhooks-on-localhost-without-leaving-the-url-open-to-everyone-36g</guid>
      <description>&lt;p&gt;Most localhost tunnels hand you a public URL that anyone can hit. That's fine for a quick demo, but when you're testing Stripe, GitHub or Slack webhooks against your laptop, an open URL means random scanners reach your dev server too.&lt;/p&gt;

&lt;p&gt;Here's the setup we use with overnight.technology Tunnels, where every link is locked by default.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Install the client
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -fsSL https://app.overnight.technology/install.sh &lt;span class="o"&gt;|&lt;/span&gt; bash
&lt;span class="kd"&gt;export&lt;/span&gt; &lt;span class="nv"&gt;PATH&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"$PATH:$HOME/.local/bin"&lt;/span&gt;
ot login --token YOUR_API_TOKEN
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It installs the open-source frp client plus a small &lt;code&gt;ot&lt;/code&gt; script into &lt;code&gt;~/.local/bin&lt;/code&gt;. The client keeps an outbound connection, so you open no ports on your router.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Start a tunnel with your own secret
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;ot http 4242 --slug hooks --secret a-long-random-string
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Your app on port 4242 is now reachable at &lt;code&gt;https://hooks.overnight.technology&lt;/code&gt;, but only with the secret (header &lt;code&gt;X-OT-Tunnel&lt;/code&gt; or &lt;code&gt;?ot=&lt;/code&gt;). Everyone else gets a 401 before a single request reaches your machine.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Register the webhook
&lt;/h2&gt;

&lt;p&gt;In the Stripe dashboard, add the endpoint:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;https://hooks.overnight.technology/webhook?ot=a-long-random-string
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Keep verifying Stripe's signature in your app as usual; the tunnel secret is an extra gate in front, not a replacement.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Watch deliveries
&lt;/h2&gt;

&lt;p&gt;Each tunnel keeps a request log of the last 200 requests (time, method, path, status), so you can see whether Stripe got a 200 or your handler threw.&lt;/p&gt;

&lt;h2&gt;
  
  
  Extra locks
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;--basic user:pass&lt;/code&gt; for client demos (the browser asks for a password)&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;--allow 203.0.113.7,10.0.0.0/8&lt;/code&gt; to restrict to your office IP, on top of the token&lt;/li&gt;
&lt;li&gt;The slug belongs to your account, so the URL stays the same after restarts&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Limits, honestly
&lt;/h2&gt;

&lt;p&gt;Tunnels carry HTTP(S) only today: no raw TCP/UDP, no WebSockets or streaming responses, no custom domains on tunnels yet, no Windows installer. Plans start at €9/month, and access is on request for now.&lt;/p&gt;

&lt;p&gt;Docs: &lt;a href="https://overnight.technology/docs/tunnels/" rel="noopener noreferrer"&gt;https://overnight.technology/docs/tunnels/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>stripe</category>
      <category>devops</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
