Skip to content

WordPress Plugin Troubleshooting

No signals appearing

Check the connection test first. Go to Logystera → Credentials and click Verify Connection. If it fails:

  • Verify your Entity Token and Entity Secret are correct.
  • Check that your server can make outbound HTTPS requests to ingest.logystera.com.
  • Some shared hosts block outbound HTTP — contact your host to confirm port 443 is open.

If the test passes but no signals appear:

  • WP-Cron may not be firing. The plugin buffers events and flushes them on a cron schedule. Trigger cron manually: bash wp cron run --due-now
  • Check whether DISABLE_WP_CRON is set to true in wp-config.php. If so, your cron must be triggered externally — ensure it runs at least every 60 seconds.

Signals delayed or batchy

This is expected. The plugin flushes events on a WP-Cron schedule (default: every 5 minutes). On low-traffic sites, WP-Cron may fire infrequently because it only runs when a visitor loads a page.

To lower latency on low-traffic sites, add a real cron job:

# crontab -e
* * * * * curl -s https://yoursite.com/wp-cron.php?doing_wp_cron > /dev/null

Or reduce the Flush interval in Settings → Logystera → Settings.

Heartbeat alert firing unexpectedly

The wp_agent_missing_heartbeat alert fires if no heartbeat is received within 30 minutes. Possible causes:

  • WP-Cron is disabled or not running.
  • The site had downtime during the window.
  • Heartbeat delivery failed due to a temporary gateway issue.

The alert auto-resolves the next time a heartbeat is delivered successfully.

High memory usage on shared hosting

The plugin is designed for shared hosting and adds minimal overhead (< 1MB). If you see unusually high memory:

  • Disable PHP errors (individual) in Settings → Logystera → Event Hooks — on sites with many PHP warnings the error handler can accumulate events. Use PHP error summary instead.
  • Reduce Batch size in Settings to flush more frequently in smaller payloads.

Duplicate events after migration

If you migrated a WordPress site (moved domain, cloned staging to production), the plugin may have stale credentials. Click Disconnect in the Credentials tab, then Connect to Logystera to set up fresh credentials for the new environment. Alternatively, update the Entity Token and Secret manually.

"Upgrade Required" admin notice

If you see a red banner saying your plugin version is no longer supported:

  1. Update the Logystera plugin to the version shown in the notice (or later).
  2. The notice clears automatically after the next successful ingest.

While the notice is active, ingestion is paused — events continue to be collected locally and will be sent once you update. No data is lost.

If you cannot update immediately, events remain buffered locally up to the configured buffer limit.

Checking raw plugin logs

Enable WordPress debug logging and look for [Logystera] prefixed entries:

// wp-config.php
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Log file: wp-content/debug.log