{"version":"2.1.247","anchor":"clearer-refusal-for-unusable-local-ipc-paths","canonical_anchor":"clearer-refusal-for-unusable-local-ipc-paths","heading":"Clearer refusal for unusable local IPC paths","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/clearer-refusal-for-unusable-local-ipc-paths","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Clearer refusal for unusable local IPC paths\n\nRejected local socket paths now tell you exactly which rule they broke.\n\n**What**\n\nWhen a local connection target is rejected, the message now names the cases it rejects: remote or UNC hosts, and pipe names with extra segments or a trailing dot or space. The underlying error code is unchanged.\n\n**Evidence**\n\n`Refusing to connect: not a usable local IPC path (remote\/UNC host, or a pipe name with extra segments or a trailing dot\/space): `\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}