Back to Community
Home / Community / Plugin → Burst statistics – privacy-friendly analytics for wordpress

Resolving the 'Due to your server or website configuration' Error in Burst Statistics

30 threads Sep 10, 2025 Plugin → Burst statistics – privacy-friendly analytics for wordpress

Content

One of the most common support queries for the 'Burst Statistics – Privacy-Friendly Analytics for WordPress' plugin is the error message: "Due to your server or website configuration it is not possible to track statistics." This alert indicates that the plugin's method for recording visitor data is failing. Based on community reports, this article explains why this happens and outlines the most effective troubleshooting steps to resolve it.

Why This Error Occurs

Burst Statistics uses two primary methods to track page views, listed in order of preference:

  1. REST API: The preferred, faster method that uses a WordPress core feature.
  2. Endpoint File Fallback: A reliable fallback method that uses a direct PHP file (burst-statistics-endpoint.php) if the REST API is unavailable.

The error appears when both methods fail. The causes are diverse but almost always relate to server security configurations, file permissions, or conflicts with other software.

Common Causes and Their Solutions

1. REST API or Endpoint Blocked by Security Software

The Problem: Security plugins (e.g., AIO WP Security, WP Hide & Security Enhancer), web application firewalls (WAFs like ModSecurity), or server-level security rules often block the requests Burst needs to function. This is the most frequent cause.

The Solution:

  • ModSecurity/Comodo WAF: Rules like 214930 or 210710 can block requests to the endpoint file. You or your hosting provider may need to whitelist the /burst-statistics-endpoint.php file or the specific rule triggering the block.
  • Security Plugins: Some features, like the "Salt postfix" in AIO WP Security, can cause conflicts. Try temporarily disabling specific security features to identify the culprit, then create an exception for Burst Statistics.
  • False Positives: If a security plugin flags burst-statistics-endpoint.php as a threat, this is a false positive. You can safely ignore the alert or report it to the security plugin's developers so they can update their definitions.

2. Endpoint File Missing or Inaccessible

The Problem: The burst-statistics-endpoint.php file may not be in the correct location, may have the wrong file permissions, or may be blocked by server configuration rules (e.g., open_basedir restrictions, client denied by server configuration errors in logs).

The Solution:

  • Manual Placement: Ensure the file is in your website's root directory (e.g., public_html/). You can manually download it from the plugin's folder (/wp-content/plugins/burst-statistics/) and place it in the root.
  • File Permissions: Set the file permissions (CHMOD) to 644.
  • Subdirectory Installs: If WordPress is installed in a subdirectory (e.g., example.com/wp/), the endpoint file path may be incorrect. A fix for this specific issue has been developed on the plugin's GitHub repository.

3. Caching or Optimization Plugin Conflicts

The Problem: Performance plugins that delay, combine, or asynchronously load JavaScript (e.g., WP Rocket, WP-Meteor) can prevent Burst's tracking script from loading correctly.

The Solution: Exclude Burst's core scripts from optimization. The scripts to exclude are typically:

  • /wp-content/plugins/burst-statistics/helpers/timeme/timeme.min.js
  • /wp-content/plugins/burst-statistics/assets/js/build/burst.min.js
Consult your caching plugin's documentation for instructions on adding script exclusions.

4. Database Table Issues

The Problem: In rare cases, the database tables required by Burst Statistics may not be created properly, especially after an update or migration. This can manifest as a "Table doesn't exist" error in your server logs.

The Solution: Trigger a database update by installing a plugin like "WP Debugging" or by re-saving your permalink structure in Settings > Permalinks.

General Troubleshooting Workflow

  1. Check the Dashboard: First, verify if data is actually being recorded despite the error message. Sometimes the status check returns a false positive.
  2. Test with a Clean Slate: Temporarily switch to a default WordPress theme (e.g., Twenty Twenty-Four) and disable all other plugins except Burst Statistics. If the error disappears, reactivate your plugins one by one to find the conflict.
  3. Inspect Server Logs: Your hosting error logs are the best source of truth. Look for 403, 404, or 500 errors related to burst-statistics-endpoint.php or the REST API (/wp-json/burst/).
  4. Wait for Cron: After making changes, note that Burst re-checks the tracking status automatically every hour. You may need to wait for this cycle to complete before the error clears.

When All Else Fails

If you have tried all the steps above and the issue persists, the problem is likely a highly specific server configuration. In this case, the best course of action is to share your website's URL and any relevant error logs from your server on a support forum. The 'Burst Statistics – Privacy-Friendly Analytics for WordPress' team is often active in these communities and can provide guidance for unique edge cases.

Remember, this error is almost always solvable by adjusting permissions, configuring security exceptions, or resolving plugin conflicts.

Related Support Threads Support