Support for TraceWall
Help for protection setup, firewall modes, allowlist and blocklist rules, host switching, local logs, import and export, and App Store review testing.
Contact
For support, bug reports, App Store review questions, or feature requests, contact Moryxo support.
Email: [email protected]
Website: https://moryxo.com/contact
When reporting an issue, include your iPhone or iPad model, iOS version, TraceWall version, protection state, firewall mode, the rule or host mapping you tested, and a short description of what happened.
What the app is for
TraceWall is a local web firewall and developer host switcher for iPhone and iPad.
It can create domain, IP, and port rules, run in Blocklist or Allowlist mode, show local allow/block logs, import and export settings, and map a domain to a selected IP address for staging or migration testing.
No account or demo login is required.
Common questions
Why does TraceWall install a VPN configuration?
TraceWall uses the iOS VPN configuration system so supported HTTP and HTTPS web traffic can be routed through a local on-device proxy. The tunnel is used for local web traffic control and logging. TraceWall is not a remote VPN service and does not provide anonymous browsing infrastructure.
What is the difference between Blocklist and Allowlist mode?
Blocklist mode allows supported web traffic by default and blocks only the rules you add to the blocked list.
Allowlist mode blocks supported web traffic by default and allows only domains, IP addresses, or ports that you explicitly add to the allowed list.
Does TraceWall decrypt HTTPS websites?
No. TraceWall does not decrypt HTTPS page content, form fields, passwords, messages, files, or full page bodies. It can log traffic metadata needed for allow/block decisions, such as destination domains, IP addresses when available, ports, timestamps, and rule decisions.
What does the Host Switcher do?
The Host Switcher maps a user-entered domain to a user-entered IP address. This is useful for staging servers, sandbox deployments, DNS migration tests, CDN origin checks, and verifying a new server before public DNS is changed. The target server must be configured to answer for the requested hostname.