Common Issues and Solutions

Quick solutions for the most frequently encountered problems with Content Guard Pro.

Scan Issues #

Scans Not Starting #

Symptoms:

  • Click “Start Scan” but nothing happens
  • Progress never appears
  • No scan in history

Solutions:

1. Check JavaScript errors:
– Open browser Developer Tools (F12)
– Look for errors in Console tab
– Disable conflicting plugins

2. Check AJAX functionality:
– Verify admin-ajax.php is accessible
– Check for security plugin blocking AJAX

3. Clear caches:
– Clear browser cache
– Clear WordPress object cache
– Try incognito/private window

4. Check Action Scheduler:
– Go to Tools → Scheduled Actions
– Look for pending CGP actions
– Check for failed actions

Scans Timing Out #

Symptoms:

  • Scan starts but never finishes
  • “Connection lost” messages
  • Frequent interruptions

Solutions:

1. Enable Safe Mode:
– Settings → Performance → Safe Mode: On
– Uses smaller batches, longer delays

2. Reduce batch size:
– Settings → Performance → Batch Size: 25
– Increase gradually if stable

3. Increase server limits:

   // wp-config.php
   define('WP_MEMORY_LIMIT', '256M');
   

4. Use server cron:
– Some hosts limit browser-triggered cron
– Set up real cron job

Scans Very Slow #

Symptoms:

  • Scans take hours
  • Low items/second rate
  • Throttling messages

Solutions:

1. Use Quick Scan mode for routine checks

2. Schedule during off-peak hours

3. Optimize database:

   wp db optimize
   

4. Check hosting resources:
– Upgrade hosting plan
– Use managed WordPress hosting

Finding Issues #

False Positives #

Symptoms:

  • Legitimate content flagged
  • Same domain flagged repeatedly
  • Trusted services detected

Solutions:

1. Add to allowlist:
– Patterns → Allowlist
– Add trusted domain
– Save changes

2. Mark as ignored:
– Click Ignore on finding
– Future scans skip this fingerprint

3. Report false positive:
– Helps improve detection patterns

Missing Threats #

Symptoms:

  • Known malicious content not detected
  • Low finding count for infected site
  • Specific patterns not caught

Solutions:

1. Use Standard Scan mode:
– Scans more content types
– Catches meta and option threats

2. Check allowlist:
– Verify domain isn’t accidentally allowlisted
– Review custom allowlist entries

3. Update patterns:
– Settings → Check for Pattern Updates
– Ensure automatic updates enabled

4. Add to denylist:
– Patterns → Denylist
– Add known malicious domains

Findings Not Resolving #

Symptoms:

  • Fixed content but finding still “open”
  • Auto-resolution not working
  • Manual edits not recognized

Solutions:

1. Ensure content is saved:
– Click Update/Publish
– Auto-resolution only on save

2. Check you fixed the right content:
– View finding details
– Verify exact matched text removed

3. Manually resolve:
– Find the finding
– Click “Mark as Resolved”

Notification Issues #

Not Receiving Emails #

Symptoms:

  • No email alerts
  • Test email not received
  • Digest emails missing

Solutions:

1. Check spam folder

2. Verify email settings:
– Settings → Notifications
– Confirm Email Alerts enabled
– Check recipients correct

3. Test WordPress email:
– Try password reset email
– Use email logging plugin

4. Install SMTP plugin:
– WordPress’s wp_mail() may not work
– Use WP Mail SMTP or similar

Webhook Not Working #

Symptoms:

  • Endpoint not receiving requests
  • Test webhook fails
  • No data at destination

Solutions:

1. Check URL:
– Must be HTTPS
– Must be accessible from your server

2. Check firewall:
– Endpoint must accept external requests
– Check for IP restrictions

3. Verify signature:
– If using secret, check implementation
– Test without secret first

4. Check timeout:
– Endpoint must respond within 30 seconds
– Process async if needed

Performance Issues #

Site Slow During Scans #

Symptoms:

  • Front-end sluggish during scans
  • Admin slow when scan running
  • Database timeout errors

Solutions:

1. Enable Safe Mode

2. Reduce batch size (Settings → Performance)

3. Increase batch delay (5-10 seconds)

4. Schedule during off-hours

High Memory Usage #

Symptoms:

  • Memory errors in logs
  • “Allowed memory exhausted”
  • Scan crashes

Solutions:

1. Reduce batch size to 25 or lower

2. Increase memory limit:

   define('WP_MEMORY_LIMIT', '256M');
   

3. Enable Safe Mode

4. Check for memory leaks in other plugins

Database Issues #

“Table Doesn’t Exist” #

Symptoms:

  • Database errors on activation
  • Findings not saving
  • Scan history missing

Solutions:

1. Deactivate and reactivate:
– Go to Plugins
– Deactivate Content Guard Pro
– Reactivate (triggers table creation)

2. Check database permissions:
– User needs CREATE TABLE permission
– Contact host if using shared DB user

3. Manual table creation:
– Use Diagnostics → Repair Database

“Database Connection Lost” #

Symptoms:

  • Scan stops mid-way
  • “Error establishing database connection”
  • Intermittent failures

Solutions:

1. Check database server:
– Contact host
– Review server logs

2. Reduce query load:
– Enable Safe Mode
– Reduce batch size

3. Check max connections:
– May be hitting connection limit
– Optimize other plugins

Quick Fixes Checklist #

When something isn’t working:

  • [ ] Clear browser cache and try again
  • [ ] Clear WordPress object cache
  • [ ] Try in incognito/private window
  • [ ] Deactivate other plugins temporarily
  • [ ] Switch to default theme temporarily
  • [ ] Run Diagnostics and check results
  • [ ] Check PHP error log
  • [ ] Check server error log
  • [ ] Ensure WordPress and plugins updated
What are your feelings
Updated on December 4, 2025
Scroll to Top