• Resolved cfm168

    (@cfm168)


    Hello,

    I get the site health check alert:
    ——————————————
    Unable to detect page cache due to possible loopback request problem. Please verify that the loopback request test is passing. Error: cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received (Code: http_request_failed)

    Page cache enhances the speed and performance of your site by saving and serving static pages instead of calling for a page every time a user visits.

    Page cache is detected by looking for an active page cache plugin as well as making three requests to the homepage and looking for one or more of the following HTTP client caching response headers:

    cache-control, expires, age, last-modified, etag, x-cache-enabled, x-cache-disabled, x-srcache-store-status, x-srcache-fetch-status.
    ————————————————

    Can you please help to improve my site from the above improvement? Thanks in advance.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Nawawi Jamili

    (@nawawijamili)

    Hi there,

    I believe it is not related to Docket Cache. You may try to disable Docket Cache and see if the issue still exists.

    Thanks.

    Thread Starter cfm168

    (@cfm168)

    Hi @nawawijamili,

    Thank you for prompt response. I understand it is not caused by your plugin. I write the support actually expected Docket Cache features can help to resolve this issue. Any suggestions will be appreciated.

    Plugin Author Nawawi Jamili

    (@nawawijamili)

    Hi,

    I’m sorry, the Docket Cache feature can’t solve this issue. Normally it is caused by a plugin. For a common solution, please try disabling plugins one by one to detect which one causes this issue.

    Thanks.

    Plugin Author Nawawi Jamili

    (@nawawijamili)

    Hi,

    I’m marking this thread as resolved. Feel free to open a new topic if you have further questions.

    Thanks.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Unable to detect the presence of page cache’ is closed to new replies.