Upgrade rConfig V8 Core to V8 Pro

Upgrade rConfig V8 Core to V8 Pro

After reading this page, you can move an existing rConfig V8 Core install onto the V8 Pro edition without losing your devices, configs, or backups. This is a cross-edition upgrade: V8 Pro is the commercial edition documented separately at docs.rconfig.com, and this page bridges you from Core to that edition.

When to use this

Use this guide when you already run rConfig V8 Core and want the additional features of V8 Pro, such as compliance policies, change management, and the wider integration set. The procedure installs V8 Pro alongside your existing Core data on the same server, then migrates your Core database and storage into it.

Prerequisites

Before you start, make sure you have:

• A valid V8 Pro license. Purchase one at rconfig.com/pricing if you do not already have one.
• A working rConfig V8 Core install. See Install rConfig V8 Core if you need to confirm your current setup.
• A full backup of your V8 Core database and storage folders. The first step below covers this, and System backups explains rConfig’s built-in backup options.
• Root or sudo access to the server, and the V8 Core APP_KEY and database password to hand.

This page targets the Pro edition

V8 Pro is a different edition to V8 Core. Pro-specific setup and feature detail live at docs.rconfig.com. This page only covers the move from Core to Pro.

Back up rConfig V8 Core

1. Dump the V8 Core database to a dated file.

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

2. Archive the V8 Core application directory.

tar -czf /root/rconfig-v8-core-backup-$(date +%Y%m%d).tar.gz /var/www/html/rconfig

Update your operating system

1. Update and upgrade your OS packages. This may take a few minutes. Let both commands finish.

For RHEL / CentOS / Rocky / AlmaLinux:

yum -y update
yum -y upgrade

For Ubuntu / Debian:

apt-get update
apt-get upgrade -y

2. If you hit a MariaDB repository error during the update, remove the stale MariaDB repo file and 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

1. On the same server as V8 Core, install V8 Pro by following the V8 Pro installation guide on docs.rconfig.com (Pro edition).

2. Open the UI once the installer finishes. The new V8 Pro UI loads with a blank default data set (no devices or configs yet). You migrate your Core data in the next steps.

Update the V8 Pro .env file

1. Open the V8 Pro .env file.

vi /var/www/html/rconfig8/current/.env

2. Copy the values below from your V8 Core .env into the V8 Pro .env, commenting out the original Pro parameters. Take particular care with DB_PASSWORD.

#APP_KEY=base64:xxxxxxxxxxxxxxxxxV8PROKEYxxxxxxxxxxxxxxxxxxx%253D
APP_KEY=base64:xxxxxxxxxxxxxxxV8COREKEYxxxxxxxxxxxxxxxxxxxxxxxx=

#APP_URL=https://rconfig.yourdomain.com
APP_URL=https://rconfig.yourdomain.com

#DB_DATABASE=rconfig456
DB_DATABASE=rconfig

#DB_USERNAME=rconfig_user
DB_USERNAME=root

#DB_PASSWORD=V8ProPassword
DB_PASSWORD=xxxxxxxxxxxxxxxV8COREDBPASSxxxxxxxxxxxxxxxxxxxxxxxx

#DB_HOST=localhost
DB_HOST=localhostOrOtherHost

#DB_PORT=3306
DB_PORT=3306

APP_KEY must match exactly

Copy the exact APP_KEY from V8 Core into V8 Pro. This key encrypts your stored data, and access to existing encrypted values fails if the keys differ.

Migrate the database

1. Clear the application state and run the migrations against your V8 Core database. You should see several tables created in the output.

cd /var/www/html/rconfig8/current
php artisan rconfig:clear-all
php artisan migrate --force

Copy the V8 Core backup files to V8 Pro

1. Copy the storage contents from V8 Core into V8 Pro so all your existing backups are available.

yes | cp -R /var/www/html/rconfig/storage/* /var/www/html/rconfig8/current/storage/

Clear the application cache

1. Clear the cache so the running instance uses the V8 Pro codebase.

cd /var/www/html/rconfig8/current
php artisan rconfig:clear-all

Verify the backup storage directory and permissions

1. Create the backup storage directory, set its permissions, and clear the cache.

For RHEL / CentOS / Rocky / AlmaLinux:

cd /var/www/html/rconfig8/current
mkdir -p storage/app/rconfig/backups
chmod 0755 storage/app/rconfig/backups
chown -R apache:apache storage bootstrap/cache
php artisan rconfig:clear-all

For Ubuntu / Debian:

cd /var/www/html/rconfig8/current
mkdir -p storage/app/rconfig/backups
chmod 0755 storage/app/rconfig/backups
chown -R www-data:www-data storage bootstrap/cache
php artisan rconfig:clear-all

Fix OAuth key permissions

1. Set the correct permissions and ownership on the OAuth authentication keys.

For RHEL / CentOS / Rocky / AlmaLinux:

cd /var/www/html/rconfig8/current
chmod 600 storage/oauth-private.key
chmod 600 storage/oauth-public.key
chown apache:apache storage/oauth-*.key

For Ubuntu / Debian:

cd /var/www/html/rconfig8/current
chmod 600 storage/oauth-private.key
chmod 600 storage/oauth-public.key
chown www-data:www-data storage/oauth-*.key

Restart services

1. Restart Apache, Supervisor, and PHP-FPM to apply all changes.

For RHEL / CentOS / Rocky / AlmaLinux:

systemctl restart httpd
systemctl restart supervisord
systemctl restart php-fpm

For Ubuntu / Debian:

systemctl restart apache2
systemctl restart supervisor
systemctl restart php8.4-fpm

Access V8 Pro

1. Open your rConfig URL in a browser, then press CTRL+SHIFT+R to hard refresh and clear the old assets.

Common gotchas

Watch these during the upgrade

• A mismatched APP_KEY is the most common failure. Copy it byte for byte from V8 Core, or existing encrypted data will not decrypt.
• Skipping the storage copy step leaves V8 Pro with no historical backups. Run the cp -R step before you rely on past configs.
• Wrong ownership on storage and bootstrap/cache causes blank pages or permission errors. Use apache on RHEL-family systems and www-data on Ubuntu and Debian.
• Always take the database and directory backups in the first step before making any changes, so you can roll back to V8 Core if needed.

Need help?

Contact rConfig support if you run into any problems during the upgrade.

What’s next

• Explore the V8 Pro documentation (Pro edition) to set up the features your new license unlocks.
• Review V8 Core system backups so your migrated data stays protected.
• Manage your devices and configs to confirm everything migrated as expected.