Activation, expiry and updates

Activate a site once

Assign a production site through your customer account or private purchase page. Open RedirectNest → License & updates to reach the Site connection screen. Copy its private key into Site-specific install key, review the connection consent and choose Connect site. A connected installation keeps key replacement under Replace the connection key. First activation requires current entitlement; every WordPress subsite counts as a site. One associated non-public staging installation is included per production site.

The key and response must match the assigned site and environment during both activation and refresh. Use the production assignment for the production installation and its associated staging assignment for staging. Check the WordPress Site Address and environment if activation reports a mismatch.

Keep using installed features

Ordinary annual expiry does not disable successfully activated Pro features on that installation. Renew for new downloads, updates and new activations. Service outages do not erase a previously verified activation. Refunds, disputes, releases and explicit revocation are separate.

Advanced redirects require Pro to remain installed and active. If Pro is removed or inactive, those rules stay saved but do not run. Free can still pause, delete, export and recover them; restoring compatible Pro resumes their matching.

Move carefully

Under License & updates, expand Release or remove this connection and use Release remote entitlement on the old installation before transferring its allowance. Releasing or replacing a key can block new Pro work on the old site after verification. Existing redirects remain. Keep the private key private and never use one production-site key for unrelated sites.

If another administrator replaces the local key while a release request is in progress, the replacement connection is preserved. Reload the Site connection screen to review the current key before another action.

Use the matched current pair

For a fresh installation, use Free 1.1.2 first, then Pro 1.1.2. For an existing pair, install Pro 1.1.2 FIRST, then Free 1.1.2, without uninstalling. WordPress 6.7+ and PHP 8.1+ are required. Free 1.1.2 pauses Pro versions older than 0.9.0. The Pro 1.1.2 loader supports Free 0.7.1 or newer only for the manual Pro-first update transition. Its new workflows and signed automatic update require Free 0.10.0. Complete both ZIP updates to the matched pair.

After the 0.7.1 storage upgrade, never downgrade either edition below 0.7.1. If Free is unavailable, restore a compatible Free installation before managing Pro. A failed service refresh does not establish that a new installation has been activated. Follow the paired update steps.