Licence problems after activating

This page covers a licence that activated once and then misbehaved. If your key is being refused outright and has never worked, start at activate your licence, which lists the five common causes of a rejected key.

Check the current state first, at Reign Settings > License. What that screen says shapes everything below.

No update notice, but the licence looks active

Confirm there is actually a newer version. The Reign version you are running is shown next to the wordmark at the top of Reign Settings, and in System status under Tools.

If a newer release exists and WordPress is not offering it:

WordPress caches update checks. The check runs periodically, not on every page load. Go to Dashboard > Updates and select Check again, which forces it.

Your site cannot reach the licence server. Update checks are outbound HTTPS requests to wbcomdesigns.com. A firewall, a security plugin, or a host that blocks outbound requests will silently produce “no updates available” forever. Ask your host to confirm outbound HTTPS is allowed.

A maintenance or management plugin is suppressing update notices. Some plugins hide theme updates by design. Check anything that manages updates across sites.

The licence keeps deactivating itself

Almost always the seat count.

A licence covers a set number of production sites. If you have activated on more sites than the tier allows, activations start displacing each other. Review the active sites in your account and deactivate any you no longer use.

Staging and local copies should not consume a seat, but they can if the staging site presents itself with a different URL that the licence server sees as a new production site. If you clone production to staging, deactivate the licence on the clone.

A subdomain running its own WordPress install counts as a separate site.

One-click installs are still off

The Extend screen’s one-click installs need an active licence. If the licence reads active and installs still fail:

The install needs the right capability. Installing plugins requires the install_plugins capability. An administrator on a single site has it. On multisite, plugin installation is restricted to network administrators, so a site administrator will not see working install buttons.

The filesystem is not writable. If WordPress asks for FTP credentials when installing any plugin, that is a file-permissions problem on the server and not specific to Reign. Your host can fix the ownership on wp-content.

The download itself failed. A blocked outbound request produces an install that starts and fails. The same connectivity check as above applies.

After moving the site

Migrating to a new domain, or from staging to live, changes the URL the licence is registered against.

Deactivate the licence on the old URL if you still have access, then activate it again on the new one. If you no longer have access to the old site, deactivate that site from your account.

Report it

If the licence reads active, the site can reach wbcomdesigns.com, and updates still do not appear, open a ticket with your System status from Reign Settings > Tools, the site URL, and the exact wording shown on the License screen.