A CDN in front of cPanel

A CDN in front of cPanel means the edge caches static files (and sometimes HTML) while your CDN origin stays on LogicWeb. We are not a CDN. Your site still runs on cPanel with LiteSpeed, AutoSSL, and mail on the origin server. If you orange-cloud the apex and www, AutoSSL’s HTTP-01 check often fails unless you leave those names direct, skip the challenge path, or use DNS-01.

Think of four parts working together. DNS may point at the CDN or straight at us. The edge has its own cache, purge tools, and cookie rules. The origin still serves the real site, certificates, and email. You also need one origin hostname that never goes through the proxy, so ACME and debugging hit the server, not last week’s cached response.

Set DNS so AutoSSL still works

When a CDN proxies (oranges) your records, HTTP-01 requests stop at the vendor. AutoSSL on cPanel needs to serve a challenge file from the account itself. Leave the web names grey (direct to origin), use a DNS-01 method your vendor supports, or exclude the ACME path from the proxy. Keep mail out of the proxy entirely. MX records through a CDN create mail problems we cannot fix at the edge.

• Point a bypass hostname at the origin A record and never proxy it.
• Use that name for AutoSSL checks and for curling the real Server header.
• Create the bypass name in DNS before you proxy the apex or www.

Purge the CDN and LSCache together

Purging only LSCache leaves the CDN holding an old homepage. Purging only the CDN makes the edge pull stale HTML from origin again. After a publish, clear both, or keep a short edge TTL on HTML. Caching HTML at the CDN is not always right for shops. You need a clear plan for cookies, carts, and logged-in users. Static assets are the easy win; HTML caching is a product choice.

What still lives on the CDN origin

cPanel, LiteSpeed, and JetBackup stay on the origin. The CDN does not back up your database or run cron. When the edge has trouble, the bypass hostname shows whether the origin itself is healthy. Your CDN origin for HTTPS is the web hostname. Mail hostnames should stay on plain A or AAAA records, with rDNS if you send mail. Do not proxy MX, do not proxy the mail hostname, and do not let the vendor rewrite SPF. Mixing web proxy settings with mail is how certificate and deliverability tickets show up on the same day.