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’.

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

I am not sure how that happened.

Can you enable debug on the wordpress site and check if there are errors and could you please give some more information about the system setup?
– PHP version
– nginx version

Hi,

Thank you for using our plugin.

The hosts.json should have your physical webservers and not the ‘load balancer’ IP. The FastCGI cache needs to be purged on the physical servers.

Hm, I’ve missed the other ‘Fatal error’. After disabling the wp-rss-multi-importer everything worked fine.

Weird, well the version of wordpress is:
$ wp core version
4.9.7

and the plugin list is:
$ wp plugin list
+——————————–+——–+———–+————-+
| name | status | update | version |
+——————————–+——–+———–+————-+
| ad-inserter | active | none | 2.3.14 |
| akismet | active | none | 4.0.8 |
| antispam-bee | active | none | 2.8.1 |
| bunyad-siteorigin-panels | active | none | 1.3.7.5-mod |
| bunyad-shortcodes | active | none | 1.0.6 |
| bunyad-widgets | active | none | 1.0.5 |
| cache-control-by-cacholong | active | none | 4.0.1 |
| contact-form-7 | active | none | 5.0.3 |
| cookie-law-info | active | available | 1.6.0 |
| google-analytics-for-wordpress | active | none | 7.0.9 |
| nextgen-gallery | active | none | 3.0.1 |
| really-simple-captcha | active | none | 2.0.1 |
| wp-rss-multi-importer | active | none | 3.15 |
| velvet-blues-update-urls | active | none | 3.2.8 |
| wp-pagenavi | active | none | 2.92 |
| wp-photo-album-plus | active | none | 6.9.06.008 |
| wordpress-seo | active | none | 7.8 |
+——————————–+——–+———–+————-+

As far as I can see it is up 2 date.

The error is reproducable.

Regards, Matthijs

Hello @ateliershen and @draven666,

The requirements in the documentation weren’t properly defined. Therefor it was obviously unclear how this should be setup. The additional requirement is a Nginx server with fastcgi_cache enabled. In the Nginx configuration you should pass the CC_NGINX_FASTCGI_CACHE_PATH parameter to PHP with the proper path to the cache. In the tab installation you can find a link to the Nginx documentation where this functionality is described.

Keep in mind that the plugin in itself doesn’t provide any caching functionality. It only provides a way of clearing the fast-cgi and or pagespeed cache generated by an Nginx server as we have setup for our customers.

Kind regards,

Durk Hellinga
Cacholong