ze3kr

I also got 503 error until I delete this plugin

I think it is not the problem of Cache system. My site have some video which the URL is beginning with https, and not work.

https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fwww.ze3kr.com%2Ffeed%2F

I tried to replace

<enclosure url="https://

To

<enclosure url="https://

Then it works.

Also see: https://stackoverflow.com/questions/29985571/w3c-validator-says-feed-does-not-validate-url-must-be-a-full-url-whats-wr

I have found this bug, it is because the max_srcset_image_width is return 1 when this plugin is enabled. It returns 1600 when this plugin is disabled. I tried remove it and it works!

function remove_max_srcset_image_width( $max_width ) {
    return false;
}
add_filter( 'max_srcset_image_width', 'remove_max_srcset_image_width', 99 );

There definitely some thing break the srcset function, as I disabled this plugin, the srcset is correct. I am going to have a deep look in it.

You need to disable the orange cloud (CDN) on the Cloudflare, use DNS only. and then go to KeyCDN and add Zonealias. KeyCDN will check the CNAME so before add Zonealias you must make the cloud gray. And to use the KeyCDN cache, you should not use Cloudflare’s CDN.

Does wp-admin.sembec.com.au and https://www.sembec.com.au use same WordPress install and same database? It should be same. A single site but two domains. If you installed this plugin on https://www.sembec.com.au, it should also be here wp-admin.sembec.com.au.

Can you access this page: https://wp-admin.sembec.com.au/wp-admin/ or https://wp-admin.sembec.com.au/wp-admin/options-general.php after you logged in?

Make sure this plugin is enabled in this page: https://wp-admin.sembec.com.au/wp-admin/plugins.php

It seems a WordPress error. Try to add this

define('COOKIE_DOMAIN', 'sembec.com.au');

At the top of wp-config.php. (After <?php)

If it works, please tell me.

Could you please give me a screenshot so I could figure out what’s wrong?

• This reply was modified 7 years, 8 months ago by ze3kr.

Could you please to / have you ever tried do these things and try to figure out the problem?

1. Login to your site and go to the domain with wp-admin, see the page of the post/page and see if the problem solved.

2. Disable this plugin(and nothing else), and go to the post/page without wp-admin domain, and append a query (like https://www.example.com/?randomnumber to make sure no cache), see if it work.

This is only the ways to find where the errors are, not the ways to solve problem (it needs to do some change in code)

I think it might a bug of the rewriting system of this plugin.

• This reply was modified 8 years, 1 month ago by ze3kr.

Sorry for the delay, but I don’t know which page have this problem (admin page or home page), and please tell me which plugin does not work and which theme you are using, so it’s easy for me to reappear this bug.

For now, this plugin does not support wildcard configuration. To support this feature, it needs to have a wildcard SSL certificate in order to support HTTPS, and it still needs to set a lot of wp-admin domains for each site.

However, if you have tons of sites, sub-dictionary installed WordPress might work (I didn’t test this, but it should work, and to do that might need to reinstall WordPress).

I don’t think woocommerce will be able to cache the whole site, because it has so many dynamic pages, you can try CDN Enabler to only cache CSS, JS, Images instead,.

The best choice is to only use:

Cache Enabler + CDN Enabler + Full Site Cache for KeyCDN

The CDN Enabler only let you to enable cache for CSS, JS and Images, move these resources to another domain, and does not cache the HTML pages.

However, with this plugin (full site cache), almost all content will be cached, so the CSS, JS and Images needn’t have another domain, use more than one domain will be slower, because it will add more delay on TLS connect and resolving DNS.

Cache Enabler, which can reduce the server response time if the page is cached, the cache file will saved on server but not on KeyCDN edge server, but will have a better cache rate. It will have an obvious effect if your server’s performance is bad, or some theme or plugins slows down your website,

The new version add support to setup this plugin on the root domain, but I only recommend to enable this if your DNS provider supports ANAME or CNAME Flattening (instead of CNAME), such as CloudFlare, DNS made easy and dnsimple support this. However, your DNS provider might not support ANAME, but somehow you might still be able to set a CNAME on your root domain, but this is NOT recommend because it might cause error.

To enable this, just add this to wp-config.php

$fsckeycdn_root_domain_setup = true;

See faq to know more about this