Contact Anusoft: contact@anusoft.com. Include your device, OS and app version, capture mode, selected target type, approximate time, and the error you saw. Start with a short description or a redacted screenshot. Do not send private CA keys, passwords, or active tokens.

Choose where capture runs

This device: the iPhone capture VPN uses the app's Packet Tunnel to handle traffic locally. The API client still contacts the server you request. Starting a local VPN is not the same as sending your capture to a developer cloud service.

Selected Mac: choose a trusted discovered Mac to pair and capture there. Pairing transfers the phone's CA certificate and private key so the Mac can inspect authorized HTTPS traffic, and remote mode can send flows and diagnostics to that Mac. Current pairing uses HTTP on the local network. Use a trusted network and do not expose pairing ports to the public internet.

Manual proxy or relay: check the host and port you entered. Traffic sent through that endpoint is visible to or processed by its operator according to the protocols and trust you configured. Use only a destination you control or are authorized to use.

On macOS, the direct download and Mac App Store build have different capabilities. The sandboxed Mac App Store build does not provide CA-based HTTPS interception or system-proxy/keychain management. Check the available controls in your installed build.

Install and remove CA trust carefully

Trust the HTTrail root certificate only on devices you own or are authorized to administer. A profile contains the public certificate and capture/proxy configuration; pairing separately transfers private CA material to your chosen Mac.

  • iOS setup: approve the profile and VPN in iOS Settings when prompted. Certificate trust, where required, is managed in Settings → General → About → Certificate Trust Settings. Profile management is in Settings → General → VPN & Device Management. Names can vary with iOS version.
  • macOS: use the CA install/trust and removal actions in a supported build. Removal from the System keychain may require administrator approval. If needed, review the HTTrail certificate in Keychain Access.
  • When finished: stop capture, disable or restore the proxy/VPN configuration, remove the HTTrail profile or trusted root from each device, and end pairing. Keep any needed redacted exports separately.

Removing trust is different from deleting a capture, and uninstalling the app is not a guarantee that profiles, keychain trust, or system proxy settings are restored. Never email a private CA key for troubleshooting.

Why is traffic missing, opaque, or failing?

Confirm the capture target, active VPN/proxy, host and port, and local-network permission. In remote mode, check both the phone and selected Mac and confirm that the session on the Mac is receiving new records. Check the host's SSL allowlist and whether your build supports HTTPS interception.

Some applications reject an inspection certificate or use certificate pinning. A blind tunnel can preserve a connection without showing its decrypted contents. UDP forwarding does not imply QUIC decryption. An HTTP success status also does not prove an entire app workflow succeeded.

For a report, include the error and approximate timestamp and say whether the issue happens in local mode, remote mode, or both. Share the smallest relevant, redacted diagnostic excerpt. Diagnostics may still reveal hosts, device identifiers, addresses, and timing.

Share HAR and diagnostics safely

Use the export action for a session or selected flows, or copy a request as cURL/code. Body and header exports preserve content and can include secrets. Exporting a HAR without response bodies reduces content but does not remove all sensitive information.

  1. Work on a copy of the export. Review URLs and query strings, Authorization and Cookie/Set-Cookie headers, request bodies, response bodies, and generated commands.
  2. Remove passwords, API keys, bearer/session tokens, cookies, personal data, private hostnames, and identifiers that are unnecessary for the report. Check binary or encoded content as well.
  3. Send only the smallest sample needed. Do not post an unredacted capture or private key in a public issue.
  4. If you already disclosed an active credential, revoke or rotate it through the issuing service. Editing a local copy does not invalidate a credential already shared.

Delete data on each relevant device

Stop active capture, then use the in-app actions to delete selected flows, individual or saved sessions, clear API request history, and clear diagnostics where offered. Each is a separate category; deleting a capture session does not promise to reset collections, environments, rules, or all settings.

Remote mode can leave a saved session on the Mac and data on the phone. Delete each copy where it is stored. Unpairing ends the dedicated proxy but does not erase the Mac's saved session. Delete exported HAR/body/header files and backups separately, and remove trust and profiles using the steps above.

We do not automatically hold your captures and cannot remotely erase files on your devices or in destinations you chose. See the Privacy Policy and Terms of Use.

Contact

Anusoft · contact@anusoft.com
Project on GitHub