Omega Security Engine Pro — Troubleshooting

Version 1.0.0 Omega Web Apps omegawebapps.com

Omega Security Engine Pro is engineered for stability and predictability. In rare cases, issues may arise due to server configuration, conflicting plugins, CDN rules, or aggressive hardening settings. This guide explains how to diagnose and resolve them, including issues related to optional .htaccess hardening.

5. Troubleshooting

5.1 Firewall Blocking Legitimate Requests

If a legitimate request is blocked:

• Check the Security Logs tab for the blocked request.
• Review the IP, request path, and user agent.
• Whitelist the IP if necessary.
• Ensure no CDN (Cloudflare, LiteSpeed, etc.) is injecting conflicting rules.

5.2 Locked Out of WordPress Admin

If you accidentally trigger the login guard:

• Wait for the lockout window to expire, or
• Log in from a different IP address, or
• Remove the blocked IP from the blocked_ips.json file via FTP.

5.3 File Monitor Shows Unexpected Changes

This may occur after:

• Plugin updates
• Theme updates
• WordPress core updates
• Server‑side file changes
• Automated deployment or CI/CD pipelines

Review the modified files to confirm whether the changes are legitimate.

5.4 Malware Scanner Flags Suspicious Files

If the malware scanner detects suspicious patterns:

• Review the file path and patterns detected.
• Check if the file belongs to a plugin or theme.
• Restore the file from a clean backup if needed.
• Use Omega Web Metrics for deeper diagnostics if the issue persists.

5.5 Hardening Rules Break the Site

If applying hardening rules causes issues:

• Go to the Hardening tab and click Remove Hardening Rules.
• If you enabled .htaccess hardening, remove the Omega block manually via FTP. Omega rules are always inside:
  # BEGIN Omega Security Engine # END Omega Security Engine
• If needed, restore your original .htaccess from the automatic backup:
  .htaccess.ose-backup
• Ensure your server does not override rules (LiteSpeed, Nginx, Cloudflare).

5.6 White Screen or Fatal Error

If you encounter a fatal error:

• Rename the plugin folder from omega-security-engine to omega-security-engine-disabled.
• This disables the plugin instantly.
• Check for conflicting plugins or outdated PHP versions.

5.7 Admin Area Slows Down

Omega Security Engine Pro does not run in the admin area except for the dashboard UI. If you experience slowness:

• Check for conflicting plugins.
• Ensure your hosting environment meets PHP requirements.
• Disable unnecessary admin‑heavy plugins.
• Ensure no malware or excessive cron jobs are running.

5.8 No Logs Are Appearing

If logs are empty:

• Ensure the logs directory inside the plugin is writable.
• Check file permissions (recommended: 755 for folders, 644 for files).
• Ensure your server is not blocking file writes (common on hardened hosts).

5.9 Issues Omega Security Engine Pro Cannot Fix

Some issues require manual developer or server‑level action. These include:

• HTTPS redirect
• HSTS header
• Security headers (CSP, X‑Frame‑Options, etc.)
• Cookie flags (Secure, HttpOnly, SameSite)
• FORCE_SSL_ADMIN in wp-config.php
• WP_DEBUG in wp-config.php
• Database prefix changes
• Mixed content
• Nginx/LiteSpeed/Cloudflare header overrides

These issues cannot be fixed by any WordPress plugin. They require a developer, hosting provider, or CDN configuration.

5.10 When to Use Omega Web Metrics

Use Omega Web Metrics for full diagnostics, including:

• Security header analysis
• HTTPS/HSTS issues
• Mixed content detection
• Cookie flag issues
• Server‑level configuration problems
• Plugin impact and performance issues
• SEO, UX, and image optimization issues