How to update rConfig V8 Pro

How to update rConfig V8 Pro

After reading this page, I can locate the rConfig update interface, verify backup requirements, and apply a system update safely in a production environment.

When to use this

Use this guide when a green update notification appears on the rConfig dashboard, or when your team has scheduled a maintenance window to apply the latest release. If you are setting up rConfig for the first time, complete the V8 Pro Installation steps before using this workflow.

Prerequisites

• Administrator access to rConfig
• SSH access to the server running rConfig
• Your installation is at the default path /var/www/html/rconfig8 (non-standard paths are not supported)
• A verified, tested backup completed before running the update (see Enterprise Backup Requirements below)
• Operating system is RHEL, CentOS, Rocky Linux, Alma Linux, or Ubuntu

Supported installation path only

Update scripts target the default installation path /var/www/html/rconfig8 exclusively. If your instance has been moved, symlinked, or renamed, updates will fail and the system may be left in a broken state. Deployments that deviate from the default path are not eligible for support under your subscription agreement. Verify your path before proceeding, or contact prosupport@rconfig.com first.

Enterprise Backup Requirements

Back up before every update

Production systems must not be updated without verified, tested backups. Complete all of the following before proceeding:

• Database snapshot: Full backup of all configuration data, device inventories, compliance records, and historical data
• Application snapshot: Full system or virtual machine snapshot for virtualised deployments
• Configuration files: Backup all rConfig config files, custom scripts, integration configs, and encryption keys
• Backup validation: Restore from backup to confirm data integrity before the update window
• Rollback documentation: Maintain a documented, tested rollback procedure accessible to your operations team

System failures, data corruption, or compatibility issues during updates can cause extended downtime and data loss. Confirm completion with your system administrator before continuing.

Enterprise Update Best Practices

Production environment checklist

• Staging first: Deploy updates to a staging environment mirroring production before touching production
• Maintenance window: Schedule the update during an approved window with stakeholder notification
• Post-update monitoring: Verify all systems and integrations are functioning immediately after the update
• Rollback ready: Ensure rollback procedures are documented and can be executed quickly if needed
• Integration validation: Test all third-party integrations, API connections, and automated workflows after update completion

License Agreement and Data Responsibility

Your responsibility

By running rConfig system updates, you accept the terms of the rConfig license agreement. All data management, backup procedures, and system administration are performed at your own risk. rConfig and its developers assume no responsibility for data loss, system downtime, or operational issues during update processes. Ensure compliance with your organisation’s data governance policies before proceeding.

Step-by-step walkthrough

1. Check for available updates

When an update is available, a green notification badge appears on the main rConfig dashboard.

2. Open the Update interface

1. Select System Settings from the main navigation sidebar.
2. Under System Management, select Update.

3. Review the available release

The Update interface has three tabs:

• Check Updates: Shows your installed version and available release version
• Instructions: Provides the exact commands to run for your operating system
• Release Notes: Details new features, enhancements, and resolved issues

Select Check Updates to confirm an update is available. If the interface shows “System is up to date” with a green indicator, no action is required.

4. Read the release notes

Select Release Notes and review the changes included in the new version. Note any breaking changes or integration impacts before proceeding.

5. Run the update commands

Select Instructions to see the commands for your operating system. Copy and run the commands appropriate for your deployed OS (RHEL/CentOS/Rocky Linux/Alma Linux or Ubuntu).

Note

The update interface generates OS-specific command sequences. Always run the commands that match your deployed operating system, not the alternative set.

6. Verify the update

After the commands complete, return to Check Updates. The installed version number should reflect the new release, and the status should show “System is up to date.”

Run a post-update smoke test: log in, navigate to a device, and confirm configuration backups are still accessible.

Common gotchas

Common update mistakes

• Non-standard install path: Running the update from a path other than /var/www/html/rconfig8 will fail. Verify your path with ls /var/www/html/rconfig8 before starting.
• No backup: Proceeding without a tested backup is the single highest-risk action. A failed update without a backup can result in unrecoverable data loss.
• Wrong user: Running update commands as the wrong system user can cause permission errors or leave files owned incorrectly. Confirm the correct user with your system administrator or check the Instructions tab.
• Wrong OS commands: The update interface shows both RHEL-family and Ubuntu commands. Running the wrong set on your OS will produce errors.

What’s next

• V8 Pro Installation - Review the original installation steps if you are rebuilding or moving the system
• Docker deployment for rConfig V8 Pro - If you operate a containerised stack, review the Docker-specific update guidance
• rConfig V8 Features Overview - Understand what capabilities the latest release adds