rConfig V6 Core to V8 Core Upgrade

rConfig V6 Core to V8 Core Upgrade

Upgrading from rConfig V6 Core to V8 Core utilizes a streamlined automated migration process. A fully automated upgrade script is provided for CentOS, RHEL, Rocky Linux, AlmaLinux, and Ubuntu-based systems, managing all required migration procedures. Review the V8 Core 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. The upgrade script creates automatic backups, but manual backups are strongly recommended.

---

Prerequisites

Before beginning the upgrade, ensure the following requirements are met:

System Requirements

• ✅ Root access to your server
• ✅ Working rConfig V6 Core installation at /var/www/html/rconfig
• ✅ Git installed and repository initialized
• ✅ PHP 8.4 or the ability to upgrade (script handles this automatically)
• ✅ Database credentials accessible in .env file
• ✅ Recent manual backup of your system (recommended)

Supported Operating Systems

• Rocky Linux 9.x or higher
• AlmaLinux 9.x or higher
• CentOS Stream 9 or higher
• RHEL 9.x or higher
• Ubuntu 20.04 or higher

---

Pre-Upgrade Checklist

Complete All Steps Before Upgrading

Failure to complete pre-upgrade verification may result in data loss or upgrade failure.

Step 1: Create Manual Backups

# Backup database
mysqldump -u YOUR_DB_USER -p YOUR_DATABASE > /root/rconfig-backup-$(date +%Y%m%d).sql

# Backup rConfig directory
tar -czf /root/rconfig-backup-$(date +%Y%m%d).tar.gz /var/www/html/rconfig

# Verify backups exist
ls -lh /root/rconfig-backup-*

Step 2: Verify Database Credentials

# Test database connection
cd /var/www/html/rconfig
source .env
mysql -u"$DB_USERNAME" -p"$DB_PASSWORD" -h"$DB_HOST" "$DB_DATABASE" -e "SHOW TABLES;"

Note

If the database connection fails, correct your credentials in /var/www/html/rconfig/.env before proceeding.

Step 3: Verify Git Repository Status

cd /var/www/html/rconfig

# Check current branch
git branch

# Check for uncommitted changes
git status

# If you have local modifications you want to preserve:
git add .
git commit -m "Local changes before v8 upgrade"

---

Upgrade Procedures

RHEL / CentOS / Rocky / AlmaLinux

This may take 5-15 minutes to complete

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

cd /root
wget https://dl.rconfig.com/downloads/upgrade-v6-to-v8-core.sh -O upgrade-v6-to-v8-core.sh
chmod +x upgrade-v6-to-v8-core.sh
sudo ./upgrade-v6-to-v8-core.sh

The script will prompt for confirmation:

⚠️  IMPORTANT WARNINGS ⚠️
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

This script will:
  1. Backup your database, .env file, and storage
  2. Upgrade PHP to 8.4 (if needed)
  3. Upgrade rConfig v6 → v8
  4. Create new .env from .env.example with your DB settings
  5. Setup Apache and Supervisor

Backup location: /root/rconfig-v6-backup-TIMESTAMP
Log file: /var/log/rconfig-upgrade-TIMESTAMP.log

⚠️  DO NOT INTERRUPT THIS PROCESS ⚠️

Have you backed up your system? (yes/no):

Type yes and press Enter to continue.

Ubuntu / Debian

This may take 5-15 minutes to complete

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

cd /root
wget https://dl.rconfig.com/downloads/upgrade-v6-to-v8-core.sh -O upgrade-v6-to-v8-core.sh
chmod +x upgrade-v6-to-v8-core.sh
sudo ./upgrade-v6-to-v8-core.sh

The script will prompt for confirmation:

⚠️  IMPORTANT WARNINGS ⚠️
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

This script will:
  1. Backup your database, .env file, and storage
  2. Upgrade PHP to 8.4 (if needed)
  3. Upgrade rConfig v6 → v8
  4. Create new .env from .env.example with your DB settings
  5. Setup Apache and Supervisor

Backup location: /root/rconfig-v6-backup-TIMESTAMP
Log file: /var/log/rconfig-upgrade-TIMESTAMP.log

⚠️  DO NOT INTERRUPT THIS PROCESS ⚠️

Have you backed up your system? (yes/no):

Type yes and press Enter to continue.

---

Upgrade Completion

Upon successful completion, you will see:

╔════════════════════════════════════════════════════════════════╗
║                                                                ║
║               ✅ UPGRADE COMPLETED SUCCESSFULLY! ✅              ║
║                                                                ║
╚════════════════════════════════════════════════════════════════╝

Upgrade Summary:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  ✓ Upgraded from: rConfig v6 Core
  ✓ Upgraded to:   rConfig v8 Core
  ✓ Backup location: /root/rconfig-v6-backup-TIMESTAMP
  ✓ Log file: /var/log/rconfig-upgrade-TIMESTAMP.log

Next Steps:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  1. Access rConfig v8:
     http://your-server.domain.com

  2. Login with your existing credentials

  3. Verify your devices and configurations

---

Post-Upgrade Verification

Browser Cache

Execute a hard browser refresh (CTRL+SHIFT+R or CMD+SHIFT+R) after accessing the system to clear cached assets.

