Fetch and add-on diagnosis

Stremio says Failed to fetch? Isolate the blocked request.

Failed to fetch can mean an add-on outage, a changed endpoint, or a network security feature blocking the request. One comparison test is more useful than reinstalling everything.

Try these first

The fixes that usually work

  1. Test only a public, unparameterized manifest address. If it also fails in the browser, reachability or browser/network policy is more likely, but the comparison does not completely clear Stremio or the device.
  2. Pause one VPN, DNS filter, or blocking resolver for a single controlled test, then restore it. Do not disable several protections at once.
  3. Try the same authorised title and source on another device on the same network to help separate a device problem from a network path problem.
  4. If the add-on has been retired, follow its official migration guidance or remove it; do not reuse private configured links from unverified sources.

No sign-up needed for any of these. If none of them change anything, the free diagnostic checks the rest of the chain and tells you which stage is actually failing.

Paste your error

Common causes

What may be happening

  • The add-on is temporarily offline or retired
  • A VPN, DNS filter, or router security feature blocked the request
  • The add-on address changed
  • A device-specific app or network problem

A better process

Check the chain in order

  1. Check official public status first
  2. Compare the same account on another device
  3. Compare a trusted network or one security feature at a time
  4. Restore protection and replace retired add-ons only from trusted sources