DecaCapBuilders
AccountOpen workbench

local companion

Connection refused at the loopback endpoint

Nothing accepted the browser’s request at the configured device-local address.

Search another error
Curious Obmil examines three clearly separated illuminated diagnostic paths inside a brass-and-crystal crossroads
Decode the cause before choosing the response.
MATCH THESE VISIBLE STRINGS
  • ERR_CONNECTION_REFUSED
  • Connection refused
  • Failed to fetch
LIKELY CAUSES
  • Companion process stopped
  • Wrong port or protocol
  • Firewall or browser private-network control
  • The local runtime is running but the DecaCap companion is not
NEVER DO THIS
  • Do not substitute a remote public URL
  • Do not disable the operating-system firewall globally
SMALLEST DIAGNOSTIC FIRST

Repair sequence

01

Start or restart the DecaCap Local Companion

02

Use the exact endpoint shown by the companion

03

Keep the endpoint on 127.0.0.1 or localhost

04

Run companion health before testing the model runtime

05

Inspect local companion logs if health still fails