Skip to content

How to activate rConfig with an offline license - rConfig V8

How to activate rConfig with an offline license

Section titled “How to activate rConfig with an offline license”

rConfig can be fully licensed on air-gapped or offline servers by importing a license file downloaded from portal.rconfig.com. No outbound internet connection is required after import.

Use this flow when your rConfig server has no outbound access to portal.rconfig.com. In online installs, the daily FetchLicenseInfoJob populates license data automatically — on air-gapped networks that job silently no-ops, leaving the About panel showing “Unknown”, “N/A”, and status “Inactive”. Offline activation resolves this without changing any firewall rules.

If your server can reach the portal, you do not need this page.

  • rConfig V8.2.2 or later
  • A user account with the setting.update permission
  • Access to portal.rconfig.com from any machine (not necessarily the rConfig server)
  • Your subscription must be active on the portal

Step 1 — Download your license file from the portal

Section titled “Step 1 — Download your license file from the portal”
  1. Log in to portal.rconfig.com on any machine with internet access.
  2. Navigate to Subscriptions and open your active subscription.
  3. Click Download offline license.
  4. Save the file — it is named rconfig-license.json.

The portal also offers a plain .env snippet if you prefer to paste rather than upload. Both contain the same data.


Step 2 — Open the Offline License importer in rConfig

Section titled “Step 2 — Open the Offline License importer in rConfig”
  1. In rConfig, navigate to Settings → About.
  2. Scroll to the Offline License section below the License Notice card.
  3. If the License Notice card shows “Inactive” with no data, a hint reading “Offline install? Import your license file from portal.rconfig.com” links directly to this section.

Choose one of two methods:

Section titled “Option A — Upload the JSON file (recommended)”
  1. Click Choose file in the Offline License section.
  2. Select the rconfig-license.json file you downloaded from the portal.
  3. Click Import.
  1. Open the .env snippet you copied from the portal.
  2. Paste the full block into the text area in the Offline License section.
  3. Click Import.

The importer reads only the eight RCONFIG_* license keys from a pasted block. Any other lines in the paste are silently ignored — pasting your full .env file will not overwrite unrelated settings.


After a successful import:

  • The License Notice card on the About panel refreshes automatically.
  • Fields previously showing “Unknown”, “N/A”, or ”—” populate with your subscription details.
  • Status changes from Inactive to Active.

No app restart is required.


The About card still shows “Unknown” after import

Section titled “The About card still shows “Unknown” after import”

The license cache may not have cleared. Run the following commands on the server, then reload the About panel:

Terminal window
php artisan config:clear
php artisan cache:forget rconfig_license_info

If the fields remain blank, restart the queue worker so any pending jobs pick up the new .env values:

Terminal window
php artisan queue:restart
Error messageCauseFix
sub_id is invalidThe file contains a placeholder value (0000000000)Download a fresh license file from the portal
sub_expiry must be a valid dateDate is not in d-m-Y formatDo not manually edit the license file
sub_status must be activeSubscription is suspended or expiredRenew the subscription in the portal before importing
device_count must be at least 1Invalid device count in fileDownload a fresh license file from the portal

Confirm the web server process has write access to the .env file on disk:

Terminal window
ls -la /var/www/html/rconfig/.env

The file should be owned by or writable by the web server user (e.g. www-data).

Import an up-to-date license file before enabling outbound access. When the server comes online, FetchLicenseInfoJob will overwrite the .env values with the latest data from the portal on its next run — this is intentional. The RCONFIG_API_TOKEN written during offline import is the token the portal currently considers valid and will be used for the first online sync.