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

routeup doctor

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, warn, or a specific failure with the command that fixes it:

terminal

  [ok]   local CA at /Users/me/.routeup/ca.crt (expires 2027-08-11)
  [ok]   local CA trusted in OS trust store
  [ok]   port 443: helper installed
  [ok]   agent running (version 0.4.2, uptime 5127s)

The command exits successfully when every check is ok or warn, and fails when any check is fail. Use routeup doctor --json for structured check IDs, levels, messages, and an overall healthy boolean.

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 setup state is missing or damaged.

Non-browser clients

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

terminal

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

For apps with their own certificate settings, including Hoppscotch, see Custom CA certificates.