Troubleshooting

"Insight engine is disabled" Notice

Details
Category: Troubleshooting
  • Applicable Software: MokonyxInsight
  • Min Version Number: 01.00.00
  • Max Version Number: Not Applicable

If Insight shows a warning that the engine is unavailable (and dashboards/data sources come up empty), the cause is almost always that the System - MokonyxInsight plugin is disabled.

Why it happens

The metrics engine, provider discovery and data-source logic live in that system plugin. Joomla only registers a plugin's classes for autoloading while it is enabled, so disabling it makes the component unable to load its engine — Insight now degrades gracefully and shows this notice (with a direct link) instead of a fatal error.

Fix

  1. Follow the link in the notice, or go to System → Manage → Plugins and search mokonyxinsight.
  2. Enable System - MokonyxInsight (and, for scheduling and REST, the Task and Web Services plugins).
  3. Reload Insight — the notice clears once the engine is back.

If the plugin is missing entirely rather than disabled, reinstall the MokonyxInsight package.

Hits: 2

A Connection Test Fails

Details
Category: Troubleshooting
  • Applicable Software: MokonyxInsight
  • Min Version Number: 01.00.00
  • Max Version Number: Not Applicable

When Test on a data source reports failure, work through these in order.

Checklist

  • Credentials — re-paste the key/token into the secret; it is write-only, so a blank field means "unchanged", not "empty".
  • Identifiers — confirm the site/property id matches the service (GA4 property id, Matomo idsite, Plausible domain, Umami website_id).
  • Reachability — the Joomla server must reach the service host/port outbound; check firewalls and that the base URL is correct and uses the right scheme.
  • Permissions/plan — some services need a specific API scope or plan tier (e.g. Plausible's Stats API).
  • Clock — OAuth and signed requests fail if the server clock is badly skewed.

Still failing? Enable Joomla debug/logging and read the mokonyxinsight log channel for the provider's underlying error.

Hits: 2

Google (GA4 / Search Console) Auth & Quota Errors

Details
Category: Troubleshooting
  • Applicable Software: MokonyxInsight
  • Min Version Number: 01.00.00
  • Max Version Number: Not Applicable

The Google connectors use OAuth, so most issues are authorization or quota related.

Authorization

  • Re-authorize if you see an invalid/expired-token error — refresh tokens can be revoked by Google or by changing the account password.
  • Enable the APIs — the Google Analytics Data API and Search Console API must be enabled on the Google Cloud project behind your OAuth client.
  • Account access — the authorizing Google account must have at least read access to the GA4 property / Search Console site.

Quota & empty results

  • Quota — GA4 enforces per-property request quotas; heavy dashboards plus short refresh intervals can exhaust them. Lengthen the refresh interval and lean on caching.
  • Freshness — GA4 data is not instant; very recent windows may read low or empty until Google finishes processing.
  • Property type — confirm it's a GA4 property, not legacy Universal Analytics (unsupported).
Hits: 1