Support

Get in touch

Email support@pterobit.com. We read everything and usually reply within two business days.

What helps us help you faster:

• Your iOS version and device.
• The rule as you entered it — domain, matching mode, and destination.
• What the Recent Lookups list shows while the tunnel is on.
• What you expected to happen, and what happened instead.

Setting up a redirect

1. Add a rule: the domain you want to capture, and the destination it should resolve to. On your own network you can pick a discovered server by name; otherwise enter an IP address or a hostname.
2. Flip the switch. iOS asks once to allow the VPN configuration.
3. Make the request — from a browser, or from whichever app you are testing. Remember that DNS cannot select a port; for a dev server on port 3000, open http://mysite.com:3000.

Requires iOS 17 or later.

Troubleshooting

Nothing is redirected

Check the Recent Lookups list while the tunnel is on — it shows every query that reached the extension. If it stays empty, the lookups are not matching your rule domain; check the domain and the matching mode. If entries appear marked redirected but the page still does not load, DNS is working and the problem is at the destination.

The page does not load, or the connection is refused

Most dev servers listen on 127.0.0.1 by default, which refuses connections from your phone. Bind to all interfaces instead:

Also check the machine's firewall — System Settings › Network › Firewall on macOS, ufw or firewalld on Linux, Windows Defender Firewall on Windows. The Check Reachability button in the rule editor tries a TCP connection to ports 443, 80, 8080 and 3000, which tells a refused connection apart from DNS that is not working.

It worked yesterday, not today

The target machine's DHCP lease probably changed its IP address. Give it a static or reserved address in your router, or update the rule.

The production site still loads

iOS and the app making the request both cache DNS aggressively. Answers carry a short TTL, but a hard reload — or closing the tab, or relaunching the app — may be needed.

HTTPS fails with a certificate error

DNS only decides where a connection goes; it cannot do anything about the certificate. https://app.mysite.com fails the TLS check unless the server presents a certificate valid for that hostname. Either use http:// for local testing, or generate a certificate with mkcert and install its root CA on the phone, trusting it under Settings › General › About › Certificate Trust Settings.

Editing a rule interrupts the connection

Expected. Changing which domains are captured requires reapplying the tunnel's network settings, so the app restarts the tunnel when rules change.

A remote destination returns the wrong site

Requests still carry the original domain in the Host header, so the server at the other end has to be configured to answer for it.

Subscriptions and purchases

Purchases are handled by the App Store, so the controls for them live in iOS rather than in the app.

• Manage or cancel — Settings › your name › Subscriptions, or apps.apple.com/account/subscriptions. Cancelling stops the next renewal; access continues to the end of the period you have paid for.
• Restore a purchase — on a new device, or after reinstalling, use Restore Purchases on the app's paywall while signed in with the same Apple Account.
• Refunds — these are Apple's to issue, at reportaproblem.apple.com. We cannot process one for you, but tell us what went wrong and we will try to fix it.
• Buying lifetime while subscribed — cancel the subscription first. The app checks that auto-renewal is off before it will sell you the lifetime purchase, so you are not paying twice for the same thing.

If a subscription lapses, nothing is deleted. Rules beyond the free tier stay in the list exactly as written and are marked paused, and they all turn back on if you subscribe again.

Privacy

The app collects nothing and sends nothing. The privacy policy explains exactly what the VPN profile does and does not do.