Skip to main content

Troubleshooting Connector Connection Issues

License activation errors, sites showing offline or revoked, firewalls and security plugins, SSL problems, and how to send a diagnostics report.

Updated Oct 13, 2026
1,293 views

The GPLC Connector talks to Zeebrar in both directions: the site calls zeebrar.com whenever it checks for updates (at least every 12 hours) or you use its screens, and your dashboard calls the site's REST endpoints (under /wp-json/gplc/v1/) to install, update and read the plugin inventory. Most connection problems block one of those two directions.

First, read the two status indicators

  • In WordPress: the connector's Dashboard screen shows the license as Active, Expired, Suspended or Inactive
  • In your account: the Sites page lists each site as Connected (contacted Zeebrar within the last 48 hours), Offline, or Revoked

"Invalid license key"

Cause: the key was mistyped, or it was regenerated in your account after this site was activated. Fix: copy the key from your account dashboard and paste it again. Activations are limited to 5 attempts per minute; if you see a rate-limit message, wait a minute.

"Site limit reached"

Cause: your plan's site limit is used up (Personal 5, Pro 15, Agency unlimited). Fix: revoke a site you no longer use from the Sites page, or upgrade the plan.

The site shows as Offline

Cause: the connector has not contacted Zeebrar for 48 hours. The update check runs through WP-Cron and admin page loads, so a site nobody visits or whose cron never fires can go offline even though nothing is broken. Fix:
  1. Open GPLC Connector > Plugin Updates in the site's WordPress admin (this contacts Zeebrar), then reload the Sites page
  2. If it is still offline, confirm the connector is active and the license shows Active
  3. If your host disables WP-Cron, ask them to trigger wp-cron.php from a system cron every few minutes

The site shows as Revoked

Cause: the site was disconnected from the connector's Dashboard screen or revoked from your account. Fix: click Reconnect on the Sites page, or activate the license again on the site.

"Connection timed out" or installs never complete

Cause: the site is slow to respond, or a firewall blocks the dashboard's calls to the site's REST endpoints. Fix:
  1. Confirm /wp-json/gplc/v1/status on the site answers (it should not return 403 or a login page)
  2. Whitelist Zeebrar's calls in your security plugin (Wordfence, iThemes, Cloudflare WAF rules that block /wp-json/)
  3. Ask your host whether outbound HTTPS to zeebrar.com is allowed; the site needs it for update checks and downloads

SSL certificate errors

Cause: the site's certificate is expired or self-signed, or PHP lacks the cURL and OpenSSL extensions. Fix:
  1. Renew the certificate; both the site and Zeebrar require valid HTTPS
  2. Ask your host to enable the cURL and OpenSSL PHP extensions if the diagnostics report lists them as missing

Requirements check

  • WordPress 6.0 or newer, PHP 7.4 or newer
  • PHP extensions: cURL and OpenSSL
  • Outbound HTTPS to zeebrar.com
  • The REST API enabled (some hardening plugins turn it off entirely)

Sending a diagnostics report

  1. Open GPLC Connector > Diagnostics in WordPress
  2. Click Generate Report; it contains the environment (WordPress, PHP, extensions), the sync status and recent errors, and no passwords
  3. Attach it to your email to [email protected], together with the site URL

If you prefer, switch on Enable remote diagnostics sharing on the same screen and support can pull the report directly while investigating; switch it off again afterwards.

Back to Support Center