Access applications and APIs inside customer networks
Connect to applications and APIs inside your customers’ private networks for support, integration, and debugging. No VPN, public IP, inbound firewall rules, or port forwarding 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.
The customer service is inside their intranet
Your team needs an internal API or application, but only machines inside the customer network can reach it. VPN setup, public IP allocation, inbound firewall changes, and port forwarding can delay support and integration.
Run one Tubu publisher inside the customer network
On an authorized machine inside the customer network, verify that http://192.168.1.20:8080 is reachable. Save this configuration as tubu.yml, replacing the address, domain, and shared secret:
tunnels:
- type: http
domain: customer-api.tubu.dev
target: http://192.168.1.20:8080
secret: REPLACE_WITH_A_RANDOM_SECRETnpx tubu-cli --config tubu.yml --authtoken YOUR_API_KEYThe publisher connects outward to Tubu. You publish this service, rather than a route to the whole customer network. Add more tunnel entries to reach additional internal services from the same process.
Call the internal API from your team’s network
After Tunnel ready, call a route that exists in the customer application:
curl --fail https://customer-api.tubu.dev/health \
-H 'X-Tubu-Auth: REPLACE_WITH_A_RANDOM_SECRET'Expect the internal service’s response. Without the secret, expect 401. Tubu removes the shared secret header before forwarding and preserves the application’s Authorization header.
For browser applications, retain their own login. Normal browser navigation cannot supply this custom header. See HTTP tunnel protection for details.
If Tubu returns 502, check reachability from the publisher machine. Applications that use internal redirects or URLs may need their public base URL configured. Stop the publisher to close access.