Re-pair a site after auth drift

The connector plugin and Manage GPL each keep their own copy of the pairing state. When those copies diverge — the connector was uninstalled and reinstalled, the site was restored from a backup that predates the pairing, or someone manually regenerated the token in WP admin — Manage GPL detects the mismatch and shows a Re-pair this site button on the site's page. Use it instead of deleting and re-adding the site, so all the site's history, activity log, and settings are preserved.

How to tell you need it

• Open any page of the site in Manage GPL — if the auth has drifted, the site's left-hand action panel shows a prominent blue Re-pair this site button (where Pause site normally lives).
• Operations like Refresh, Update, and SSO will refuse to run while the site is in this state.

How to re-pair

1. On the site's page in Manage GPL, click Re-pair this site.
2. A modal opens with a link straight to WP admin → Settings → Manage GPL Connect on your site.
3. In WP admin, copy the current connection token (use the Copy button next to it). If you don't trust the existing one, click Regenerate token first.
4. Paste the token into the modal and click Re-pair site.

The site transitions back to connected on the next request, and the dashboard updates.

What's preserved

• Site history and activity log
• Whitelabel profile (if configured)
• Uptime monitoring settings and incident history
• The site's position in your sites list

What's reset

• The HMAC secret — the old one stops working immediately; a fresh one is generated as part of the re-pair.
• The inventory re-pulls on the next refresh.

If Re-pair keeps failing

If pasting the token doesn't move the site back to connected, the cause is almost always a network issue on the WordPress side. Check:

• Can the WP host reach https://www.managegpl.com over HTTPS? Test with curl from SSH.
• Is the WordPress REST API reachable at https://yoursite.com/wp-json/? If a security plugin is blocking it for unauthenticated requests, our confirmation call fails.
• Did the WP admin URL recently change? The connector reports its canonical URL on every request — if that drifted from what we have stored, the URLs need to match.

If none of those help, open a support ticket with the site URL and the timestamp of your re-pair attempt — we can usually pinpoint the cause from our side-of-the-wire logs.

What if there's no Re-pair button?

The button only appears for the auth-drift case. If your site is just unreachable (genuinely down or temporarily blocked) without auth drift, you don't need to re-pair — the next successful request flips it back to connected automatically. If the site is fully gone (e.g., decommissioned), use Delete site on the site's page.