Troubleshooting
Fixes for the most common snags — activation, checks that return nothing, a chain or rotator that will not carry traffic, and AI, MCP, or Discord connections.
Most snags fall into a few buckets. Work through the relevant one below.
The tools are locked or the app says my license is not valid
Proxy is a licensed product and needs to be activated before its tools unlock. Check that you have activated it, and see the Licensing page for what each license state means. If the app reports that the licensing service could not be reached, wait a moment and try again; if it says the license belongs to a different machine, it was activated elsewhere.
A check returns nothing, or every proxy comes back dead
Checking a proxy means using it, so a working connection is required. If a whole list comes back dead, confirm the list actually contains proxies (run it through Parse first) and that your own connection is up. A single proxy that returns nothing is usually just dead or too slow — that is the check doing its job.
Extract's Cloud sources are unavailable
The curated Cloud sources come with your license. If they are missing, confirm the app is activated; see Licensing. Other Extract sources — text, HTML, JSON, and files — do not depend on the license.
I started a chain or rotator but my tool will not connect to it
Point your tool at the exact local address the engine shows in its runtime snapshot — if the port you asked for was taken, the engine bound a different one and reports it there. If the chain's policy has require auth turned on, your tool must present the username and password set in the policy. See Policies & live traffic.
A running chain keeps failing or switching routes
That is health-checking at work. Open the chain's policy and check its probe URL, timeouts, and failure threshold — a probe URL that only works from your normal address, or timeouts set too tight, will make a healthy chain look broken. If the primary route is genuinely down, the engine falls back when fallback is enabled and a fallback chain is set. See Chain Engine and Policies & live traffic.
The AI assistant will not respond
Check which model the assistant is set to use in Settings. A local model has to be running on your computer for the assistant to reach it; a hosted model needs its connection configured. The assistant shows the tools it runs, so if it stalls mid-task, the visible call history tells you where. See AI Assistant.
Another tool cannot connect to Proxy over MCP
The MCP server is off until you turn it on. Confirm it is enabled in Settings, then point your other tool at it. If it was working and stopped, check that the server is still enabled.
Reports are not reaching my Discord channel
Discord delivery is optional and off until you configure it. Confirm you have set up a destination channel in Settings and chosen to send the report. See Discord reports.