ZeroTrace Proxy
Settings, Storage, and Troubleshooting
Window settings, storage paths, Discord settings, task state, runtime issues, and common fixes.
The Settings page exposes local app behavior and storage paths.
Window Settings
| Setting | Meaning |
|---|---|
| Always on top | Keep the app above other windows. |
| Content protection | Ask the desktop shell to protect window content. |
| Disable resize | Keep the app window fixed. |
| Start state | Choose normal, maximised, fullscreen, or minimised startup behavior. |
Storage Paths
Settings shows paths for:
- base app data directory
- settings file
- task history file
- core notifications file
- chain definitions and policies
- chain runtimes
- rotation definitions and policies
- rotation runtimes
- proxy pools directory and index
- task profiles directory
- task runs directory
- WebView user data path
Discord Webhook
The webhook URL must:
- be a valid URL
- use HTTPS
- have a host containing
discord
If files are included, ZeroTrace Proxy sends a multipart webhook payload.
Export and Discord Limits
| Item | Limit or behavior |
|---|---|
| Discord username | Defaults to ZeroTrace. |
| Content | Truncated to 1900 characters. |
| Embeds | Up to 10. |
| Embed title | 256 characters. |
| Embed description | 4096 characters. |
| Embed fields | 25 fields. |
| Embed field name/value | 256 characters for names, 1024 characters for values. |
| Files | Up to 10 files. |
| File content | Truncated at 7 MiB with a [truncated] marker. |
| Text exports | .txt proxy list saving through the Files service. |
| Export names | Task name is slugified into the export filename. |
Startup and Task State Details
| Detail | Meaning |
|---|---|
| Queued tasks | Each core task type runs up to two active tasks. |
| Scheduled tasks | Wait until their parsed local due timestamp. |
| Restarted app | Running, queued, and scheduled snapshots normalize to stopped so stale work does not look active. |
| Queue order | Oldest queued tasks start first when slots open. |
| Progress snapshots | Task progress persists during runs. |
Common Issues
| Issue | Fix |
|---|---|
| Task stays queued | Another run of the same tool may be active. Each task type has a two-run active limit. |
| Scheduled task did not start yet | Confirm the scheduled time and local clock. |
| Extractor returns zero proxies | Try a specific parser profile, HTML selector, or JSON path. |
| Checker marks many proxies dead | Increase timeout, verify expected status codes, and test with a smaller sample. |
| Benchmark looks unstable | Reduce concurrency, increase rounds only after source quality improves. |
| Leak test cannot classify | Confirm the target returns inspectable JSON with headers and origin. |
| Runtime bound a different port | Requested port was in use; copy the bound endpoint from the runtime snapshot. |
| Rotation has no available proxies | Check cooling/quarantine counts, source pool quality, and health errors. |
| Discord export fails | Recheck webhook URL, network access, and payload size. |
Safe Support Bundle
When asking for help, share:
- tool name
- sanitized task name
- result status counts
- relevant error message
- sanitized proxy format example
- screenshot with webhook URLs and proxy credentials hidden
Do not share:
- Discord webhook URLs
- real proxy credentials
- private source URLs
- app data folders
If a screenshot contains a webhook URL or proxy credentials, retake it with those values hidden.