gastownhall/beads · error

--proxied-server-config-path %v

Error message

--proxied-server-config-path %v

What it means

The config file passed via --proxied-server-config-path failed validateProxiedServerConfig; the underlying validation message is wrapped and surfaced with this prefix. init does not inspect the file's semantics until this point.

Source

Thrown at cmd/bd/init.go:455

		}
		if initProxiedServer {
			if sharedServer || externalServer ||
				serverHost != "" || serverPort != 0 || serverSocket != "" || serverUser != "" || cmd.Flags().Changed("server-tls") {
				return fmt.Errorf("--proxied-server cannot be combined with --shared-server, --external, or any --server-* flag")
			}
		}
		if initTeamServer && !initProxiedServer {
			return fmt.Errorf("--team-server requires --proxied-server")
		}
		if serverConfigPath != "" {
			if !initProxiedServer {
				return fmt.Errorf("--proxied-server-config-path requires --proxied-server")
			}
			if !filepath.IsAbs(serverConfigPath) {
				return fmt.Errorf("--proxied-server-config-path must be an absolute path, got %q", serverConfigPath)
			}
			if err := validateProxiedServerConfig(serverConfigPath); err != nil {
				return fmt.Errorf("--proxied-server-config-path %v", err)
			}
		}
		if serverLogPath != "" {
			if !initProxiedServer {
				return fmt.Errorf("--proxied-server-log-path requires --proxied-server")
			}
			if !filepath.IsAbs(serverLogPath) {
				return fmt.Errorf("--proxied-server-log-path must be an absolute path, got %q", serverLogPath)
			}
			if err := validateProxiedServerLogPath(serverLogPath); err != nil {
				return fmt.Errorf("--proxied-server-log-path %v", err)
			}
		}
		if serverRootPath != "" {
			if !initProxiedServer {
				return fmt.Errorf("--proxied-server-root-path requires --proxied-server")
			}
			if !filepath.IsAbs(serverRootPath) {

View on GitHub (pinned to 71377f2769)

Solutions

  1. Read the wrapped detail after '--proxied-server-config-path ' for the specific problem
  2. Validate the file is valid JSON and matches the proxied-server config schema
  3. Confirm the path points to the intended existing file (ls/cat it)

Example fix

// before
bd init --proxied-server --proxied-server-config-path /etc/bd/proxied.json  # invalid JSON
// after
# fix JSON, e.g. jq . /etc/bd/proxied.json to check, then re-run
bd init --proxied-server --proxied-server-config-path /etc/bd/proxied.json
Defensive patterns

Strategy: validation

Validate before calling

jq empty /etc/bd/proxied.json && echo ok || echo 'invalid JSON config'

Prevention

When it happens

Trigger: Running `bd init --proxied-server --proxied-server-config-path <file>` where the file is missing, unreadable, malformed JSON, or contains invalid proxied-server configuration values.

Common situations: Hand-editing the proxied server config and introducing syntax errors; pointing at a config from a different tool; file deleted between config authoring and init.

Understand the failure class

Background: Config validation failed: what "invalid value for {key}" and settings-rejection errors mean across 19 open-source libraries — this error's family across 19 libraries.

Related errors

AI-assisted analysis of gastownhall/beads@71377f2769 (2026-08-30). Data as JSON: /api/errors/3fbb975a7aae1cef. Report an issue: GitHub.