Skip to content

Receive webhooks behind a firewall without opening ports

Deliver webhook events to localhost or services inside your company’s or customers’ private networks. No VPN, public IP, router port forwarding, or deployment required.

You need Node.js 26.7 or later and a Tubu API key on the publisher machine. Follow the Quick start to get your key. Replace YOUR_API_KEY and choose an available Tubu domain in the examples. The publisher must reach the target service and connect outward to Tubu. Keep it running while access is needed.

Webhook providers cannot reach your private service

Your payment provider or Git service needs a public URL to deliver events. A handler on your laptop or an internal company server is inside a private network. Repeated deployments slow down local testing, while opening incoming ports adds network configuration for company integrations. Tubu connects outward from a machine that can reach your handler and forwards HTTPS requests to it.

Forward HTTPS requests to your local handler

Run your webhook handler on port 3000 with a route at /webhooks, then start:

npx tubu-cli http 3000 --domain my-hooks.tubu.dev --authtoken YOUR_API_KEY

After Tunnel ready, set the provider’s webhook destination to:

https://my-hooks.tubu.dev/webhooks

Keep Tubu running. Requests go to your local handler without opening an inbound port on your router. Keep the provider’s signature verification in your application.

Forward webhooks to an internal company server

For a receiver inside your company’s or a customer’s intranet, run Tubu on an authorized machine that can reach it. Replace this private address with the receiver’s host and port:

npx tubu-cli http http://192.168.1.30:8080 --domain company-hooks.tubu.dev --authtoken YOUR_API_KEY

After Tunnel ready, set the provider’s destination to the handler’s route:

https://company-hooks.tubu.dev/webhooks

The receiver stays on its private IP. No incoming router port is needed. Keep the publisher running while events are expected and verify provider signatures in the receiver.

Send a test event and inspect the receiver logs

Use the provider’s test event control. Expect the event in your handler logs and a successful delivery response in the provider dashboard. For local testing, change the handler and send another event to test your fix.

For a basic transport check, use the domain from your chosen setup and send this unsigned sample:

curl -i https://my-hooks.tubu.dev/webhooks \
  -H 'Content-Type: application/json' \
  --data '{"type":"test"}'

A handler that verifies signatures should reject this sample. If delivery fails, check the public route, signature configuration, and reachability from the publisher machine.

Tubu does not queue events during disconnections or replay them afterward. Use the provider’s retry policy and monitor the receiver for ongoing use. Stop the publisher when access is no longer needed.

Get started with Tubu