Internal Scan – Page Unresponsive

  • viablethought

    (@viablethought)


    4 days, 10 hours ago

    Hello –

    I just installed the plugin on one of our client’s sites and initiated an internal scan, the scan starts but within 10 seconds I receive a message saying the Page is Unresponsive – Exit or Wait. I exit the page and return and find that the scan is still running but then within another 10 seconds, I receive the same message about the Page Unresponsive.

    What are the required server settings? This application runs on its own dedicated server.

    Thanks

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter viablethought

    (@viablethought)

    4 days, 10 hours ago

    Hello –

    Just checked the operational logs and this is what is showing:

    ERROR [12:09:26] Failed to update option qtr_scan_cron_args
    ERROR [12:14:15] Failed to update option qtr_scan_cron_args
    ERROR [12:14:35] Failed to update option qtr_scan_cron_args
    ERROR [12:15:40] Failed to update option qtr_scan_cron_args
    ERROR [12:16:43] Field action not supported
    ERROR [12:16:43] Field _wpnonce not supported
    ERROR [12:16:43] Field _wp_http_referer not supported
    ERROR [12:18:40] Failed to update option qtr_scan_cron_args
    ERROR [12:18:40] Failed to update option qtr_scan_cron_args
    ERROR [12:18:40] Failed to update option qtr_scan_cron_args
    ERROR [12:24:57] Failed to update option qtr_scan_cron_args
    ERROR [12:28:41] Failed to update option qtr_scan_cron_args
    ERROR [12:28:48] Failed to update option qtr_scan_cron_args
    ERROR [12:37:06] Failed to update option qtr_scan_cron_args

    Plugin Author quttera

    (@quttera)

    2 days, 17 hours ago

    Hello,

    Thank you for sharing the additional log details.

    If the browser shows “Page is Unresponsive” during the internal scan, it usually means the front-end page is waiting for an AJAX response from the back-end, but the server-side process is not responding within the expected time. In other words, the scan may still be running in the background, but the browser interface becomes stuck because it is waiting for the back-end to complete or return status information.

    Regarding the following log entry:

    ERROR [12:18:40] Failed to update option qtr_scan_cron_args

    This error indicates that the plugin was unable to update the WordPress option qtr_scan_cron_args using the standard WordPress update_option() method.

    This can usually happen for one of two reasons:

    1. WP-Cron is not working correctly
      If the scanner has not successfully run before, this may indicate that the WordPress cron mechanism is not executing properly. The scan process depends on scheduled WordPress tasks, so if WP-Cron is disabled, blocked, or not triggered, the scan status may not update correctly.
    2. Database write/update issue
      The plugin may be unable to write or update the required option in the WordPress database. This could be related to database permissions, table corruption, object caching, or another server/database-level restriction.

    As a first step, please check whether WP-Cron is enabled and functioning correctly on the site.

    Best regards,

    Michael
    Quttera Support

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.