• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

CloudFlare problem with non www domains

Alan_SP

Basic Pleskian
Thing is, when you use partner implementation of CloudFlare, like Plesk does, you can't use non www domains (CloudFlare refers to them as naked domains). You only could have CloudFlare on www.domain.com.

This is problem that exists for years now and probably wouldn't be solved.

To use CloudFlare and non www domain, you need to add domain directly with CloudFlare like regular CloudFlare user, bypassing CloudFlare Plesk extension completely (although, you still use second part, StopTheHacker).

It would be good to put some text in that direction in extension description. It took me a while to discover that fact, when I noticed that there's no CloudFlare caching of my website. Having information upfront would be useful in speeding up the process.

Also, you link page where CloudFlare states that: https://support.cloudflare.com/hc/e...-I-use-a-naked-domain-no-www-with-CloudFlare-
 
@Alan_SP,

It is not only about "naked domains", CloudFlare extension is also not working if Plesk is not working as a primary nameserver.

Note that StopTheHacker from CloudFlare also does not work, in the case that Plesk is not working as a primary nameserver.

In general, the whole CloudFlare extension is rather useless, since

a) CloudFlare itself has many pitfalls and undesirable disadvantages, with the number of disadvantages even higher than in the case of using CloudFlare directly (and not the extension),

b) the extension itself should not be dependent of Plesk functioning properly as a primary nameserver: the extension code uses the API and a simple API call will allow CloudFlare to set the most important DNS records (at the nameservers of CloudFlare), allowing traffic to pass or bypass CloudFlare and caching of specific requests. However, this does not work.

In short, the CloudFlare extension is flawed.

Just use CloudFlare directly (or rather, do not: the suggested benefits of CloudFlare are not that relevant and most of those alleged benefits are actually disadvantages).

Regards....
 
Back
Top