ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When you need a stable, secure HTTPS URL for webhooks or mobile callbacks, ngrok offers several binding options. This guide compares temporary HTTP, reserved domains, custom domains, and TCP endpoints, then walks you through setting up a reserved domain with a traffic policy and how to validate it.
Expose an internal webhook receiver with Ngrok using a reserved domain and Traffic Policy. This architecture note covers requirements, minimal design, trust boundaries, operational checks, failure modes, and when a different ingress is needed.
Architecture note on using ngrok's edge-level OAuth traffic policy to gate access to locally hosted services — requirements, minimal design, trust boundaries, operational checks, failure modes, and when to migrate.
The goal is to understand whether a request cancelled by the client or terminated by an upstream timeout increments the volume_threshold and/or the error_percentage_threshold of a ngrok Traffic Policy circuit‑breaker. The documentation does not specify how such requests are classified, leaving uncertainty about whether they are treated as successful volume,
Migration context I am moving an ngrok tunnel definition from the legacy per-tunnel flags (the --oauth option with an email/domain allowlist) to the newer Traffic Policy configuration, where the same control is expressed as an ordered rule with an OAuth action. The goal is to gate a local app behind provider login (e.g., Google) for integration testing, with
ngrok
oauth