• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question CloudFlare/DNS/Root Domain

J

Justin Buckkley

New Pleskian
Hello,

I have a question about the CloudFlare integration with Plesk, and how it works with domains that default/redirect to their root (domain.com).

I have a customer that has a domain that defaults/redirects to root (domain.com). It seems that when enabling CF for a domain, by default it is only routing traffic through CF if using the CNAME/www.domain.com. In this setup - is there any use in enabling CF? Or how can I utilize both CF and default/redirect to root?

Sorry if this has been covered or I'm just completely messing this up!
 
You must log in or register to reply here.

Similar threads

bigbear67
Question Network routing issue after update (loss of default route source IP / DNS failure on Ubuntu 24.04)
Replies
0
Views
871
bigbear67
bigbear67
B
Issue CRITICAL: Sitejet Extension /publish/run returning 302 Redirect
Replies
1
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
S
Forwarded to devs Preferred Domain & Alias Redirect behavior inconsistent after recent updates
Replies
2
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
D
Question Cloudflare DNS Extension - Clarification on a few things
Replies
3
Views
4K
Kaspar
K
N
Issue 421 Misdirected Request on Apache-only Plesk server after recent Apache update (CVE-2025-23048)
Replies
2
Views
11K
NatuurlijkHosting
N
Back
Top