zrok VS ngrok

zrok - Aims for effortless sharing both publicly and privately. Supports multiple types of resources, including HTTP endpoints and files. Built on OpenZiti (see overlay section below). Apache 2 License. Written in Go.

I'm the lead developer on an open source product called zrok (https://github.com/openziti/zrok). zrok is a peer-to-peer sharing tool for network and file-based resources, similar to tools like ngrok.

fwiw, its back up. stars for zrok and ziti (i.e., the parent repo) are super appreciated!

Tailscale makes outbound connections so it circumvents the need for IPv6 with things like CGNAT.

OP, why not use an open source equivalent to Tailscale Funnel? For example, I work on the OpenZiti project and we created zrok.io which is fully open source alternative - https://github.com/openziti/zrok.

Here's a Dockerfile from the zrok repo you might find helpful: https://github.com/openziti/zrok/blob/main/docker/images/zrok/Dockerfile

I've started with a RPi 1 Model B rev 2 (armv61) running dietpi, which should be fine for Pihole but I'm also thinking of using it to run software to control remote access to my server, which could be Tailscale or Wireguard but zrok looks interesting. Unfortunately that doesn't have a armv61 version, only armv7 Releases · openziti/zrok (github.com) so I couldn't run it on this RPi.

I work on the open source OpenZiti project. We recently released zrok (https://zrok.io/), we have Local Debugging Interface in the backlog - https://github.com/openziti/zrok/issues/73.

Many good reverse proxy solutions currently exist on the market such as ngrok and Cloudflare tunnels. They give one the ability to reliably run a tunnel and ensure it does not go down. They also offer the ability to securely access their links using whitelisted IP addresses or by using HTTP Basic Authentication.

These is a very common problem. Luckily, it's been solved already. My go-to tool for this was ngrok or localtunnel. Both of these tools are great, but they didn't fit my needs perfectly.

Ensure your app works as expected and provides a good user experience by thoroughly testing and debugging. Utilize tools like Chrome DevTools or Firefox Developer Tools to inspect and modify your app’s code, network, and storage. Employ tools like ngrok or localtunnel to expose your local development server to the internet, enabling testing on various devices and browsers.

ngrok

Tunnels (CloudFlare vs. Ngrok)

We need to make our WhatsApp API accessible on the internet so the trigger.dev cloud service can connect to it. We can do that by running ngrok in a separate terminal.

This means that Cronitor must have an endpoint that it can reach. Normally, we can't do that when developing on a personal machine. For this tutorial, however, we can use ngrok to establish a tunnel to our local Django application for testing purposes.

There are so many weird suggestions in the comments. I'm surprised nobody has mentioned ngrok https://ngrok.com/ (there are many competing alternatives as well). It makes exposing local service over HTTPS trivial. It's been used heavily in most of my engineering orgs.

Ngrok: This provides about 2hours on the free account but requires account registration and adding your authtoken, and starting it is as simple as running ngrok http 8080