# General Issues General Issues # Scan Not Running ## What This Means This issue occurs when the Steel Security scan does not run or does not produce results when expected. --- ## Common Symptoms - the scan page loads but no results appear - the scan does not start automatically - findings are not updated - the scan appears to hang or stall --- ## Possible Causes This issue may be caused by: - JavaScript errors in the browser - server timeouts or resource limits - plugin conflicts - incomplete installation or configuration --- ## How to Fix It Try the following steps: ### 1. Refresh the Page - reload the scan page - ensure the scan is triggered properly --- ### 2. Check Browser Console - open developer tools - look for JavaScript errors - resolve any visible issues --- ### 3. Disable Other Plugins - temporarily disable other plugins - check if the scan runs correctly - re-enable plugins one at a time --- ### 4. Check Server Limits - ensure your server has sufficient resources - review timeout settings - check PHP error logs --- ### 5. Verify Installation - confirm Steel Security is installed and activated correctly - ensure all required components are present --- ## What to Expect After Fixing After resolving the issue: - the scan should run automatically when the page loads - findings should be generated and displayed - results should reflect the current state of your site --- ## When to Seek Help If the issue persists: - gather error messages or logs - note recent changes to your site - contact support with details --- ## Related - [Understanding Scan Findings](https://docs.steelsecurity.com/books/findings-reference/page/understanding-scan-findings) - [Reviewing Findings](https://docs.steelsecurity.com/books/getting-started/page/reviewing-findings) # Changes Not Applying ## What This Means This issue occurs when changes made through Steel Security do not appear to take effect on your site. You may apply a hardening control, but the expected behavior does not change. --- ## Common Symptoms - protections appear enabled but have no effect - restricted files or endpoints remain accessible - headers do not appear after being applied - previously visible behavior remains unchanged --- ## Possible Causes This issue is often caused by: - caching (browser, server, or CDN) - delayed server configuration updates - conflicting rules or settings - unsupported server environment --- ## How to Fix It Try the following steps: --- ### 1. Clear All Caches - clear your browser cache - clear any WordPress caching plugins - purge CDN caches (if applicable) --- ### 2. Reload the Page Fully - perform a hard refresh (e.g., Ctrl+F5 or Cmd+Shift+R) - test in a private/incognito window --- ### 3. Check Server Environment - confirm your server supports the applied control - ensure configuration changes are allowed - verify `.htaccess` or server rules are being read --- ### 4. Review Conflicting Configurations - check for overlapping rules from other plugins - review manual server configurations - ensure no settings override Steel Security changes --- ### 5. Allow Time for Changes - some environments may delay configuration updates - wait briefly and test again --- ## What to Expect After Fixing After resolving the issue: - applied protections should take effect immediately - restricted access should behave as expected - headers or rules should appear correctly --- ## When to Seek Help If the issue persists: - document the specific control applied - note your server type (Apache, Nginx, IIS) - check logs or error messages - contact support with details --- ## Related - [Apache (.htaccess) Hardening](https://docs.steelsecurity.com/books/hardening-reference/page/apache-htaccess-hardening) - [Nginx Hardening](https://docs.steelsecurity.com/books/hardening-reference/page/nginx-hardening) - [IIS (web.config) Hardening](https://docs.steelsecurity.com/books/hardening-reference/page/iis-webconfig-hardening) # Unexpected Site Behavior ## What This Means This issue occurs when your site behaves unexpectedly after applying one or more hardening controls. This may include broken functionality, missing features, or access issues. --- ## Common Symptoms - parts of the site stop working - login or admin access is affected - integrations fail or behave differently - pages do not load as expected --- ## Why This Happens Hardening controls restrict access or behavior to improve security. In some cases, these restrictions may: - conflict with plugins or themes - block required functionality - interfere with integrations or custom code This is more likely in complex or customized environments. --- ## How to Fix It Try the following steps: --- ### 1. Identify the Change - determine which hardening control was applied most recently - consider any recent configuration changes --- ### 2. Revert the Change - disable the most recent control - confirm whether normal behavior returns --- ### 3. Test Incrementally - reapply controls one at a time - test your site after each change - identify the specific control causing the issue --- ### 4. Review Requirements - check if your site relies on the affected functionality - confirm whether restrictions are appropriate for your use case --- ### 5. Adjust or Exclude - modify the configuration if possible - allow required access where needed - leave the control disabled if necessary --- ## What to Expect After Fixing After resolving the issue: - normal site functionality should be restored - problematic controls can be adjusted or excluded - other protections can remain in place --- ## When to Seek Help If you are unable to resolve the issue: - document the affected functionality - note which control caused the issue - include any error messages or logs - contact support with details --- ## Key Principle Security should not come at the cost of breaking your site. Apply protections in a way that balances security and functionality. --- ## Related - [Safe Rollback Practices](https://docs.steelsecurity.com/books/plugin-guide/page/safe-rollback-practices) - [Applying Hardening Safely](https://docs.steelsecurity.com/books/getting-started/page/applying-hardening-safely) - [Restrict Sensitive Endpoints](https://docs.steelsecurity.com/books/hardening-reference/page/restrict-sensitive-endpoints)