hyperledger/fabric · error

config envelope has nil config

Error message

config envelope has nil config

What it means

Validate returns this when the ConfigEnvelope is non-nil but its inner Config field is nil. The envelope shell exists but carries no actual configuration to apply, so validation cannot proceed. Like the nil-envelope check, it is a fast-fail guard before sequence and content checks.

Source

Thrown at common/configtx/validator.go:168

	}

	return &cb.ConfigEnvelope{
		Config: &cb.Config{
			Sequence:     vi.sequence + 1,
			ChannelGroup: channelGroup,
		},
		LastUpdate: configtx,
	}, nil
}

// Validate simulates applying a ConfigEnvelope to become the new config
func (vi *ValidatorImpl) Validate(configEnv *cb.ConfigEnvelope) error {
	if configEnv == nil {
		return errors.Errorf("config envelope is nil")
	}

	if configEnv.Config == nil {
		return errors.Errorf("config envelope has nil config")
	}

	if configEnv.Config.Sequence != vi.sequence+1 {
		return errors.Errorf("config currently at sequence %d, cannot validate config at sequence %d", vi.sequence, configEnv.Config.Sequence)
	}

	configUpdateEnv, err := protoutil.EnvelopeToConfigUpdate(configEnv.LastUpdate)
	if err != nil {
		return err
	}

	configMap, err := vi.authorizeUpdate(configUpdateEnv)
	if err != nil {
		return err
	}

	channelGroup, err := configMapToConfig(configMap, vi.namespace)
	if err != nil {

View on GitHub (pinned to 2736b63f8f)

Solutions

1. Ensure the Config field is populated (with Sequence and ChannelGroup) before calling Validate.
2. Re-serialize from the original bytes or rebuild the envelope if it came from an empty unmarshal.
3. Guard with a nil check on env.Config before invoking the validator.

Example fix

// before
env := &cb.ConfigEnvelope{} // Config unset
validator.Validate(env)
// after
env := &cb.ConfigEnvelope{Config: &cb.Config{Sequence: seq, ChannelGroup: channelGroup}}
validator.Validate(env)

if configEnv == nil || configEnv.Config == nil { return errors.New("config envelope has no inner Config") }

func hasConfig(cEnv *cb.ConfigEnvelope) bool { return cEnv != nil && cEnv.Config != nil }

if err := validator.Validate(env); err != nil {
    if strings.Contains(err.Error(), "config envelope has nil config") {
        // rebuild envelope with Config: &cb.Config{Sequence:..., ChannelGroup:...}
        return err
    }
}

When it happens

Trigger: Calling Validate with a ConfigEnvelope whose Config is nil — e.g., an envelope constructed as &cb.ConfigEnvelope{} without setting Config, or one deserialized from an empty/partial payload.

Common situations: Hand-constructed ConfigEnvelope objects in tests or tools; proto unmarshaling from truncated payloads yielding an empty message; code paths that set only ChannelGroup or Sequence on the wrong struct.

Related errors

• Attempted to set the batch size max message count to an inva
• Attempted to set the batch size absolute max bytes to an inv
• Attempted to set the batch size preferred max bytes to an in
• Attempted to set the batch size preferred max bytes (%v) gre
• Attempted to set the batch timeout to a non-positive value:

AI-assisted analysis of hyperledger/fabric@2736b63f8f (2026-09-04). Data as JSON: /api/errors/83e6c7491becdb2c. Report an issue: GitHub.