rConfig V7 to V8 Professional Upgrade: Complete Migration Guide

rConfig V7 to V8 Professional Upgrade: Complete Migration Guide

Upgrading from rConfig V7 Professional to V8 Professional utilizes a streamlined automated migration process. Fully automated upgrade scripts are provided for CentOS, RHEL, Rocky Linux, and Ubuntu-based systems, managing all required migration procedures. Review the V8 Pro installation documentation if you plan to deploy clean environments alongside the upgrade.

Critical: Backup Requirements

Prior to commencing upgrade procedures, verify that complete system and database backups have been created and tested.

rConfig Vector Customers

The Vector upgrade process follows separate procedures. Vector customers should consult the Vector Upgrade Guide for platform-specific migration instructions.

---

Upgrade Procedures

RHEL / CentOS / Rocky Linux

This may take a few minutes to complete

Keep your terminal session active until the script completes. Do not interrupt the process.

cd /home
wget https://dl.rconfig.com/downloads/upgrade-to-rconfig8.sh -O upgrade-to-v8.sh
chmod +x upgrade-to-v8.sh
sudo ./upgrade-to-v8.sh YourSecureToken1234 v8

Ubuntu / Debian

This may take a few minutes to complete

Keep your terminal session active until the script completes. Do not interrupt the process.

cd /home
wget https://dl.rconfig.com/downloads/upgrade-to-rconfig8-ubuntu.sh -O upgrade-to-v8.sh
chmod +x upgrade-to-v8.sh
sudo ./upgrade-to-v8.sh YourSecureToken1234 v8

Note

Replace YourSecureToken1234 with your API authentication token from the rConfig portal.

---

Database Path Update Procedure

Following upgrade script completion, update legacy directory path references in the database that reference rconfig5, rconfig6, or rconfig7 directories:

cd /var/www/html/rconfig8/current
php artisan rconfig:updatedb8

Web Server Configuration

Caution

If HTTP 404 errors occur following the upgrade, web server configuration updates may be required. Apache or Nginx configurations must be updated to reference the new rConfig V8 directory structure.

For Apache deployments, verify DocumentRoot references /var/www/html/rconfig8/current/public. For Nginx deployments, update the root directive accordingly.

Verify current configuration:

# Apache Ubuntu
apache2ctl -S

# Apache RHEL/CentOS/Rocky
httpd -S

# Example output:
# VirtualHost configuration. Verify each VirtualHost for correct path configuration:
10.1.1.2:443           vega.rconfig.com (/etc/httpd/sites-enabled/vega.rconfig.com-le-ssl.conf:3)
*:443                  vega.rconfig.com (/etc/httpd/conf.d/ssl.conf:40)
*:80                   vega.rconfig.com (/etc/httpd/sites-enabled/vega.rconfig.com.conf:2)

For each virtual host configuration, update the DocumentRoot directive:

# Update rconfig7 references to rconfig8

RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
<IfModule mod_ssl.c>
<VirtualHost v8demo.rconfig.com:443>
        ServerName v8demo.rconfig.com
        ServerAlias v8demo.rconfig.com
        DocumentRoot /var/www/html/rconfig8/public
        <Directory "/var/www/html/rconfig8/public">
                Options Indexes FollowSymLinks MultiViews
                Order allow,deny
                Allow from all
                AllowOverride All
                Require all granted
                Satisfy Any
        </Directory>

    SSLEngine on
    SSLCertificateFile  /etc/pki/tls/certs/cert.crt
    SSLCertificateKeyFile /etc/pki/tls/private/key.key

    SSLProtocol             all -SSLv3 -TLSv1 -TLSv1.1
    SSLCipherSuite          PROFILE=SYSTEM

</VirtualHost>
</IfModule>

---

Upgrade Completion

Upon successful completion of upgrade procedures:

• Your rConfig system is now operating on V8 Professional
• Access the system using your existing rConfig URL
• Execute a hard browser refresh (CTRL+SHIFT+R or CMD+SHIFT+R) following the upgrade to clear cached assets

rConfig V8 Authentication Interface

Note

For upgrade assistance or troubleshooting support, contact rConfig professional support services.