ze3kr

Yes, use “Cache Everything” can cache HTML page, but I had tried this settings, it also cache 404 page. And CloudFlare doesn’t provide clear cache by tag feature for free so it’s hard to manage cache on a same domain.

You are right, KeyCDN is not a free service, but CloudFlare is free forever. But CloudFlare doesn’t support clear cache by tag, custom SSL and cache HTML page for free.

CloudFlare can make your images, CSS and JS file load faster, but not HTML, it doesn’t cache HTML file, but KeyCDN can. Both of them can help you prevent DDOS attack and let your server support HTTPS and HTTP/2, and CloudFlare is easier to use(however you have to change your DNS service).

Because KeyCDN only support to set the CNAME record on the DNS server. If you only want to use the root domain without “www”, you cannot use KeyCDN.

I already explain this on FAQ page.

And by the way, I updated my plugin Full Site Cache for KeyCDN to support this plugin, which I had introduced here.

Please check does zonealias is created or not. This plugin will also automatically create zonealias for you, but it seems that the request to create zonealias is timeout and this plugin doesn’t set a fault-tolerant for that, it will be fix in the next version.

And if the zone is created, add zonealias by yourself. And go to the settings page of this plugin, if it show the purge button, it means you have done all setup.

And you need to check origin server IP, the results isn’t always right, especially you use shared hosting. This plugin will send a HTTP request to your server itself to check the server own IP, it’s works well at most of time, but not always work.

First, you need to use custom URL. And you don’t need to add zone by you self, this plugin will add the zone automatically. And
$fsckeycdn_useHTTPS = false; doesn’t effect your KeyCDN HTTPS, it set to false because it detect your server doesn’t support HTTPS. If your server support, please go to CloudFlare and turn ssl to full ssl.

The domain will be unreachable until you go to the next step.

Yes, I found why this error happened. I did’t push some code directly to the SVN. Now this plugin is able to work.

I’ll fix it in the next version. But before that, you can turn the debug mode off for your PHP. Set display_errors to Off. (Add display_errors = Off in php.ini.

Please check /srv/users/serverpilot/apps/****tips/public/wp-content/plugins/full-site-cache-kc/functions.php this file, it must exist, if not, download here https://downloads.www.ads-software.com/plugin/full-site-cache-kc.2.0.0.zip and upload functions.php file to /srv/users/serverpilot/apps/****tips/public/wp-content/plugins/full-site-cache-kc/

In my test, it doesn’t appear this problem. I think it might because of when this plugin is updating online on WordPress, it updated full-site-cache-kc.php before functions.php, so it have this problem. Try to install this plugin via FTP, or deactivate this plugin before update.

The new version had fix this bug, if functions.php not exist, returns a error and not effect WordPress.

If the error still exist, please tell me.