magus v0.4.3 is out. See what's new
¶ View markdown source · ✎ Suggest an edit

MGS9014: share listener unavailable

The server answered 503 service unavailable to a share request because it could not open the LAN listener the other device connects to.

[MGS9014] share: no up, non-loopback, private-range IPv4 interface found;
connect to a LAN or Wi-Fi network and try again
  see: .../MGS9014.md

Why

A share serves the console on this machine's private LAN address, never on a public one. With no private-range IPv4 interface up there is no address a nearby device could reach, and a listener that cannot bind has nothing to serve on.

Resolution

Connect to a LAN or Wi-Fi network and start the share again. If one is connected, the message names the address the listener could not bind; free that port or retry once whatever holds it exits.

AuthPages in this section. MGS9001: bearer token rejectedThe server refused a request because the bearer token it carried was wrong, expired, or revoked. This is the usual reason an MCP client cannot connect. Tokens and grantsHow the magus daemon decides who may use which route. Four token classes told apart by prefix, a grant of none, read or write per scope, a need declared by every procedure, one rule for minting, the trust model, and what the activity trail records about each. Daemon APIThe magus daemon's Connect, gRPC, and gRPC-Web API: every service, method, message, and enum, generated from the .proto contract.
MGS9014authsharelan503
Last updated (95680f58)
Earlier changes on this page (1)

Full history ↗ · Blame source ↗

Glossary

Op

A single tool-native command a target composes (long form: operation); the middle of the work hierarchy (Spell to Op to Target). Op in full.

Service

A long-running or shared process magus manages across runs, distinct from a one-shot target. Service in full.

Conventions

This page uses none of the site's convention markers. The full set is on the conventions page.