Relay support
Help with Relay.
A place for questions, connection problems and ideas for what comes next. Start with the answers below, or get in touch.
A useful first message
Help us reproduce it.
A small example is often the quickest way to find what happened.
- Tell us your setup. Include the Relay version and build from Settings, your iPhone or iPad model, and the iOS or iPadOS version.
- Describe the difference. What did you expect, what happened, and which steps reproduce it? Mention the selected protocol, DNS resolver, connection target or proxy when relevant.
- Share only what is needed. If useful, attach a redacted report from the response or inspection screen. Review its contents first and use a synthetic example where possible.
Redacted does not mean anonymous
Reports can still include hostnames, paths, custom headers, DNS records and certificate details. Live headers, copied values and exported bodies can include complete credentials or private content.
Common questions
Get back to your request.
A request or local-network connection fails
Check the URL, port, network connection and any selected target or proxy. For a local server, check Relay’s Local Network permission in iOS or iPadOS Settings and make sure the server is reachable from the device.
A strict HTTP version can fail if the server or network does not support it. Try Automatic to compare. Keep TLS verification on while investigating; a certificate error can indicate a real identity or trust problem.
DNS works, but the request or certificate check does not
A DNS answer establishes a name-to-record result, not that a service is listening or that its certificate is trusted. DNS inspection uses the resolver you select. A certificate connection target changes where the TLS probe connects while keeping the original hostname for identity checks.
A missing MX record says nothing about whether a website is available. System DNS may not distinguish a missing name from a missing record type.
My headers or history contain redacted values
A fresh response shows complete live header values. Saved history removes known credentials and query values; keeping a response body does not restore those request values. Open the saved request or restore the missing values before sending again.
Shared reports sanitize separately from the live view. Copying a live header or exporting a body preserves its content, so check what you are sharing.
Relay does not appear in the share sheet, or an import is missing
Open Relay once before sharing into it. In the source app, share a single HTTP URL or cURL command, choose Relay, then choose Add to Relay. Reopen Relay to review the import before applying it. Applying never sends the request automatically.
If Relay is not listed, check the share sheet’s More or Edit actions. The source app must offer compatible text or a URL. Shared requests in Settings lets you check the inbox and see any import error.
Restore, manage or cancel Relay Pro
Use Restore purchases in Relay’s Pro screen while signed into the Apple Account that made the purchase. Manage subscription opens Apple’s subscription controls. Deleting Relay does not cancel a subscription.
When plans are unavailable, check your connection and try again. Your saved work remains editable if Pro ends; executing assertions and DNS routing rules requires Pro.
Apple’s subscription cancellation guide · Request a refund from Apple
What happens to my saved requests and response files?
Relay stores its workspace on your device with encryption. It does not provide cloud sync or workspace recovery. Persistent workspace and response files are excluded from backup, so a lost device or deleted app can mean lost work.
History omits response bodies by default and keeps up to 100 runs. Keep response retains a body until its history item is deleted, cleared or trimmed at that limit. Clear temporary response files in Settings to remove disposable cached bodies. Avoid deleting the app as a first troubleshooting step.
What does a private session do?
Private-session changes are not saved to the normal workspace. Leaving the session restores the previous workspace. Large responses may still use encrypted temporary files, and the destinations you contact still receive your traffic.
Private mode does not make requests anonymous. Anything you explicitly copy or export leaves Relay under your control.