Noxgild
Troubleshooting

CLI Connection Problems

Fix common Noxgild computer-connection and diagnostic problems.

The public connection command is:

npx @noxgild/cli@latest connect

Command is not found

Confirm Node.js 22 or later is installed and that node, npm, and npx are available in the terminal.

Platform not available

Certified public local runtimes are available for Windows, macOS, and Linux.

The CLI detects the host platform and architecture and installs the matching certified Noxgild runtime.

Browser did not open

The CLI prints the verification URL when it cannot open a browser automatically. Copy that URL into a browser yourself and complete the approval.

Approval expired

Connection requests are short-lived. Run the CLI command again to generate a fresh request.

You approved but installation failed

Do not keep approving repeated requests blindly. Capture the terminal error, confirm the computer is running a supported Windows, macOS, or Linux configuration, and contact support if a fresh attempt fails the same way.

Run the diagnostic

After installation, run:

noxgild doctor

Use the report to confirm that the computer is connected and whether Relay, Files & terminal, Browser, or Desktop access is unavailable.

If doctor says the runtime is missing or incomplete, rerun the public connection flow rather than manually copying credentials or pairing data.

The CLI says connected but the computer is unavailable

Open the account area and compare its computer state with noxgild doctor.

Continue with Computer offline if the computer or one of its local workers is unavailable.

On this page