Connection errors now name the real problem: DNS, refused, unreachable, or a proxy tunnel failure.
What's wrong with this entry?
"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.
check your connection or VPN (
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
Clearer message when a request is rejected as too large
Both mention error message
-
v2.1.228
API rejections are classified from a structured marker instead of prose alone
Both mention error
-
v2.1.234
Empty or malformed API responses now report what actually answered
Both mention error