Step 1: Access rConfig V8

Navigate to your rConfig URL in a web browser:

http://your-server.domain.com

You should see the new V8 Core interface with modern UI design.

rConfig V8 Core Authentication Interface

Step 2: Login with Existing Credentials

Use your existing V6 Core credentials to authenticate. All users, roles, and permissions are preserved during the upgrade.

Step 3: Verify System Data

After logging in, verify the following:

• ✅ Devices: Confirm all network devices are present in inventory
• ✅ Configurations: Verify device configurations are accessible
• ✅ Scheduled Tasks: Check that scheduled polling tasks are active
• ✅ Users: Confirm all user accounts are accessible
• ✅ Tags & Categories: Verify organizational structure is intact

---

Troubleshooting

Log Files

All upgrade operations are logged. Review logs for detailed troubleshooting:

• Upgrade log: /var/log/rconfig-upgrade-TIMESTAMP.log
• Application log: /var/www/html/rconfig/storage/logs/laravel.log

Issue: HTTP 500 Internal Server Error

Symptoms: Application loads but displays HTTP 500 error

Solution:

cd /var/www/html/rconfig

# Fix OAuth key permissions
chmod 600 storage/oauth-private.key
chmod 600 storage/oauth-public.key
chown apache:apache storage/oauth-*.key  # RHEL/CentOS/Rocky
# OR
chown www-data:www-data storage/oauth-*.key  # Ubuntu

# Clear application cache
php artisan rconfig:clear-all

# Restart services
systemctl restart httpd      # RHEL/CentOS/Rocky
systemctl restart apache2    # Ubuntu
systemctl restart supervisord

Issue: Page Loads but No Data Displayed

Symptoms: Interface loads but devices, configurations, or other data is missing

Solution:

cd /var/www/html/rconfig

# Verify database migrations
php artisan migrate:status

# Run migrations if any are pending
php artisan migrate --force

# Check application logs
tail -100 storage/logs/laravel.log

Issue: PHP Version Error During Upgrade

Symptoms: Script fails with PHP version compatibility error

Solution:

RHEL / CentOS / Rocky / AlmaLinux

cd /tmp
wget https://dl.rconfig.com/downloads/php-updates/centos-php8-update.sh
chmod +x centos-php8-update.sh
sudo ./centos-php8-update.sh

# Verify PHP version
php -v

Ubuntu / Debian

cd /tmp
wget https://dl.rconfig.com/downloads/php-updates/ubuntu-php8-update.sh
chmod +x ubuntu-php8-update.sh
sudo ./ubuntu-php8-update.sh

# Verify PHP version
php -v

Issue: Database Connection Failure

Symptoms: Script fails at database verification step

Solution:

# Verify .env file contains correct credentials
cat /var/www/html/rconfig/.env | grep DB_

# Test database connection manually
cd /var/www/html/rconfig
source .env
mysql -u"$DB_USERNAME" -p"$DB_PASSWORD" -h"$DB_HOST" "$DB_DATABASE" -e "SELECT VERSION();"

# If connection fails, update .env with correct credentials
nano /var/www/html/rconfig/.env

---

Rollback Procedures

Last Resort Only

Rollback procedures should only be executed if the upgrade fails catastrophically and the system is non-functional. Contact support before proceeding with rollback.

If you must rollback to V6 Core:

# Stop services
systemctl stop httpd supervisord      # RHEL/CentOS/Rocky
# OR
systemctl stop apache2 supervisor     # Ubuntu

# Restore database from backup
mysql -u YOUR_DB_USER -p YOUR_DATABASE < /root/rconfig-v6-backup-TIMESTAMP/rconfig-database.sql

# Restore .env file
cp /root/rconfig-v6-backup-TIMESTAMP/.env /var/www/html/rconfig/.env

# Restore storage directory
rm -rf /var/www/html/rconfig/storage
cp -a /root/rconfig-v6-backup-TIMESTAMP/storage /var/www/html/rconfig/

# Checkout V6 branch
cd /var/www/html/rconfig
git checkout main  # Or your V6 branch name

# Reinstall V6 dependencies
composer install --no-dev --optimize-autoloader

# Clear cache
php artisan config:clear
php artisan cache:clear

# Restart services
systemctl start httpd supervisord      # RHEL/CentOS/Rocky
# OR
systemctl start apache2 supervisor     # Ubuntu

Getting Help

Note

For upgrade assistance or troubleshooting support beyond this documentation, contact rConfig support services.

Support Resources

• 📚 Documentation: https://v8coredocs.rconfig.com
• 💬 Community Forums: https://github.com/rconfig/rconfig/discussions/categories/general
• 🐛 GitHub Issues: https://github.com/rconfig/rconfig/issues

Before Contacting Support

When requesting assistance, provide:

1. Complete upgrade log: /var/log/rconfig-upgrade-TIMESTAMP.log
2. Laravel application log: /var/www/html/rconfig/storage/logs/laravel.log
3. Operating system and version: cat /etc/os-release
4. PHP version: php -v
5. Git branch information: cd /var/www/html/rconfig && git branch

Note

This upgrade guide is maintained by the rConfig development team. For the latest updates and version-specific information, visit the official documentation at https://docs.rconfig.com