V8 Core to V8 Pro
rConfig V8 Core to V8 Pro Upgrade
Section titled “rConfig V8 Core to V8 Pro Upgrade”rConfig V8 Core is our open source free version of rConfig. It does not have all enterprise features of rConfig V8 Professional, but it has the core capabilities and config backup features. Many users transition from V8 Core to V8 Professional to take advantage of the additional features. This guide will walk you through the upgrade process.
This guide assumes you’re running V8 Core and you have a valid V8 Professional license. Throughout this guide we may refer you to other parts of the documentation for specific instructions. Please follow the instructions carefully.
Backup rConfig V8 Core
Section titled “Backup rConfig V8 Core”✅ Ensure you have a full system backup of rConfig V8 Core database and storage folders.
# Backup databasemysqldump -u YOUR_DB_USER -p YOUR_DATABASE > /root/rconfig-v8-core-backup-$(date +%Y%m%d).sql
# Backup rConfig directorytar -czf /root/rconfig-v8-core-backup-$(date +%Y%m%d).tar.gz /var/www/html/rconfigUpdate your OS
Section titled “Update your OS”✅ This may take a few minutes, but let it finish for both commands below.
For RHEL / CentOS / Rocky / AlmaLinux:
yum -y updateyum -y upgradeFor Ubuntu / Debian:
apt-get updateapt-get upgrade -yIf you get a MariaDB error during the update, please see the note below.
If you get this error during the update, please run the following command and then re-run the update command above.
For RHEL / CentOS / Rocky / AlmaLinux:
rm -fr /etc/yum.repos.d/MariaDB*For Ubuntu / Debian:
rm -fr /etc/apt/sources.list.d/mariadb*Run the V8 Pro Installer
Section titled “Run the V8 Pro Installer”✅ On the same server where you have rConfig V8 Core installed, install rConfig V8 Professional. Follow the instructions in the V8 Pro Installation Guide. Once this is completed, you should try to access the UI, and the new V8 Professional UI should be displayed with a blank default data set (i.e. no devices or configs).
Update ENV File
Section titled “Update ENV File”✅ Copy the following .env file parameters from V8 Core to V8 Pro .env file (comment out the V8 Pro parameters). Take care in updating the DB_PASSWORD parameter.
vi /var/www/html/rconfig8/current/.envUpdate the following parameters:
#APP_KEY=base64:xxxxxxxxxxxxxxxxxV8PROKEYxxxxxxxxxxxxxxxxxxx%253DAPP_KEY=base64:xxxxxxxxxxxxxxxV8COREKEYxxxxxxxxxxxxxxxxxxxxxxxx=
#APP_URL=https://rconfig.yourdomain.comAPP_URL=https://rconfig.yourdomain.com
#DB_DATABASE=rconfig456DB_DATABASE=rconfig
#DB_USERNAME=rconfig_userDB_USERNAME=root
#DB_PASSWORD=V8ProPasswordDB_PASSWORD=xxxxxxxxxxxxxxxV8COREDBPASSxxxxxxxxxxxxxxxxxxxxxxxx
#DB_HOST=localhostDB_HOST=localhostOrOtherHost
#DB_PORT=3306DB_PORT=3306Migrate the database
Section titled “Migrate the database”✅ Now migrate the database from V8 Core to V8 Pro. You should see several tables being created in the output.
cd /var/www/html/rconfig8/currentphp artisan rconfig:clear-allphp artisan migrate --forceCopy the V8 Core backup files to V8 Pro
Section titled “Copy the V8 Core backup files to V8 Pro”✅ Copy the files from V8 Core to V8 Pro. This will ensure you have all your backups in V8 Pro.
yes | cp -R /var/www/html/rconfig/storage/* /var/www/html/rconfig8/current/storage/Clear the application cache
Section titled “Clear the application cache”✅ Clear the application cache to ensure you are using the V8 Pro codebase.
cd /var/www/html/rconfig8/currentphp artisan rconfig:clear-allVerify Backup Storage directory and permissions
Section titled “Verify Backup Storage directory and permissions”✅ Run the following scripts to ensure the backup storage directory is created and has the correct permissions.
For RHEL / CentOS / Rocky / AlmaLinux:
cd /var/www/html/rconfig8/currentmkdir -p storage/app/rconfig/backupschmod 0755 storage/app/rconfig/backupschown -R apache:apache storage bootstrap/cachephp artisan rconfig:clear-allFor Ubuntu / Debian:
cd /var/www/html/rconfig8/currentmkdir -p storage/app/rconfig/backupschmod 0755 storage/app/rconfig/backupschown -R www-data:www-data storage bootstrap/cachephp artisan rconfig:clear-allFix OAuth Key Permissions
Section titled “Fix OAuth Key Permissions”✅ Set the correct permissions for OAuth authentication keys.
For RHEL / CentOS / Rocky / AlmaLinux:
cd /var/www/html/rconfig8/currentchmod 600 storage/oauth-private.keychmod 600 storage/oauth-public.keychown apache:apache storage/oauth-*.keyFor Ubuntu / Debian:
cd /var/www/html/rconfig8/currentchmod 600 storage/oauth-private.keychmod 600 storage/oauth-public.keychown www-data:www-data storage/oauth-*.keyRestart Services
Section titled “Restart Services”✅ Restart Apache and Supervisor to apply all changes.
For RHEL / CentOS / Rocky / AlmaLinux:
systemctl restart httpdsystemctl restart supervisordsystemctl restart php-fpmFor Ubuntu / Debian:
systemctl restart apache2systemctl restart supervisorsystemctl restart php8.4-fpmAccess V8 Professional
Section titled “Access V8 Professional”Open rConfig URL in your browser. CTRL+SHIFT+R to hard refresh the browser
rConfig V8 Professional Login Page