ipfs/kubo · error

unknown router type %q

Error message

unknown router type %q

What it means

A Routers.<name>.Type value did not match any known router kind (the switch over cfg.Type fell to default); supported types include the HTTP delegated router, DHT router, and the composable sequential/parallel routers.

Source

Thrown at routing/delegated.go:164

		crp := cfg.Parameters.(*config.ComposableRouterParams)
		var sr []*routinghelpers.SequentialRouter
		for _, cr := range crp.Routers {
			ri, err := parse(visited, createdRouters, cr.RouterName, routersCfg, extraDHT, extraHTTP)
			if err != nil {
				return nil, err
			}

			sr = append(sr, &routinghelpers.SequentialRouter{
				Router:      ri,
				IgnoreError: cr.IgnoreErrors,
				Timeout:     cr.Timeout.Duration,
			})

		}

		router = routinghelpers.NewComposableSequential(sr)
	default:
		return nil, fmt.Errorf("unknown router type %q", cfg.Type)
	}

	if err != nil {
		return nil, err
	}

	createdRouters[routerName] = router

	log.Info("created router ", routerName, " with params ", cfg.Parameters)

	return router, nil
}

type ExtraHTTPParams struct {
	PeerID        string
	AddrFunc      func() []ma.Multiaddr // dynamic address resolver for provider records
	PrivKeyB64    string
	HTTPRetrieval bool

View on GitHub (pinned to 329838acdf)

Solutions

  1. Set Type to a supported value (e.g. 'http', 'dht', 'sequential')
  2. Check for typos in Routers.<name>.Type
  3. Reference: docs/config.md Routers section for valid types
Defensive patterns

Strategy: validation

When it happens

Trigger: Thrown at routing/delegated.go:164 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of ipfs/kubo@329838acdf (2026-09-03). Data as JSON: /api/errors/76a790ebe6062bb7. Report an issue: GitHub.