Jackett/Jackett · error · Exception

Testing returned no results!

Error message

Testing returned no results!

What it means

During configuration testing NebulanceAPI runs an empty TorznabQuery against PerformQuery. If the query returns zero releases the indexer refuses to mark itself configured, guarding against a 'successful' setup that would silently return nothing to the user.

Source

Thrown at src/Jackett.Common/Indexers/Definitions/NebulanceAPI.cs:125

        public override async Task<IndexerConfigurationStatus> ApplyConfiguration(JToken configJson)
        {
            LoadValuesFromJson(configJson);

            IsConfigured = false;
            var apiKey = configData.Key;
            if (apiKey.Value.Length != KeyLength)
            {
                throw new Exception($"Invalid API Key configured: expected length: {KeyLength}, got {apiKey.Value.Length}");
            }

            try
            {
                var results = await PerformQuery(new TorznabQuery());

                if (!results.Any())
                {
                    throw new Exception("Testing returned no results!");
                }

                IsConfigured = true;
                SaveConfig();
            }
            catch (Exception e)
            {
                throw new ExceptionWithConfigData(e.Message, configData);
            }

            return IndexerConfigurationStatus.Completed;
        }
    }

    public class NebulanceAPIRequestGenerator : IIndexerRequestGenerator
    {
        private readonly TorznabCapabilities _torznabCaps;
        private readonly ConfigurationDataAPIKey _configData;

View on GitHub (pinned to adff194147)

Solutions

  1. Retry the test shortly - an empty default feed is often transient.
  2. Verify the account is in good standing and actually has browse access on the Nebulance site.
  3. Enable debug logging and inspect the raw API response to confirm it is truly empty vs. being filtered.
  4. If persistent, the default/test query logic in PerformQuery may need a broad fallback term.
Defensive patterns

Strategy: retry

Validate before calling

// Pre-test: confirm the API responds with at least a non-empty payload structure
var probe = await PerformQuery(new TorznabQuery());
if (!probe.Any())
{
    // do not hard-fail immediately; flag as 'verify access' rather than misconfigured
    logger.Warn("Nebulance test query returned no results; verify account browse access.");
}

Try / catch

try
{
    await indexer.ApplyConfiguration(configJson);
}
catch (ExceptionWithConfigData ex) when (ex.Message == "Testing returned no results!")
{
    // transient empty feed - safe to retry once after a short delay
    await Task.Delay(TimeSpan.FromSeconds(5));
    await indexer.ApplyConfiguration(configJson);
}

Prevention

When it happens

Trigger: ApplyConfiguration calls PerformQuery(new TorznabQuery()); the resulting IEnumerable is empty (results.Any() == false).

Common situations: The Nebulance API is reachable but its default feed is momentarily empty, a brand-new account with no indexed torrents, or an upstream change that made the default query return nothing.

Related errors

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