Troubleshooting

Common issues and solutions when using the Security Suite module.

Troubleshooting

Scan Doesn't Complete

Symptom: The scan progress stops or the page becomes unresponsive.

Causes & Solutions:

  • PHP execution time limit — Reduce the batch size in Settings (try 200 or 100 instead of 500)
  • Memory limit — The module needs approximately 128 MB of PHP memory. Check your php.ini or hosting panel
  • Browser timeout — Keep the browser tab active. Some browsers throttle background tabs. Use cron for unattended scanning.

Too Many False Positives

Symptom: The scanner reports hundreds of detections in known-safe files.

Solutions:

  1. Enable comment filtering in scan settings
  2. Add known-safe directories to excluded paths (e.g., /vendor/)
  3. Whitelist specific patterns that are legitimate in your codebase
  4. Use Quick Scan instead of Full Scan for routine checks — it skips vendor and cache directories

Cron Job Not Running

Symptom: Automated scans are not executing on schedule.

Check:

  1. Verify the cron URL is correct (copy fresh from Settings)
  2. Check that the security token matches
  3. Test the URL manually in a browser — you should see a JSON response
  4. Check your hosting panel's cron logs for errors
  5. Ensure curl or wget is available on your server

Locked Out by Admin Protection

Symptom: You enabled IP whitelisting or Basic Auth and can't access admin.

Solution:

  1. Connect via FTP or SSH
  2. Navigate to your admin directory
  3. Remove or edit the .htaccess file created by the module
  4. Access your admin and reconfigure the protection settings

Quarantine Restore Fails

Symptom: Restoring a quarantined file gives an error.

Causes:

  • The original directory no longer exists — create it manually first
  • File permissions prevent writing — check directory permissions (should be 755)
  • Another file now exists at the original path — rename or remove it first

Module Won't Install

Symptom: Upload fails or installation gives an error.

Check:

  • Ensure the ZIP file is not corrupted (re-download from Addons)
  • Check PHP version compatibility (7.2+)
  • Verify sufficient disk space
  • Check PrestaShop module directory permissions (/modules/ should be writable)