​
Troubleshooting

If you only have 2 minutes, use this page as a triage front door.

​
First 60 seconds

Run this exact ladder in order: 
pllan status
pllan status --all
pllan gateway probe
pllan gateway status
pllan doctor
pllan channels status --probe
pllan logs --follow
Good output in one line:
  • pllan status → shows configured channels and no obvious auth errors.
  • pllan status --all → full report is present and shareable.
  • pllan gateway probe → expected gateway target is reachable (Reachable: yes). RPC: limited - missing scope: operator.read is degraded diagnostics, not a connect failure.
  • pllan gateway status → Runtime: running and RPC probe: ok.
  • pllan doctor → no blocking config/service errors.
  • pllan channels status --probe → channels report connected or ready.
  • pllan logs --follow → steady activity, no repeating fatal errors.

​
Anthropic long context 429

If you see: HTTP 429: rate_limit_error: Extra usage is required for long context requests, go to /gateway/troubleshooting#anthropic-429-extra-usage-required-for-long-context.

​
Plugin install fails with missing pllan extensions

If install fails with package.json missing pllan.extensions, the plugin package is using an old shape that Pllan no longer accepts. Fix in the plugin package:
  1. Add pllan.extensions to package.json.
  2. Point entries at built runtime files (usually ./dist/index.js).
  3. Republish the plugin and run pllan plugins install <npm-spec> again.
Example: 
{
  "name": "@pllan/my-plugin",
  "version": "1.2.3",
  "pllan": {
    "extensions": ["./dist/index.js"]
  }
}
Reference: Plugin architecture

​
Decision tree

pllan status
pllan gateway status
pllan channels status --probe
pllan pairing list --channel <channel> [--account <id>]
pllan logs --follow
Good output looks like:
  • Runtime: running
  • RPC probe: ok
  • Your channel shows connected/ready in channels status --probe
  • Sender appears approved (or DM policy is open/allowlist)
Common log signatures:
  • drop guild message (mention required → mention gating blocked the message in Discord.
  • pairing request → sender is unapproved and waiting for DM pairing approval.
  • blocked / allowlist in channel logs → sender, room, or group is filtered.
Deep pages:
pllan status
pllan gateway status
pllan logs --follow
pllan doctor
pllan channels status --probe
Good output looks like:
  • Dashboard: http://... is shown in pllan gateway status
  • RPC probe: ok
  • No auth loop in logs
Common log signatures:
  • device identity required → HTTP/non-secure context cannot complete device auth.
  • AUTH_TOKEN_MISMATCH with retry hints (canRetryWithDeviceToken=true) → one trusted device-token retry may occur automatically.
  • repeated unauthorized after that retry → wrong token/password, auth mode mismatch, or stale paired device token.
  • gateway connect failed: → UI is targeting the wrong URL/port or unreachable gateway.
Deep pages:
pllan status
pllan gateway status
pllan logs --follow
pllan doctor
pllan channels status --probe
Good output looks like:
  • Service: ... (loaded)
  • Runtime: running
  • RPC probe: ok
Common log signatures:
  • Gateway start blocked: set gateway.mode=local → gateway mode is unset/remote.
  • refusing to bind gateway ... without auth → non-loopback bind without token/password.
  • another gateway instance is already listening or EADDRINUSE → port already taken.
Deep pages:
pllan status
pllan gateway status
pllan logs --follow
pllan doctor
pllan channels status --probe
Good output looks like:
  • Channel transport is connected.
  • Pairing/allowlist checks pass.
  • Mentions are detected where required.
Common log signatures:
  • mention required → group mention gating blocked processing.
  • pairing / pending → DM sender is not approved yet.
  • not_in_channel, missing_scope, Forbidden, 401/403 → channel permission token issue.
Deep pages:
pllan status
pllan gateway status
pllan cron status
pllan cron list
pllan cron runs --id <jobId> --limit 20
pllan logs --follow
Good output looks like:
  • cron.status shows enabled with a next wake.
  • cron runs shows recent ok entries.
  • Heartbeat is enabled and not outside active hours.
Common log signatures:
  • cron: scheduler disabled; jobs will not run automatically → cron is disabled.
  • heartbeat skipped with reason=quiet-hours → outside configured active hours.
  • requests-in-flight → main lane busy; heartbeat wake was deferred.
  • unknown accountId → heartbeat delivery target account does not exist.
Deep pages:
pllan status
pllan gateway status
pllan nodes status
pllan nodes describe --node <idOrNameOrIp>
pllan logs --follow
Good output looks like:
  • Node is listed as connected and paired for role node.
  • Capability exists for the command you are invoking.
  • Permission state is granted for the tool.
Common log signatures:
  • NODE_BACKGROUND_UNAVAILABLE → bring node app to foreground.
  • *_PERMISSION_REQUIRED → OS permission was denied/missing.
  • SYSTEM_RUN_DENIED: approval required → exec approval is pending.
  • SYSTEM_RUN_DENIED: allowlist miss → command not on exec allowlist.
Deep pages:
pllan status
pllan gateway status
pllan browser status
pllan logs --follow
pllan doctor
Good output looks like:
  • Browser status shows running: true and a chosen browser/profile.
  • pllan starts, or user can see local Chrome tabs.
Common log signatures:
  • Failed to start Chrome CDP on port → local browser launch failed.
  • browser.executablePath not found → configured binary path is wrong.
  • No Chrome tabs found for profile="user" → the Chrome MCP attach profile has no open local Chrome tabs.
  • Browser attachOnly is enabled ... not reachable → attach-only profile has no live CDP target.
Deep pages: