Skip to main content

​
Check Your Versions First

Before troubleshooting, confirm what you’re running.
In AIOStreams → About → Get Started — the loaded template name and version are shown at the top of the template card.Alternatively, check the template JSON directly: open the raw URL in a browser and look for "version" inside the "metadata" object.
In AIOStreams → About — the AIOStreams version is shown in the footer. Core Builds templates require v2.30+.
Re-import the same URL — AIOStreams merges the new version over your existing config and preserves your API keys. Check for an in-app update notification first (AIOStreams will prompt you automatically when a new version is available).

​
Import Errors

This is a regex whitelist error. Public AIOStreams hosts validate inline pattern strings against an allowlist before saving. The pattern content must match the allowlist exactly — even a single character difference causes rejection.Fix: re-import the latest template. As of v2.9.0, all pattern strings are synced to the host allowlists. The most common cause is importing an older template that predates the v2.8.9 / v2.9.0 sync.If you’re still seeing this after re-importing v2.9.0+, paste the exact error text in the community thread — it may indicate the allowlist has been updated again.
A URL inside the template (regex source, expression URL, or logo URL) has been blocked by your host.Most common cause: an old template referencing a raw GitHub URL that the host doesn’t whitelist.Fix: re-import the current template. All URL references are up to date from v2.9.0 onwards.If the error persists on a self-hosted instance, set REGEX_FILTER_ACCESS=all in your AIOStreams environment.
AIOStreams updated the metadata.inputs schema — the field previously named key was renamed to id, and label was renamed to name. Labs templates built before v2.9.0 used the old field names.Fix: re-import the Labs template. The schema fix is live from the current main branch. If errors persist, paste the full error list in the community thread.
Warnings like interpolation {{inputs.exitThreshold}} references undeclared input appear when the template uses directive interpolation and the input IDs don’t match what’s declared in metadata.inputs. This is a Labs-only issue — stable templates don’t use template directives.Re-import the latest Labs template. If the warnings continue, they are non-fatal — the template will still function, but the configurable inputs at import may not work as intended.

​
Results Issues

Check first:
  • Is the title in TorBox’s cache? Search at torbox.app
  • Are your API keys entered? TorBox key in Services, TMDB in Settings
  • Are your scrapers enabled? Open AIOStreams → Add-ons — from v2.9.4, MediaFusion and HdHub are on by default; on older imports they may be toggled off
If you’re on a Flash or Speed template: These templates exit as soon as they find cached results. If TorBox doesn’t have the title cached, Flash returns nothing. Switch to Core Nexus Essential for full coverage with uncached fallback.Try the Lite variant: The standard template runs quality-gate ESEs (low bitrate, low seeders, bad encodes). Lite removes those gates — hard kills stay but quality filters are gone. If Lite returns results, one of the quality gates is filtering your content.
Fixed in v2.9.4. Earlier versions of the base Stream template had no 720p fallback tier — if a title had no 1080p source indexed, the template returned zero results instead of falling back to 720p WEB-DL or WEBRip. Re-import the latest Stream template. The Lite and Fire Stick variants already had this fallback; it now applies to the base template too.
Fixed in v2.8.3. All 1080p templates now have a hard resolution kill ESE as their first filter. Re-import your template.
Fixed in v2.8.4. Re-import your template. The Boost Cached Usenet PSE now catches any cached NZBs that fall outside the quality-window PSEs and ensures they rank above uncached streams.
Fixed in v2.8.3. seadexBestOnly: true was dropping all non-SeaDex streams on several non-Anime templates. Re-import to pick up the fix.
Fixed in v2.7.5. The newznab timeout was 3000ms — too short for TorBox Usenet. Updated to 10,000ms. Additionally searchMode: auto and checkOwned: true are now set. Re-import your template.
Most common causes:
  • Debrid link timeout (Nuvio / AIOStreams v2.24.0+) — If you see a visible Playback Error, the debrid link resolver timed out. Re-import the v2.9.0+ template — the stremthruTorz/stremthruStore timeout was raised to 5000ms to cover congested periods. If errors persist, check TorBox’s status page for outages, or try a different stream from the list.
  • Codec not supported on your device — check the stream’s codec in the formatter display. If it’s AV1 on a device without hardware AV1 decode (Fire Stick 4K, older Samsung Tizen), the stream will buffer or fail. Switch to a device-specific template (Samsung TV, Fire Stick) which hard-exclude unsupported codecs.
  • DV-only stream on a non-DV device — the Samsung templates have a DV-Only Kill ESE enabled by default. If you’re on a generic template, enable the DV-Only Kill ESE manually in AIOStreams.
  • Bitrate too high — very high-bitrate REMUX streams can stall on slower connections or budget hardware. Try the B-tier or lower result in the list.

