• Resolved wpwench

    (@wpwench)


    Hi there,

    We are having an issue with that this plugin is conflicting with SG-Cachepress plugin and the cache is continuously MISSING. The response header
    x-proxy-cache: MISS
    x-proxy-cache-info: 0 NC:000000 UP:SKIP_CACHE_SET_COOKIE

    Siteground has informed us that this is due to the following cache control headers coming from this plugin.
    cache-control: no-store, no-cache, must-revalidate

    I have confirmed, that by deactivating Cerber, the cache response header reports a HIT.

    Is there anything that we can alter on our end to avoid this or could this perhaps be addressed on your end? Thanks in advanced.

    Dignostic report

    Web Server	Apache
    PHP version	7.3.27
    Server API	cgi-fcgi
    Server platform	Linux
    Memory limit	768M
    Default PHP timezone	UTC
    Disabled PHP functions	
    WordPress version	5.7.1
    WordPress locale	en_GB
    WordPress options DB table	wp_options
    MySQLi	YES
    MySQL Native Driver (mysqlnd)	YES
    PHP allow_url_fopen	Enabled
    PHP allow_url_include	Disabled
    Persistent object cache	Yes | 27th April 2021, 4:37 am (8 mins ago) | Cerber's entries: 9 | Clear the cache
    Your IP address is detected as	178.128.39.210 (check it on the What Is My IP Address page)
Viewing 7 replies - 1 through 7 (of 7 total)
  • Drake

    (@marcoragogna)

    I have the same problem on SiteGround servers using SG Optimizer and no cloudflare.

    If I enable Cerber the cache system doesn’t work. @wpwench have you been able to solve it?

    Thread Starter wpwench

    (@wpwench)

    @marcoragogna yes I did solve it by removing the plugin and installing Wordfence. Sorry if that doesn’t help.

    Drake

    (@marcoragogna)

    Ok I found the issue. It is related to anti-spam settings, I disabled those and now the cache works.

    Plugin Author gioni

    (@gioni)

    Siteground has informed us that this is due to the following cache control headers coming from this plugin.

    Siteground’s staff have no idea what is going on. WP Cerber doesn’t set any header related to caching. Instead, it utilizes cookies as an element of its anti-spam engine. Siteground’s caching system does not cache pages with cookies in the HTTP header. You need to configure the caching system to ignore a cookie if the cookie’s name starts with a given prefix. The cookie prefix is set in the main WP Cerber settings. That’s it.

    @marcoragogna

    Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    There is no way we (SiteGround) can ignore cookie session and cache such pages. Basically, you are disabling our caching mechanism on all pages. Opening a cookie session for anything but to display user-speciffic content is a bad idea really.

    As to the caching headers, we honour those too. They might be coming from somewhere else – another plugin / theme but either will disable the cache.

    Thread Starter wpwench

    (@wpwench)

    Okay, so the information in the original post might not have been 100% correct because SG cache turned out to be interfering with 2 different plugins. I am guessing it was the anti-spam feature from this plugin and the cache control headers from the other plugin (worlpay).

    But bottom line, cache was missing with this worldpay disable and cerber active, and cache would hit with Cerber and worldpay disabled. Seems @marcoragogna figured it out though.

    Plugin Author gioni

    (@gioni)

    There is no way we (SiteGround) can ignore cookie session and cache such pages. Basically, you are disabling our caching mechanism on all pages. Opening a cookie session for anything but to display user-speciffic content is a bad idea really.

    WP Cerber does not use its cookies as session identifiers or anything specific to a user. Cookies are just cookies and they are used for many reasons not related to sessions.

    So, to make WP Cerber compatible with Siteground’s caching system, you need to disable
    “Protect comment form with bot detection engine” and “Protect all forms on the website with bot detection engine” in the anti-spam settings.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Issues with content not cacheing’ is closed to new replies.