Jackett/Jackett · warning · Exception

Could not find releases from this URL

Error message

Could not find releases from this URL

What it means

Thrown in SubsPlease's ApplyConfiguration during the setup test. SubsPlease is a cardcast-style RSS/JSON source, so configuration simply loads values and runs PerformQuery; if it returns no releases the configuration is rejected because a live SubsPlease feed should always have content. This guards against a broken feed URL, an API outage, or a parser that returned nothing.

Source

Thrown at src/Jackett.Common/Indexers/Definitions/SubsPlease.cs:84

        }

        public override IIndexerRequestGenerator GetRequestGenerator()
        {
            return new SubsPleaseRequestGenerator(SiteLink);
        }

        public override IParseIndexerResponse GetParser()
        {
            return new SubsPleaseParser(SiteLink);
        }

        public override async Task<IndexerConfigurationStatus> ApplyConfiguration(JToken configJson)
        {
            LoadValuesFromJson(configJson);
            var releases = await PerformQuery(new TorznabQuery());

            await ConfigureIfOK(string.Empty, releases.Any(), () =>
                throw new Exception("Could not find releases from this URL"));

            return IndexerConfigurationStatus.Completed;
        }

        protected override async Task<IEnumerable<ReleaseInfo>> PerformQuery(TorznabQuery query)
        {
            var releases = await base.PerformQuery(query);

            if (query.SearchTerm.IsNotNullOrWhiteSpace())
            {
                releases = releases.Where(release => query.MatchQueryStringAND(release.Title));

                // If we detected a resolution in the search terms earlier, filter by it
                var resolutionMatch = Regex.Match(query.SearchTerm, @"\d{3,4}p", RegexOptions.IgnoreCase);

                if (resolutionMatch.Success)
                {
                    releases = releases.Where(release => release.Title.IndexOf(resolutionMatch.Value, StringComparison.OrdinalIgnoreCase) >= 0);

View on GitHub (pinned to adff194147)

Solutions

  1. Retry the configuration test shortly in case the feed returned nothing transiently.
  2. Open the SubsPlease feed/site in a browser to confirm it is up.
  3. Update Jackett so the parser matches the current SubsPlease feed format.
  4. Check network/proxy settings so Jackett can reach the feed host.
Defensive patterns

Strategy: retry

Try / catch

// SubsPlease config is just a connectivity/parse test; one retry covers transient empties.
int n = 0;
while (true)
{
    try { return await indexer.ApplyConfiguration(configJson); }
    catch (Exception ex) when (ex.Message.Contains("Could not find releases") && ++n < 2)
    { logger.Warn("SubsPlease returned nothing; retrying."); continue; }
}

Prevention

When it happens

Trigger: PerformQuery(new TorznabQuery()) returns no releases. Causes: SubsPlease API/feed temporarily down, network/DNS issue reaching the feed, parser mismatch after a format change, or (rarely) a genuinely empty moment.

Common situations: First-time setup while the SubsPlease API is having an outage; Jackett version predates a feed format change; network egress blocked.

Related errors

AI-assisted analysis of Jackett/Jackett@adff194147 (2026-08-13). Data as JSON: /api/errors/aa0fdf1fcc2e1f94. Report an issue: GitHub.