What changes when a local app gets a public address?
A public ngrok address receives internet traffic and forwards it to the service you chose. The request reaches the actual app behind that address, with the data and routes that app can access. Use a separate fictional test service if you need to rehearse the flow. Keep private services behind approved access controls.
What does Traffic Inspector keep?
By default the inspector retains information about requests, including the route and client IP, and selected header values. Full capture is optional and can store query values, headers and request and response contents, with size limits. Leave full capture off for an ordinary test unless there is a specific reason to collect more.
The inspector and any configured log export are separate. Check both. A replay can send a request back to your app and repeat its effects, so reading an old request is a different action from replaying it.
What should you check before relying on the address?
The Free plan lists one assigned development domain. Check the plan’s traffic allowances, who can access the endpoint and what happens when the test service stops. Inspector retention depends on the plan. Keep a clean description of the test, expected reply and settings you need to reproduce it separately from short-lived capture history.
How can you spot when an address reaches the wrong app?
Draw a route from a fictional outside sender to a disposable “Demo hours” service on your computer. Do the exercise on paper without creating a tunnel.
- Name the one replyThe disposable service would return one made-up opening time. Write which service would provide it.
- Draw the boundaryCross out any path that reaches an admin screen, live data or a different app. Write down the intended audience and whether the test needs a public address at all.
- Decide when to close itIf you later use an approved isolated connection, define when it closes and how you will confirm that no test address remains active.