Skip to content
rConfig V8 Core Documentation rConfig V8 Core Documentation rConfig V8 Core Documentation

System Settings Reference

System Settings Reference: Configuration and Administration in rConfig V8 Core

Section titled “System Settings Reference: Configuration and Administration in rConfig V8 Core”

After reading this page, you can locate any System Settings section in rConfig V8 Core, understand what it controls, and jump straight to the detailed guide for that area. It maps each settings group to its purpose so administrators can find the right configuration screen quickly.

System Management

Section titled “System Management”

Core system configuration, upgrades, and operational settings.

System

Section titled “System”

General system configuration including the application name, timezone, date and time formats, email settings, and default user interface preferences. Configure these during initial deployment to set organizational standards, or whenever you adjust system-wide display and behavior.

Related documentation: Security Hardening covers the wider configuration baseline for a new install.

Upgrade

Section titled “Upgrade”

In-place upgrade management for moving rConfig to a newer release. Use the upgrade screen to check for available updates and run the update process when a new version ships features, improvements, or security fixes.

Related documentation: Update Process.

Security and Access

Section titled “Security and Access”

Authentication, authorization, and security hardening configuration.

Security

Section titled “Security”

System security settings including password complexity and rotation policies, session timeout and concurrent session limits, two-factor authentication, API rate limiting, HTTPS enforcement, and audit logging. Set these during initial deployment to establish a security baseline, when meeting compliance requirements, or when hardening the system.

Related documentation:

Device Credentials

Section titled “Device Credentials”

Management of the authentication credentials rConfig uses to connect to network devices. Create and manage credential sets, configure SSH passwords and private keys, set Telnet passwords, configure SNMP community strings and v3 credentials, and assign credentials to devices. Use this when adding devices that need different credentials, rotating device passwords, or organizing credentials by device group.

Related documentation: Managing Devices covers how credentials attach to each device.

Data Management

Section titled “Data Management”

Migration and bulk data lifecycle tooling.

Data Migration

Section titled “Data Migration”

Migration tools for moving from a previous rConfig version or between deployments, covering the database, configuration files, user accounts, policy data, and integration settings. Use these when upgrading an older instance to V8 Core, moving to new infrastructure, or consolidating instances.

Related documentation: V6 Core to V8 Core Update.

Import / Export

Section titled “Import / Export”

Bulk import devices from a spreadsheet and export rConfig database tables to CSV. Download a locally generated device import template (.xlsx), bulk create devices from a populated .csv or .xlsx file with per row validation, and export any non-internal database table to CSV for backup or analysis. Use this when onboarding many devices at once, migrating from a legacy system, or taking a CSV snapshot for reporting.

Related documentation:

Monitoring and Debugging

Section titled “Monitoring and Debugging”

Logging, monitoring, and diagnostic configuration.

Logging and Debugging

Section titled “Logging and Debugging”

Configuration of logging levels, debug mode, log rotation, and diagnostic tools for troubleshooting. Log levels run from emergency through debug, and debug mode produces verbose output for support requests. Use this when troubleshooting system issues, investigating performance, or gathering diagnostic detail.

Related documentation:

Application Logs

Section titled “Application Logs”

Access to the database-driven application event log for operational monitoring. View and filter events, search descriptions by keyword, filter by severity, and export logs for external analysis. Use this when investigating device connection issues, reviewing user activity, monitoring scheduled task runs, or troubleshooting application errors.

Related documentation: Application Log.

Scheduled Tasks

Section titled “Scheduled Tasks”

Management and monitoring of background tasks including configuration downloads, compliance checks, and maintenance operations. View execution history, monitor success and failure rates, configure schedules, and enable or disable tasks. Use this when reviewing task status, troubleshooting failures, or tuning schedules for performance.

Related documentation:

Health Checks (Environment)

Section titled “Health Checks (Environment)”

Connectivity health checks can be tuned for online, internal-only, and air-gapped deployments to avoid false-positive failures. External ping checks are configurable through environment variables, can be disabled entirely, and the deployment can be marked offline or air-gapped. Internal-only ping targets such as localhost or a gateway are supported.

SettingDefaultPurpose
HEALTHCHECK_PING_ENABLEDtrueMaster switch for the connectivity ping check. Set to false to disable ping checks completely.
HEALTHCHECK_OFFLINE_MODEfalseMarks the deployment as offline. When true, ping checks are skipped automatically.
HEALTHCHECK_AIR_GAPPEDfalseMarks the deployment as air-gapped. When true, ping checks are skipped automatically.
HEALTHCHECK_PING_TARGEThttps://www.rconfig.comTarget URL or host used by the ping health check. Set to an internal endpoint for isolated networks.
HEALTHCHECK_PING_TIMEOUT5Timeout in seconds for the ping check before it is treated as failed.

Behavior summary:

  • The ping check runs only when HEALTHCHECK_PING_ENABLED=true and both offline flags are false.
  • If either HEALTHCHECK_OFFLINE_MODE=true or HEALTHCHECK_AIR_GAPPED=true, the ping check is skipped.
  • If the ping check is enabled and the target is internal, the health check validates internal reachability only.

Disable the connectivity ping check entirely:

HEALTHCHECK_PING_ENABLED=false

Air-gapped deployment (automatic ping check skip):

HEALTHCHECK_PING_ENABLED=true
HEALTHCHECK_AIR_GAPPED=true

Internal-only validation (no external dependency):

HEALTHCHECK_PING_ENABLED=true
HEALTHCHECK_PING_TARGET=http://127.0.0.1
HEALTHCHECK_PING_TIMEOUT=3

Use these settings for environments without internet access, segmented internal networks, strict firewall policies, or when health checks should validate internal reachability instead of external internet access.

Info

Section titled “Info”

System information and version details.

About

Section titled “About”

System information display including the rConfig version and build, license status, system health metrics (uptime and resource usage), installed modules, open source credits, and support contact information. Use this when verifying the version for a support request, checking license status, or reviewing system health at a glance.

Related documentation: rConfig V8 Core Overview.

How do I access System Settings?

Section titled “How do I access System Settings?”
  1. Log in with an account that has the Admin role.
  2. Open Settings from the main navigation menu.
  3. Choose a section from the categories in the left sidebar.
  4. Select a section to view and modify its configuration.

Many sections include search fields that match on setting names, descriptions, and values, with filters to narrow results by category or status.

What’s next

Section titled “What’s next”