{"version":"2.1.281","anchor":"gateway-managed-settings-host-must-resolve-to-a-private-addr","canonical_anchor":"gateway-managed-settings-host-must-resolve-to-a-private-addr","heading":"Gateway managed-settings host must resolve to a private address","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/gateway-managed-settings-host-must-resolve-to-a-private-addr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Gateway managed-settings host must resolve to a private address\n\nA gateway host used as a managed-settings source must now use https and resolve to a private network address\n\n**What**\n\nManaged settings are settings an organization pushes to Claude Code. When they come from a gateway host, Claude Code now checks that host before accepting it:\n\n- It must use https.\n\n- Its addresses must be private, or inside a network the organization has declared.\n\nIf the host resolves to a public address, the connection is dropped with `EADDRNOTPRIVATE`. If the check against the declared network fails, you are asked to connect to your organization's network or VPN.\n\n**Why**\n\nSettings meant to come from inside your organization can no longer be fetched from a host on the public internet. If you work away from the office, you may need to be on the VPN for managed settings to load.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}