What causes "while downloading data for %s: %w" in crowdsecurity/crowdsec?

Inspect the wrapped inner error to find which data file failed and why.

while downloading data for

Error message

while downloading data for %s: %w

What it means

Wraps any error surfaced by downloadDataSet (which itself aggregates URL validation and per-data-file download failures) while processing the data files belonging to item i. It attaches the item's FileName so the user knows which item's data could not be set up.

Solutions

Inspect the wrapped inner error to find which data file failed and why.
Test/fix the offending data SourceURL, or remove the item if its data source is gone upstream.
Retry when network access is restored; note downloaded data files expire after 7 days and must be refreshed.
Use `cscli hub list -a` and item-specific inspect commands to see the data section state.

Defensive patterns

Strategy: try-catch

Validate before calling

// verify each data entry before download
for _, d := range item.DataSources {
    if u, err := url.Parse(d.SourceURL); err != nil || u.Scheme == "" {
        return fmt.Errorf("bad data URL for %s: %s", item.FileName, d.SourceURL)
    }
}

Try / catch

err := runDownloadPlan(ctx, plan)
if err != nil {
    log.Fatalf("while downloading data: %v", err) // inner error names the failing item/file
}

Prevention

Inspect an item's data section with `cscli <type> inspect <item>` before enabling it.
Provide network access or offline mirrors for remote blocklist data.
Remember downloaded data expires after 7 days; schedule hub refresh accordingly.
Check disk space and data-dir permissions on hosts with large blocklists.

When it happens

Trigger: Download Run on an item whose .data.yaml references data files that are unreachable, have invalid URLs, or fail to write into the hub data directory — the underlying cause is wrapped by errors 1090/1091 upstream in the same call chain.

Common situations: A parser/collection ships a data section pointing at a dead blocklist URL; offline install of an item requiring remote data; expired 7-day shelf-life file needing refresh but the host is offline.

Understand the failure class

Background: 'Something went wrong' / 'Request failed (500)' / 'HTTP error! status: 404' — what failed HTTP requests actually mean and how to find the real cause — this error's family across 28 libraries.

Related errors

AI-assisted analysis of crowdsecurity/crowdsec@909b515798 (2026-09-06). Data as JSON: /api/errors/1a025c9bafeb450b. Report an issue: GitHub.

Appendix: source

Thrown at pkg/hubops/download.go:196

	if downloaded {
		plan.ReloadNeeded = true
	}

	i.State.Tainted = false
	i.State.UpToDate = true

	// read content to get the list of data files
	reader, err := os.Open(finalPath)
	if err != nil {
		return fmt.Errorf("while opening %s: %w", finalPath, err)
	}

	defer reader.Close()

	needReload, err := downloadDataSet(ctx, plan.hub.GetDataDir(), c.Force, reader)
	if err != nil {
		return fmt.Errorf("while downloading data for %s: %w", i.FileName, err)
	}

	if needReload {
		plan.ReloadNeeded = true
	}

	return nil
}

func (*DownloadCommand) OperationType() string {
	return "download"
}

func (c *DownloadCommand) ItemType() string {
	return c.Item.Type
}

func (c *DownloadCommand) Detail() string {

View on GitHub (pinned to 909b515798)