Configuration

Nexigon Agent reads TOML configuration from /etc/nexigon/agent.toml by default. This page describes credentials, device identity, and optional features. For installation, follow Getting Started.

Connection Settings

Every device needs an executable fingerprint script that identifies it consistently. Static deployments also set a Nexigon Hub URL and a deployment token:

hub-url = "https://eu.nexigon.cloud"
token = "deployment_..."

fingerprint-script = "/usr/libexec/nexigon/nexigon-device-fingerprint"

Device Fingerprints

Nexigon Agent computes the device fingerprint from the fingerprint script’s standard output. Keep that output stable across reboots, updates, and credential changes, and unique to each device. Send diagnostics to stderr so they do not change the identity input.

For example, the following script uses /etc/machine-id. It requires a unique machine ID generated for each device and preserved across updates. Cloning the same populated machine-ID file into several devices would give them the same fingerprint. If storage can be replaced, use an identity source that survives that replacement, such as a hardware-specific identifier:

#!/usr/bin/env bash

set -euo pipefail

cat "/etc/machine-id"

Feature Configuration

Commands, operation polling, and the browser terminal are disabled by default. Enable the capabilities required by your device integration.

Commands

To allow Nexigon to run device commands, enable commands and point the agent at a directory of command definition files:

[commands]
enabled = true
directory = "/etc/nexigon/agent/commands"

Operation Polling

To let the agent pick up device-executable operation steps, configure operation polling:

[operations]
enabled = true
poll-interval-secs = 60

Operation polling and commands are both disabled by default. DeviceCommand steps only work when both are enabled and the referenced command exists on the device. The bundled agent does not execute DeviceTask steps.

Browser Terminal

The browser terminal opens a shell on the device independently of SSH forwarding:

[terminal]
enabled = true
user = "root"

Set user to the account that should run terminal sessions. Enable the feature only on devices where remote shell access is intended.

TCP Forwarding Capacity

The agent treats its authenticated Nexigon Hub as the policy authority for TCP forwarding and does not impose a separate feature-level forwarding limit. Device HTTP proxy admission, including the number of active forwards and the bounded request queue, is configured on the Nexigon Hub. The agent’s multiplex transport remains bounded to protect protocol resources.