registry_client_build_failed

Summary

`{0}` failed to build http client

Help

inspect the rustls/native-tls feature set and proxy configuration

Details

When this fires

ClientError in crates/nanook-core/src/registry.rs is emitted when an adapter, collector, or action couldn't build its reqwest HTTP client. The named target is the entity's config name; the wrapped source comes from reqwest::ClientBuilder::build. Reasons usually trace back to TLS backend selection (rustls vs native-tls feature flags), bad proxy configuration picked up from env, or invalid root-cert paths. Surfaces during nanook run startup, when registries materialize their entries.

What to check

Check HTTP_PROXY / HTTPS_PROXY / NO_PROXY for malformed values inherited by the nanook process. Overridden CA bundles via SSL_CERT_FILE must point at a valid PEM. Mismatched TLS feature sets (rustls vs native-tls) at build time also surface here.