{"version":"2.1.323","anchor":"sign-in-errors-and-org-settings-check-give-actionable-messag","canonical_anchor":"sign-in-errors-and-org-settings-check-give-actionable-messag","heading":"Failed sign-ins now explain what went wrong and what to try","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/sign-in-errors-and-org-settings-check-give-actionable-messag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Failed sign-ins now explain what went wrong and what to try\n\nSign-in failures now show the HTTP status with advice or a proxy and connection hint, and the org-settings check adds a hint on timeouts\n\n**What**\n\nWhen signing in fails, Claude Code now shows a specific message instead of a bare failure. Depending on what happened, it shows either:\n\n- The HTTP status code (the number a web server returns to say what went wrong) together with advice.\n\n- A hint about proxies (servers some networks route traffic through) and your internet connection, such as checking your connection and trying again.\n\nThe message shown when Claude Code cannot verify your organization's settings also gains an extra hint when the failure is a connection error or a timeout.\n\n**Why**\n\nSign-in problems caused by a proxy or a flaky network become much easier to work out from the message alone.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}