caddyserver/caddy · error

no build information

Error message

no build information

What it means

Error "no build information" thrown in caddyserver/caddy.

Source

Thrown at cmd/commandfuncs.go:424

	resp, err := AdminAPIRequest(adminAddr, http.MethodPost, "/load", headers, bytes.NewReader(config))
	if err != nil {
		return caddy.ExitCodeFailedStartup, fmt.Errorf("sending configuration to instance: %v", err)
	}
	defer resp.Body.Close()

	return caddy.ExitCodeSuccess, nil
}

func cmdVersion(_ Flags) (int, error) {
	_, full := caddy.Version()
	fmt.Println(full)
	return caddy.ExitCodeSuccess, nil
}

func cmdBuildInfo(_ Flags) (int, error) {
	bi, ok := debug.ReadBuildInfo()
	if !ok {
		return caddy.ExitCodeFailedStartup, fmt.Errorf("no build information")
	}
	fmt.Println(bi)
	return caddy.ExitCodeSuccess, nil
}

// jsonModuleInfo holds metadata about a Caddy module for JSON output.
type jsonModuleInfo struct {
	ModuleName string `json:"module_name"`
	ModuleType string `json:"module_type"`
	Version    string `json:"version,omitempty"`
	PackageURL string `json:"package_url,omitempty"`
}

func cmdListModules(fl Flags) (int, error) {
	packages := fl.Bool("packages")
	versions := fl.Bool("versions")
	skipStandard := fl.Bool("skip-standard")
	jsonOutput := fl.Bool("json")

View on GitHub (pinned to 50e54ee279)

Solutions

1. Use an official Caddy binary built with module info, or rebuild with proper build information embedded.

When it happens

Trigger: Thrown at cmd/commandfuncs.go:424 when the library encounters an invalid state.

Common situations: See trigger scenarios.

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