{"version":"2.1.300","anchor":"egress-proxy-connect-rejection-message-reworded","canonical_anchor":"egress-proxy-connect-rejection-message-reworded","heading":"Blocked network connections now point to the host not being allowed","tier":"notice","area":"Network","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/egress-proxy-connect-rejection-message-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Blocked network connections now point to the host not being allowed\n\nWhen the outbound proxy rejects a connection, the message now says a refusal most often means the host is not allowed for this session\n\n**What**\n\nIn some setups, Claude Code's network connections go out through a proxy (a go-between server that can allow or block destinations). When that proxy rejects a connection, the message used to say it was denied by organization policy or could not reach the destination.\n\nIt now says the proxy refused the connection or could not reach the host. It adds that a refusal most often means the host is not allowed for this session.\n\n**Why**\n\nWhen a connection is blocked, the message now points you toward the most likely cause.\n\n- Area: Network\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}