Support » Plugin: W3 Total Cache » won't use existing MaxCDN pullzone

  • Installed plugin update on existing site where CDN was working with W3. Required authorization. Done. Then required the creation of a pull zone.

    The WordPress install is in /wp so it appears W3 is trying/forcing the creation of a pullzone for and it will not see the pull zone for the root (which it has been using all along and I don’t want to lose since it is used for other non-WordPress caching as well).

    Is there a way to restore the ability to hand-enter the pull zone, or to see the pullzone for the root of the domain?


Viewing 5 replies - 1 through 5 (of 5 total)
  • This is still an issue on my sites. I’ve used MaxCDN with W3TC for a long time. The pull zones were already configured. And they apply to the ROOT of the domain, even though WordPress is installed in a subdirectory.

    Been running without the cache… would be great to be able to get the CDN working again…


    I am in the same boat here, It is not letting select my existing (already configured) pullzone after upgrading from ->

    It seems as if there should be a selector (drop-down) that should let me choose my existing zone, but there is not, instead I am faced with the following:
    Notice there is only a button to “create” a zone, and not select an existing one.

    When I click the button and enter the name of my existing Pull Zone I get the following error message:
    “Something is wrong:
    You have reached the limit of zones you can create”

    Luckily I am testing this on a staging site so my production site is not affected and still happily using MaxCDN w/ W3TC, but I’d like to upgrade this plugin on production, but this issue is a blocker.


    I am in the exact same situation, WordPress installed in root.

    I can’t choose the zone I already created in MaxCDN, but if I click the “Create pull zone” button on the WTC CDN tab, I get the “Something is wrong: You have reached the limit of zones you can create” error.

    Did any of you resolve this issue?

    I am using WordPress 3.5.2 and W3 Total Cache

    Any advice is greatly appreciated!


    My issue has been fixed, thanks to MaxCDN chat support. 🙂

    I had originally set up my origin as

    Once the support rep changed the origin to, and I clicked Save all settings, the “Select pull zone” dropdown list appeared!

    Clicking the “Test MaxCDN” button now results in the green box “Test passed.”


    After emailing MaxCDN support I figured out the issue. You must access the admin portion of the site using the same hostname as the pull zone. Therefore if you have a staging or dev site that uses a different hostname ( then the production hostname ( the plugin will exhibit this behavior. So I pushed my changes to production and everything is working just fine.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘ won't use existing MaxCDN pullzone’ is closed to new replies.