{"version":"2.1.227","anchor":"connection-errors-say-what-actually-went-wrong","canonical_anchor":"connection-errors-say-what-actually-went-wrong","heading":"Connection errors say what actually went wrong","tier":"notice","area":"Error Messages","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/connection-errors-say-what-actually-went-wrong","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Connection errors say what actually went wrong\n\nConnection errors now name the real problem: DNS, refused, unreachable, or a proxy tunnel failure.\n\n**What**\n\n\"Unable to connect to API (CODE)\" is replaced by distinct messages per socket, DNS and proxy error: dropped connections, refused connections with a firewall or proxy hint, unreachable hosts, no route to host, and failed proxy tunnels. Unrecognised codes still get the old generic wording.\n\n**Evidence**\n\n`check your connection or VPN (`\n\n- Area: Error Messages\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 1\/5"}