Diagnostics & settings
This page covers the diagnostics screen and the account/settings screens reached from the account menu.
Diagnostics
Section titled “Diagnostics”Reached from the rail’s Diagnostics button. Host health cards across the top, the log below.
| Card | What it shows |
|---|---|
| Host | The machine’s hostname and OS version. |
| CPU Load | Aggregate CPU usage. |
| System Memory | Memory used / total. |
| Uptime | How long the node has been running, and the build version. |
The cards are fed from __sys/host/*. Below them, the Logger shows the node’s full log stream —
each line a timestamp, a level badge (INFO / WARNING / ERROR) and the message. The same log is
available everywhere from the floating
Logger drawer.
System Config
Section titled “System Config”Reached from Account → System Config. Three sections, with a Save button for the editable fields.
Basic Configuration
Section titled “Basic Configuration”| Field | What it is |
|---|---|
| Node ID (with copy) | The node’s stable unique identifier (read-only). |
| Node Name | A friendly name for the node (editable). |
| Description | Free-text notes about the node. |
Script defaults
Section titled “Script defaults”| Field | What it is |
|---|---|
| Skip if already running | The node-wide default for the per-script Skip if already running flag applied to newly created scripts. On by default; existing scripts keep their own setting. |
Remote Access
Section titled “Remote Access”Controls browser access to this node through the JasperX cloud (a Disconnected / Connected badge shows the current tunnel state).
| Control | What it is |
|---|---|
| Allow browser access through JasperX | Master toggle for remote access. |
| Max sessions | How many concurrent remote browser sessions are allowed. |
| Inactivity timeout (min) | Auto-disconnect an idle session after this many minutes (0 = never). |
| Allowed ports | Which ports remote access may use (default: the JasperNode HTTP port only). |
| Save | Applies the Remote Access changes. |
Danger Zone
Section titled “Danger Zone”| Action | What it does |
|---|---|
| Restart application → Restart | Restarts the JasperNode process. Connectors briefly drop and reconnect; all tags, configuration, scripts and the Node ID are preserved. |
| Factory reset → Reset | Permanently deletes all tags and configuration, stops the Logic Cycle, regenerates the Node ID, and unlinks from JasperX. Setup is required again — this cannot be undone. |
System Updates
Section titled “System Updates”Reached from Account → System Updates. Shows the current runtime version and lets you check for and install an update to the JasperNode runtime.
Report Issue
Section titled “Report Issue”Reached from Account → Report Issue. A form for filing a bug report against the node.
Login & Setup
Section titled “Login & Setup”These appear before the main IDE:
- Setup — a one-time first-run step shown on a brand-new node, to establish its identity before anything can be edited.
- Login — sign-in via a single Login via JasperX button (OAuth through the JasperX cloud; there are no local accounts). The first editor to register a node becomes its owner.