Skip to content
routeup

routeup doctor

routeup doctor checks that the pieces setup installed are still healthy. Run it whenever a local route does not load as expected.

Terminal window
routeup doctor

What it checks

Section titled “What it checks”
  • Local CA: the certificate authority exists under ~/.routeup.
  • OS trust: that CA is present in the system trust store.
  • Port 443: routeup can answer on 443 (the macOS forwarder is installed, or the Linux cap_net_bind_service capability is set on the binary).
  • Agent: the background agent is running and reachable over its local socket.

Each check prints ok or a specific failure with the command that fixes it.

Common failures

Section titled “Common failures”
  • Lost Linux capability after an upgrade: a package upgrade replaces the binary inode, dropping the setcap capability. doctor detects this with getcap; re-run routeup setup to reapply it.
  • CA not trusted: the trust store was reset or the CA was removed. Re-run routeup setup.
  • Agent unreachable: restart it with routeup agent restart, or run routeup setup if autostart was removed.

Non-browser clients

Section titled “Non-browser clients”

Browsers, Safari, and curl use the system trust store automatically. Some runtimes ship their own CA bundle, point them at the routeup CA:

Terminal window
export NODE_EXTRA_CA_CERTS=~/.routeup/ca.crt   # Node.js
export REQUESTS_CA_BUNDLE=~/.routeup/ca.crt     # Python (requests / urllib3)