Skip to content
nara Documentation

Troubleshooting

Troubleshooting

No authentication token found

Section titled “No authentication token found”

Symptom

  • CLI commands (generate, package, upload, test) fail with a message like: “No authentication token found. Run: edge-connector auth”.

Fix

  • run edge-connector auth --token "<ADMIN_JWT>" on the machine, or
  • in desktop mode, complete the browser-based login when prompted.

Ensure AUTH_TOKEN_PATH points to a writable location if you overridden it.

Unable to connect to Tool RPC

Section titled “Unable to connect to Tool RPC”

Symptom

  • generate or test reports that it cannot connect to the Tool RPC server, or times out.

Fix

  • verify the Tool RPC URL (TOOL_RPC_URL, config.json, or CLI flags),
  • confirm the server is reachable from the connector host (network/firewall),
  • double-check that your token is valid for the target environment.

Deployment already connected

Section titled “Deployment already connected”

Symptom

  • the runtime logs “Deployment already connected from another instance”.

Fix

  • stop the other connector using the same deploymentId, or
  • create a separate deployment for the new environment and update credentials.

Upload failed

Section titled “Upload failed”

Symptom

  • edge-connector upload fails with an HTTP error or “Upload failed” message.

Fix

  • ensure the bundle is a .tgz produced by edge-connector package,
  • check that the file size is within the allowed limit,
  • confirm your token is valid and has access to the organization,
  • if the error includes a server message, follow that guidance (for example invalid org ID).