​
Device Issues

The Samsung TV templates exclude lossless audio (TrueHD, DTS-HD MA, DTS:X, FLAC) by default — these formats require HDMI ARC/eARC passthrough to a compatible receiver. If you have a compatible receiver and want lossless audio, remove those tags from excludedAudioTags in the AIOStreams settings after importing.If audio is stuttering on tracks that should work, re-import the latest Samsung TV template.
The DV-Only Kill ESE is enabled by default on Samsung templates. If you’re still seeing DV streams:
  • Re-import the latest Samsung TV template
  • Check you haven’t disabled the No DV-Only ESE in the AIOStreams expression editor
Use the Stream (Fire Stick) template. It hard-excludes AV1 (no hardware decoder on most Fire Stick models), HDR10+, Dolby Vision, and lossless audio. If you’re on a generic Stream template, these formats may be served and cause transcoding or failure.
The Apple TV 4K Nightly template prioritises DV Profile 5/8 — the profiles natively supported by the A15 chip. If DV isn’t playing, confirm you’re using Infuse (native DV support) rather than a player that doesn’t decode DV.AV1 is hard-excluded on the Apple TV template — the A15 chip has no hardware AV1 decoder.

​
FAQ

Yes for all TorBox templates. AllDebrid templates require an AllDebrid account. EasyNews templates require an EasyNews subscription. The Speed EasyNews template is the only one that works without TorBox.
Both work with Core Builds v2.9.0+. The main difference is the regex whitelist — fortheweak is stricter. As of v2.9.0, all templates are verified against both allowlists.If you’re self-hosting, no whitelist applies — all templates work as-is.
Standard runs 24 ESEs including quality gates (low bitrate, low seeders, upscaled 4K, bad Bluray encodes). Lite runs 12 — hard kills only (CAM, YouTube, 3D, bad NZBs). More results come through on Lite, but without quality filtering some bad encodes may appear.Use Lite when: your library is thin, you’re on a shared host, or you’re debugging why a title returns no results on Standard.
The stable Samsung TV 4K (Device folder) is general-purpose — targets all 2018–2022 Samsung Tizen TVs without DV support. It uses standard Core Builds PSEs.The Nightly Samsung RU7100 4K is model-specific — tuned for the RU7100 (UA65RU7100W) and compatible TVs. It runs the full APEX IQR Tukey fence PSE stack and more aggressive filtering. Use it if you specifically have an RU7100 or want to test the more aggressive expression set.
Labs templates test AIOStreams features that aren’t fully stabilised yet — template directives (__if/__value interpolation), dynamicAddonFetching conditions, and per-scraper toggles at import time. These features depend on AIOStreams schema versions that change without notice, which is why Labs can break between AIOStreams updates.Labs import errors are expected — reporting them helps identify schema changes.
Yes. As of v2.9.0, all inline patterns are verified against both elfhosted and fortheweak allowlists. Import the template, enter your API keys, and save.
Optional but recommended. Without it, title matching falls back to AIOStreams defaults, which is less accurate for foreign titles and anime.
Yes — open a PR to Community-Templates/ in the repository. Include a README with what your template does and what service/plan it requires.
SeaDex is an anime release quality database. When seadexBestOnly: true, only streams flagged as SeaDex best releases are shown for anime queries. This was incorrectly enabled on several non-Anime templates and fixed in v2.8.3.
AIOStreams enforces a hard 3,000 character limit per expression. The Final Limit ESE is currently at 2,953 characters — 47 characters of headroom. Adding anything risks hitting the limit and breaking import.