• Hello,
    The plugin cant seem to purge pagespeed.
    I was able to fix fastcgi by adding fastcgi_param CC_NGINX_FASTCGI_CACHE_PATH in the nginx configuration file.

    is there any documention to make the pagespeed cache work.

    Below the error from log
    Time: 16-07-2021, 01:02:27 (UTC)
    Message: Purge pagespeed cache: https://127.0.0.1/*
    Time: 16-07-2021, 01:02:28 (UTC)
    Message: Purge fastCGI cache: https://127.0.0.1/cacholong_cc_action

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Preliot

    (@preliot)

    We’ve just released a new version of Cache control by Cacholong. There’s no need anymore for the CC_NGINX_FASTCGI_CACHE_PATH parameter. Could you download the lateste version and try again?

    Your log output suggests both caches are purged. If purging the pagespeed cache still fails with the most recent plugin, you can debug the purge request:

    wp-config.php

    define('CACHOLONG_CACHE_DEBUG_HTTP_API_REQUEST', true);

    • This reply was modified 3 years, 4 months ago by Preliot.
    Thread Starter arber14

    (@arber14)

    Hello,
    After the update, I removed the CC_NGINX_FASTCGI_CACHE_PATH in the nginx configuration file.
    Now it doesn’t purge the fastcgi.

    I added define(‘CACHOLONG_CACHE_DEBUG_HTTP_API_REQUEST’, true); in the config file but dont see any log in wp-content/cacholong-cache-control.log.

    Help please!

    Thread Starter arber14

    (@arber14)

    I think theres a bug in the plugin.
    It works only when DEBUG is true.
    define(‘WP_DEBUG’, true);
    define(‘CACHOLONG_CACHE_DEBUG_HTTP_API_REQUEST’, true);

    Can you fix it?

    Plugin Author Preliot

    (@preliot)

    Let’s take a step back and make sure all the requirements are met. It’s easier to help you when everything is clear:

    1) Which WordPress version are you using?
    2) Did you install version 5.4.1 of this plugin?
    3) Does you nginx contain the pagespeed and fastcgi module?
    4) FastCGI ‘purge all’ only works when you install the latest patch.

    If i’m reading this correctly, pagespeed is working now and fastcgi doesn’t? Assuming that’s the case, does a single purge work (f.e. purging a single url on the settings page) and the purge all fails? If that’s the case, please install the latest fastcgi module/patch.

    Concerning the WP_DEBUG / CACHOLONG_CACHE_DEBUG_HTTP_API_REQUEST combination, you are right. This is a (small) bug, which will be fixed in the next release. For now just use the combination to debug your issue.

    Plugin Contributor Cacholong

    (@cacholong)

    Hello,

    First of all, this plugin is created specifically for our platform but it can be used on other platforms if the requirements are met:

    With the latest version you need nginx with the following modules (or builtin into nginx):
    – pagespeed (see: https://www.modpagespeed.com/)
    – http-cache-purge (see: https://github.com/nginx-modules/ngx_cache_purge)

    Then you need some additional configuration (per vhost) in nginx (pagespeed):

    pagespeed EnableCachePurge on;
    pagespeed PurgeMethod PURGE;

    And for nginx fastcgi cache purge (per vhost):

    location ~ /purge(/.*) {
        fastcgi_cache_purge <cache zone> "$scheme$request_method$host$1";
    }

    If these modules are installed correctly into nginx and the configuration above is correctly applied then you should be able to use the plugin.

    I assume you are able to configure nginx correctly for wordpress.

    Regards, Matthijs

    Thread Starter arber14

    (@arber14)

    Hello,

    When activate SSL. I get this error

    Time: 27-07-2021, 07:33:56 (UTC)
    Message: Purge fastCGI cache: https://127.0.0.1/cacholong_cc_action
    Time: 27-07-2021, 07:33:56 (UTC)
    Message: HTT API got following error(s):
    Time: 27-07-2021, 07:33:56 (UTC)
    Message: Array
    (
        [0] => cURL error 7: Failed to connect to 127.0.0.1 port 443: Connection refused
    )

    any idea why?

    Plugin Author Preliot

    (@preliot)

    Does this mean there are no issues when using the plugin with http?

    Thread Starter arber14

    (@arber14)

    Hello,
    I reverted back to the old version. With http it works but when I activate HTTPS it doenst.
    Any idea why? How to fix it?

    Plugin Contributor Cacholong

    (@cacholong)

    How did you activate SSL?

    What does your nginx configuration looks like?

    To me, it seems the nginx configuration is missing the default configuration for listening on port 443. Hence the error ‘Connection refused’.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘pagespeed error’ is closed to new replies.