CDN Acceleration & Caching

A CDN caches your site's content at edge nodes around the world, so visitors are served from nearby — improving speed and easing the load on your origin. This article shows how to put a site behind the CDN on NextCLi.

CDN products: acceleration capabilities and plans

Create acceleration

• Go to "Console → CDN → Create".
• Enter the domain to accelerate and the origin (an IP or a domain).
• Choose the origin protocol and a basic cache policy, then confirm.
• Point the domain's DNS (CNAME) to the acceleration address as instructed; if the domain is managed on NextCLi, configure it directly in DNS.

Enable CDN: choose the domain to accelerate

HTTPS

Enable HTTPS for the accelerated domain so visitors reach the edge nodes over https. After completing certificate configuration as prompted, the edge serves traffic encrypted.

Caching & purge

• Cache policy: set cache duration by file type/path — long cache for static assets, no or short cache for dynamic content.
• Cache purge: after updating content, if the edge still returns the old file, manually purge the specific URL or directory so the edge pulls the latest from the origin.

Analytics

On the CDN detail page, view analytics such as traffic, requests and hit rate to evaluate acceleration and bandwidth usage.

Common questions

• Still seeing old content after enabling? Run a cache purge; confirm the DNS points to the acceleration address.
• Origin fetch failing? Check the origin address, port and origin protocol are correct, and that the origin allows the fetch requests.
• HTTPS not working? Confirm certificate configuration is complete and the domain's DNS points to the acceleration address.

---

Related references

• Free DNS, free CDN and free DDoS protection with Cloudflare
• Use together with: Domain Registration & DNS