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-
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-