caddyserver/caddy · error

loading TLS session ticket ephemeral keys provider module: %

Error message

loading TLS session ticket ephemeral keys provider module: %s

What it means

Error "loading TLS session ticket ephemeral keys provider module: %s" thrown in caddyserver/caddy.

Source

Thrown at modules/caddytls/sessiontickets.go:75

func (s *SessionTicketService) provision(ctx caddy.Context) error {
	s.configs = make(map[*tls.Config]struct{})
	s.mu = new(sync.Mutex)

	// establish sane defaults
	if s.RotationInterval == 0 {
		s.RotationInterval = caddy.Duration(defaultSTEKRotationInterval)
	}
	if s.MaxKeys <= 0 {
		s.MaxKeys = defaultMaxSTEKs
	}
	if s.KeySource == nil {
		s.KeySource = json.RawMessage(`{"provider":"standard"}`)
	}

	// load the STEK module, which will provide keys
	val, err := ctx.LoadModule(s, "KeySource")
	if err != nil {
		return fmt.Errorf("loading TLS session ticket ephemeral keys provider module: %s", err)
	}
	s.keySource = val.(STEKProvider)

	// if session tickets or just rotation are
	// disabled, no need to start service
	if s.Disabled || s.DisableRotation {
		return nil
	}

	// start the STEK module; this ensures we have
	// a starting key before any config needs one
	return s.start()
}

// start loads the starting STEKs and spawns a goroutine
// which loops to rotate the STEKs, which continues until
// stop() is called. If start() was already called, this
// is a no-op.

View on GitHub (pinned to 50e54ee279)

Solutions

  1. Check the session ticket keys provider module name and configuration; the wrapped error identifies the problem.

When it happens

Trigger: Thrown at modules/caddytls/sessiontickets.go:75 when the library encounters an invalid state.

Common situations: See trigger scenarios.

Understand the failure class


AI-assisted analysis of caddyserver/caddy@50e54ee279 (2026-08-15). Data as JSON: /api/errors/4abc2e5bda80a5aa. Report an issue: GitHub.