Support / Royal MCP Pro / License Activation Issues

License Activation Issues

You entered your purchase email + license key on the Royal MCP Pro license page and hit Activate, but activation didn't succeed. This doc walks through the exact error paths the licensing SDK returns and the fix for each one. Most activation failures fall into one of five categories.

Quick sanity check first
  • Both fields filled? The activate form needs Purchase Email and License Key. Empty either one fails immediately.
  • Correct plugin? A GuardPress or SiteVault license won't activate Royal MCP Pro. Each product has its own license.
  • Copied cleanly? Leading/trailing whitespace is stripped by the SDK, but a partially-copied key (missing the last character) fails as if it were a different key.

If none of those apply, work through the error-code sections below.

Where the error message appears

After you click Activate, the SDK either:

  • Shows an inline admin notice at the top of the license page ("License activation failed" + a specific reason), OR
  • Returns a JSON error to the AJAX call ("License server error. Please try again."), OR
  • Silently keeps the license page in its unactivated state (page reloads with no notice) — this is rare and usually indicates a nonce or session issue; try again.

The exact wording of the reason is what tells you which category below applies.

The five activation error categories

Category 1: "Please enter a license key" / empty submission

SDK error code: empty_license. You submitted the form with the License Key field blank. If the Purchase Email field was pre-filled from a prior session, this can look like the form is filled when only half of it actually is.

Fix

Copy the license key from your purchase confirmation email or from My Account → Licenses. Paste into the License Key field. Ensure both fields have values before clicking Activate.

Category 2: "License activation failed" / server rejected the key

SDK error code: activation_failed. The licensing server received your request and answered — but the answer was "no." This is the most common category. The specific reason is usually included in the admin notice text after the "License activation failed" prefix.

Sub-cause 2a: Key exists but doesn't match this plugin

You entered a GuardPress / SiteVault / ForgeCache / SEObolt / etc. key on the Royal MCP Pro license page. Different products, different keys. Check your purchase-confirmation email for the key that starts with the Royal MCP Pro product line item.

Sub-cause 2b: Purchase email doesn't match this key

The email on your order and the email you're entering must match. Common gotcha: you bought under you@work.example but the license page has you@personal.example pre-filled from a different site's activation. Correct the email field and re-submit.

Sub-cause 2c: Key is expired

Your license expired (Personal / Professional / Agency licenses all renew annually — the Founding Members tier is a rate lock at $79/yr, not a lifetime license). Renew from My Account → Subscriptions, then re-activate on the site.

Sub-cause 2d: Activation limit reached

Your tier's activation slots are used up (Personal: 1 site, Professional: 5 sites, Agency: 100 sites). Deactivate a site you no longer need from My Account → Licenses, then re-activate here. See License & Renewals for the full slot-management walkthrough.

Category 3: "License server error" / transport failure

SDK error code: api_error. The plugin sent the activation request to my.royalplugins.com, but the request came back with a non-200 HTTP status or never got a response at all. This is a host-layer / network issue, not a license problem.

Diagnosis

Try the same request from another network. If activating from a different location (mobile hotspot, different site) works with the same email + key, the issue is on the failing site's outbound path.

Common causes on the failing site

  • Host WAF blocking outbound POSTs to unfamiliar domains. Ask your host to allowlist my.royalplugins.com for outbound HTTPS from your site.
  • Server-level firewall (fail2ban / CSF) throttling repeat outbound requests. First activation attempt goes through; retries within a short window get blocked.
  • DNS resolution failure for my.royalplugins.com from the server (rare but happens on locked-down VPS setups). Check with ping my.royalplugins.com from the server if you have SSH access.
  • Outdated cURL / OpenSSL on the server refusing modern TLS. Very old PHP setups (7.2 or earlier on hosts that haven't updated their stack) sometimes fail here.
  • Two stacked 10-second timeouts exactly matching the SDK's total. If the server takes exactly 20+ seconds to respond, the SDK gives up. Retry — this is usually transient.

Category 4: "Invalid response from license server" / CDN mangled response

SDK error code: json_error. The licensing server responded with HTTP 200 but the body wasn't JSON. Something on the response path replaced or wrapped the actual JSON with HTML — almost always a CDN / WAF interstitial page.

Common signature

Response body starts with <!DOCTYPE html> or <html> instead of {"success":...}. Contains phrases like "Just a moment..." (Cloudflare challenge), "One moment, please..." (BitNinja WebShield), "Access denied" (Imunify360), or similar interstitial.

Root cause

The interstitial is being served by a security layer at your host or between your host and my.royalplugins.com — not by us. Your outbound request tripped their bot-detection ruleset. Same class of issue as the Royal MCP Free host-layer patterns; see Free Troubleshooting for full signature-matching detail.

Fix

Ask your host to allowlist your own server's outbound requests to my.royalplugins.com (specifically for POSTs to /wp-admin/admin-ajax.php with body param action=wpgenius_license). Retry activation after the allowlist is applied.

Category 5: Activation appeared to succeed but tools still show upgrade prompt

Not technically an activation failure — the license page shows the key as active, but Pro tools still return an "upgrade" prompt when called. Different diagnostic path.

Fix

See Upgrade Prompt with Valid License for the sibling-class-shadow diagnosis (usually another Royal Plugin loading first with a stale SDK copy).

Force a fresh check (deactivate + reactivate)

The SDK caches license validity for 24 hours to avoid hammering the licensing server on every admin page load. If you want to force a re-check right now (e.g., you just renewed and want the "expired" state to clear):

  1. Go to Royal MCP Pro → License in wp-admin
  2. Click Deactivate — this clears the local option AND the 24-hour "valid" transient
  3. Click Activate with the same email + key — forces a fresh server call and re-caches the result

This is the correct path to try before contacting support for "license says X but should say Y" issues.

Deactivation is non-blocking on the server side

The local plugin removes its license data immediately. The licensing server's slot-release call is fire-and-forget with a short timeout — the slot on my.royalplugins.com may take a few seconds to a minute to actually reclaim depending on server load. If you deactivate then immediately try to activate on a different site and hit an activation-limit error, wait 60 seconds and try again.

Still Stuck? Two-Step Support Path

If none of the five categories above match your symptom, work through these two steps in order.

Step 1: Cross-check on My Account

Go to My Account → Licenses and confirm:

  • The license key you're entering matches the one shown for Royal MCP Pro
  • The status is Active (not Expired or Cancelled)
  • The activation-count is below your tier's limit (e.g., 4/5 for Professional means 1 slot free)
  • The purchase email is what you're entering on the license page

If any of those don't match, the fix is on My Account, not the site.

Step 2: Email priority support

If My Account looks correct but activation on the site still fails, email priority support from your purchase email address at support@royalplugins.com. Priority email support is included with your license — typical response within 24 hours. Never include your license key in email; we look it up from your purchase address.

What to include in your email
  • The exact wording of the error notice / message on the license page
  • Your hosting provider (needed if the error looks like Category 3 or 4)
  • Royal MCP Pro version installed
  • WordPress + PHP versions
  • Whether the same key activated successfully on any other site — tells us if it's the key vs. this site's network
  • Screenshot of the license page after the failed activation attempt (with the notice visible)