Tunnelmole – give your local servers a public URL

Some time ago I created an instruction on setting up a DIY ngrok alternative with just Caddy and SSH [1]. Works really well for me ever since.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;ziolko&#x2F;tunnel">https:&#x2F;&#x2F;github.com&#x2F;ziolko&#x2F;tunnel</a><p>Edit: The nice thing about this is that it allows you to proxy to any any target port including e.g. standard email ports. This was very helpful while I was working locally on a custom email server.

Nice work, these types of tools are invaluable and there are well-supported paid options, but not that many OSS projects. There is another project called fast reverse proxy (frp) that has been around for a while, it&#x27;s open source, however some users are concerned with the country of origin. Never the less, it&#x27;s probably more mature and well-tested at this point.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;fatedier&#x2F;frp">https:&#x2F;&#x2F;github.com&#x2F;fatedier&#x2F;frp</a>

I&#x27;m not a domain expert in networking. Can someone explain to me the difference between a tunnel and a reverse proxy ?<p>Also, for local setup, this still require to have a port mapping at router level, I assume?

Looks very interesting (every now and then I wonder about good self-hostable ngrok alternatives), but the &quot;curl x | sudo bash&quot; pattern for installation is really putting me off this one.

Guide to similar services in this space:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;anderspitman&#x2F;awesome-tunneling">https:&#x2F;&#x2F;github.com&#x2F;anderspitman&#x2F;awesome-tunneling</a>

Congrats on the launch!<p>There are quite a few of these out there. ngrok (very popular) and Svix Play (ours) come to mind, but I&#x27;ve also seen a few Show HNs in the last few months. What&#x27;s your biggest differentiator to existing solutions? Not saying that one is needed (hacking for the sake of hacking is great), just wondering if there&#x27;s something we need to add to ours. :P

For anyone looking for a simple easy to use alternative, try <a href="https:&#x2F;&#x2F;pinggy.io" rel="nofollow">https:&#x2F;&#x2F;pinggy.io</a><p>Gives you tunnels with one command, no need to even download anything.<p>Full disclosure: I have created <a href="https:&#x2F;&#x2F;pinggy.io" rel="nofollow">https:&#x2F;&#x2F;pinggy.io</a> :)

I recently started using Tailscale funnel for the same purpose. Works well! <a href="https:&#x2F;&#x2F;tailscale.com&#x2F;blog&#x2F;introducing-tailscale-funnel&#x2F;" rel="nofollow">https:&#x2F;&#x2F;tailscale.com&#x2F;blog&#x2F;introducing-tailscale-funnel&#x2F;</a>

I did that with two Caddy servers (one on my host and another locally) and Tailscale (ssh tunnel at first): <a href="https:&#x2F;&#x2F;solovyov.net&#x2F;blog&#x2F;2022&#x2F;ngrok-for-the-wicked&#x2F;" rel="nofollow">https:&#x2F;&#x2F;solovyov.net&#x2F;blog&#x2F;2022&#x2F;ngrok-for-the-wicked&#x2F;</a>

What is the benefits of this vs DynDNS?

I am using my own solution. <a href="https:&#x2F;&#x2F;github.com&#x2F;Eun&#x2F;frwd">https:&#x2F;&#x2F;github.com&#x2F;Eun&#x2F;frwd</a> Costs me nothing when using the free tier of aws&#x2F;oracle you name it...

seems like a great tool for exposing webhooks to the internet. it would be great to limit to a specific uri. for example<p><pre><code> tmole 80 &quot;^&#x2F;webhooks&#x2F;?$&quot;</code></pre>

Love these, but they get abused very quickly. Good luck to you.

Hehe, used to work for ZEIT. Always tickles me when things like Now pop up. I wish it still existed in its original form sometimes.