{"version":"2.1.273","anchor":"better-error-messages-for-github-token-import-failures","canonical_anchor":"better-error-messages-for-github-token-import-failures","heading":"More specific error messages for GitHub token import network failures","tier":"notice","area":"GitHub","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/better-error-messages-for-github-token-import-failures","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### More specific error messages for GitHub token import network failures\n\nGitHub token import now shows clearer errors for TLS\/proxy problems and invalid tokens, including a new sslHint\n\n**What**\n\nImporting a GitHub token now gives more actionable error messages:\n\n- Network errors are classified, and TLS-tunnel (ERR_PROXY_TUNNEL) failures now explain that the proxy refused the tunnel, via a new `sslHint`.\n\n- Generic network errors during token import\/web-setup now surface the `sslHint` and\/or which proxy environment-variable source is in effect.\n\n- Invalid-token (400) responses now parse the server's message and show it in the UI, appending guidance to add the repo scope.\n\n**Why**\n\nThese changes turn generic, hard-to-diagnose network and token errors into specific messages that point at the actual cause, such as a proxy blocking the connection or a token missing a required scope.\n\n- Area: GitHub\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}