Skip to main content

My site key doesn't work

If the WP-Script Core dashboard rejects your site key, or a previously connected site suddenly shows the activation screen again, the error message returned by the server tells you exactly what's wrong. Here's what each one means and how to fix it.

What happens when a site key is rejected

Whenever the server rejects a site key (on the errors below), WP-Script Core clears the site key, the connected products, and the signature it had stored locally. This is why a rejected site key doesn't just fail once: the site disconnects entirely until you paste a valid site key back into the dashboard.

1. "Unknown site key."​

The server doesn't recognize this site key at all.

Common causes:

  • Typo when pasting the key. Go back to My Account → Sites on wp-script.com, copy the key again, and paste it carefully into the Paste your site key here field.
  • The key was never generated, or was generated for a different site. Each site key is tied to one specific site entry in your account. Go to My Account → Sites, find (or add) the site you're activating, and use the key generated for that entry.
  • You pasted your account-wide license key by mistake. License keys start with wpscript_, site keys start with wpssite_. If you still have your old license key saved somewhere, go to My Account → Sites and generate a proper site key instead.
  • The site was removed from your account. See Managing your site keys for what happens when a site is deleted.

2. "This site's URL doesn't match the one registered for this site key."​

A site key is registered against the exact URL of the site it was generated for. When WP-Script Core checks in, it sends the site's current URL, and the server compares it against the one on record. If they don't match, you get a 403.

This happens in a few concrete situations:

  • You changed domains. For example you moved from a staging domain to your production domain, or renamed the site entirely.
  • You use both www and non-www, or switched between them. https://example.com and https://www.example.com are two different registered URLs.
  • You switched between http and https.
  • You installed WP-Script Core in a subfolder, or moved the site into/out of one. For example https://example.com versus https://example.com/blog. The site key is tied to the exact site URL WordPress reports, subfolder included.

Fix: go to My Account → Sites, find the site, and regenerate its site key. Regenerating updates the registered URL to match your site's current address. Then paste the new key into the WP-Script Core dashboard.

Site cloned from another of your sites?

Before WP-Script Core 6.0.9, a site copied from another one kept the address of the original site, so every new site key pasted on the copy was refused with this URL mismatch. Update WP-Script Core to 6.0.9 or later, then paste the site key generated for the copy: it is checked against the copy's own address.

3. Site not found (404)​

The site key itself may still be valid, but the server can't find a matching site record to attach it to. In practice you'll see this if the site entry behind the key was deleted from your WP-Script account after the key was generated, or if you're trying to activate a very old integration that predates the current setup.

Fix: go to My Account → Sites, add the site again if it's missing, and paste the newly generated site key into WP-Script Core.

4. After fixing it​

Once you've resolved the error and pasted a valid, matching site key, the WP-Script Core dashboard reloads automatically and your purchased themes and plugins reconnect. You don't need to reinstall anything, the products were only disconnected locally, not uninstalled.

If none of the above matches what you're seeing, see Site Key Activation for the full activation walkthrough, or contact support with the exact error message shown in your WP-Script Core dashboard.