Connecting to Legra

Your CLI needs a reachable Legra node and access to the workspace you want to use. Your organization may provide a node identifier or a connection ticket.

Choose the connection

Use the supplied full node identifier:

legra --node <node-id> node vitals

Or use a connection ticket:

legra --ticket <ticket> node vitals

Keep that connection option when running graph commands. A ticket identifies where to connect; it does not replace workspace membership.

If Legra is already running on your machine, restrict the connection locally:

legra --localhost node vitals

--lan selects local-network discovery when your setup uses it. Shared options and environment variables are listed in Command context.

Connect from a browser

Open Legra and sign in. Select a workspace available to your account. For scripts that use HTTP, obtain the gateway URL and credentials for your environment and follow HTTP API.

Diagnose a failed connection

1. Check the exact command and the selected node or ticket.
2. Run legra --version to identify your CLI version.
3. Run node vitals with the same connection options.
4. If the node is reachable, check your account and workspace selection.
5. If access is denied, ask a workspace administrator to review your membership.

When reporting a problem, include the command, version, error text, and whether other commands can reach the node. Remove credentials and private data from the report. Node commands cover health and logs.