An install can fail at one of five points: the credit check, the safety checks, the download, the file install, or the health check afterwards. The message tells you which. In every case where credits were charged, they are refunded automatically; you do not need to open a ticket for the refund.
"Insufficient credits"
Cause: the plugin's tier price is higher than your balance. Fix:- Buy a credit pack from the pricing page; credits are added instantly
- Wait for the next monthly allocation (date on your Subscription page)
- Upgrade to a plan with a larger allocation
"Compatibility check failed" or "Requires WordPress x / PHP x"
Cause: the plugin's minimum WordPress, PHP or WooCommerce version is higher than the site's. Zeebrar reads those numbers from the plugin package and compares them with what the connector reported for the site. Fix: update WordPress, PHP or WooCommerce on the site first, then retry. The site's current versions are on its page in your dashboard when diagnostics sharing is on, or under Tools > Site Health in WordPress."Blocked by scan result"
Cause: the plugin package has a VirusTotal result Zeebrar does not allow to be installed. Fix: there is no override. Wait for a newer version of the plugin, or contact [email protected] if you believe the result is a false positive."Connection failed" or "Site unreachable"
Cause: the connector on the site did not answer. The site may be down, a firewall or security plugin may be blocking the connector's REST endpoints, or the connector was deactivated. Fix: check that the site loads, that the connector is active, and see Troubleshooting Connector Connection Issues."Site offline"
Cause: the connector has not contacted Zeebrar for 48 hours, so the dashboard marks the site offline. Fix: open GPLC Connector > Plugin Updates in the site's WordPress admin; that contacts Zeebrar and the site shows as Connected again. If the connector's Dashboard screen shows the license as anything but Active, re-enter your license key."Installation failed: disk full" or "Permission denied"
Cause: the web server could not write to/wp-content/plugins/.
Fix:
- Check the folder permissions (755 for folders, 644 for files is typical)
- Free up disk space or ask your host to
- As a last resort, upload the plugin ZIP by FTP and link it from GPLC Connector > Installed > Add to updates
"Update reversed" or "the previous version was restored"
Cause: the plugin installed, but the health check afterwards found the site not responding, so the connector restored the backup it made before the install. On WordPress 6.6 and newer a scheduled auto-update can be reversed by WordPress core in the same way. Fix: the site is back on the previous version and the credits were refunded. Check the plugin's changelog for a known conflict, and try the update again on a staging site. The activity feed shows which mechanism rolled the site back."Package is a bundle" or "Download URL failed"
Cause: the package Zeebrar received from the catalog source was not a single installable plugin, or the download link expired before the site fetched it. Fix: retry once. If it fails again, email [email protected] with the plugin name; the catalog entry needs attention on our side. Credits were refunded."Too many requests"
Cause: the account hit a rate limit (for example, 5 license activations per minute). Fix: wait a minute and retry.Still stuck
Email [email protected] with:
- The exact error message (a screenshot is fine)
- The site URL and the plugin name
- The site's WordPress and PHP versions (on the site's page in your dashboard when diagnostics sharing is on, otherwise from WordPress's Site Health screen)
- A diagnostics report from GPLC Connector > Diagnostics > Generate Report