WordPress.org

Ready to get started?Download WordPress

Forums

W3 Total Cache
"Error: No zones matching custom domain" error message. (19 posts)

  1. ranpha
    Member
    Posted 1 year ago #

    When I configure the CDN feature to use MaxCDN, I got the 'Error: No zones matching custom domain.' error message when doing a test within the CDN setting. What have gone wrong there?

    http://wordpress.org/extend/plugins/w3-total-cache/

  2. draven666
    Member
    Posted 1 year ago #

    I have the same problem...

  3. ranpha
    Member
    Posted 1 year ago #

    So, no comments about this one from developers? The latest update I have just installed now still has the same problem.

  4. companyjuice
    Member
    Posted 1 year ago #

    I have the same problem. I've tried setting "Application URL" and "Callback URL" to my http://www.domainname.com, but still this error persists.

  5. companyjuice
    Member
    Posted 1 year ago #

    The solution for me was to

    1) generate a new API key with NetDNA/MaxCDN by visiting http://cp.maxcdn.com/ and selecting APIs, then

    2) delete my existing Pull Zone that is tied to the CNAME that I want to use (cdn.domainname.com), then

    3) create a new Pull Zone in my NetDNA/MaxCDN account (more info on this step can be found here http://www.wpbeginner.com/wp-tutorials/how-install-wordpress-cdn-solution-maxcdn/), then

    4) update my DNS CNAME to this new zone (temporary url), and finally

    5) locate my "Alias" for my MaxCDN by going to Account > Settings at https://cp.maxcdn.com/account/settings

    I also needed to Bummer that the zone didn't transfer over when I upgraded from W3 Total Cache to the latest version that supports the new API key management system from NetDNA/MaxCDN. No one's fault here, but I wish it wasn't such a surprise troubleshooting hour for me right now. But it's working now!

    Thanks -- Marty McGee, http://www.companyjuice.com

  6. ranpha
    Member
    Posted 1 year ago #

    Even after following what you said above, I still get the same error.

  7. Frederick Townes
    Member
    Plugin Author

    Posted 1 year ago #

    The cname and Test CDN issue will be fixed in next release.

  8. the9man
    Member
    Posted 1 year ago #

    Facing the same issue... When will be next release?

  9. ranpha
    Member
    Posted 1 year ago #

    This problem still happens with the new version. AFAIK, MaxCDN is now broke with W3 Total Cache.

  10. Marius Jensen (Clorith)
    Member
    Posted 1 year ago #

    I too was hoping that this update would address it, especially as it was posted 2 months ago that it would be fixed with the next release at the time.

  11. Josh Carr
    Member
    Posted 1 year ago #

    From what I can tell, it has nothing to do with the functionality in this version.

    Yes, the test button is broken... but it's still serving my content from the cdn.

  12. ranpha
    Member
    Posted 1 year ago #

    It doesn't in my case. The CDN is basically broken when I tried to enable MaxCDN caching in the past two versions of W3 Total Cache.

  13. Marius Jensen (Clorith)
    Member
    Posted 1 year ago #

    This is my problem as well, it's as if it can't verify the CDN without this test passing as I don't get any buttons to add stuff like my theme files and such, it happily makes links to the cdn for everything in my theme though, which of course breaks the site.

  14. jshare
    Member
    Posted 1 year ago #

    Confirmed this problem as well.

    The test button generates the error message even if the custom domain works perfectly fine from the MaxCDN side, and when I click Save All Settings, W3TC does begin using the custom domain regardless of the test button's error message. So at least I can use my CDN.

    Incidentally, I can get 'Test passed' if I use the Temporary URL as provided in the Zone Configuration tab of the MaxCDN Pull Zone admin panel.

  15. jshare
    Member
    Posted 1 year ago #

    Confirmed this problem as well.

    The test button generates the error message even if the custom domain works perfectly fine from the MaxCDN side, and when I click Save All Settings, W3TC does begin using the custom domain regardless of the test button's error message. So at least I can use my CDN.

    Incidentally, I can get 'Test passed' if I use the Temporary URL as provided in the Zone Configuration tab of the MaxCDN Pull Zone admin panel.

  16. olly connelly
    Member
    Posted 12 months ago #

    Ditto for the behaviour jshare's reporting.

    (Damn splendid plugin otherwise Frederick.)

  17. olly connelly
    Member
    Posted 12 months ago #

    For the record, am using these instructions:-

    http://support.netdna.com/pullzone/wordpress-w3-total-cache/

    "In the “Replace site’s hostname with”, please use the Temporary CDN URL which you have been given after you have created your Pull Zone. If you are using a Custom Domain, such as cdn.mysite.com, you can input that in the text box."

  18. olly connelly
    Member
    Posted 12 months ago #

    Follow-up: While the test says fail on the plugin's CDN page, the actual functionality is working, for me at least, not just for one but for several CNAME's.

    So for anyone else with this concern, perhaps take the message with a pinch of salt, maybe purge the CDN cache (I did, not entirely sure it was necessary but it's no big deal) test your site and see from what hosts, for instance, your assets are resolving using a tool like YSlow in Firebug.

    "(Damn splendid plugin otherwise Frederick.)" ... Otherwise? HEavily assisting a 98/100 YSLow score, I meant entirely. :)

  19. Josh Carr
    Member
    Posted 12 months ago #

    @ranpha, clorith, jshare -- try removing the plugin completely and set it up from scratch. All of my tests have been with fresh CDN settings (wasn't using it until this most recent update). It's possible that some lingering settings could be interfering with your functionality. Enable the CDN and check the source of your site to see if it's using the CDN for static content.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.