> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.faaaster.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How do I turn on the CDN and edge caching on Faaaster?

The **CDN Proxy, WAF & Edge caching** is set from the site's **Performance** tab, **CDN & edge cache** section. It serves your site through a global network of edge servers.

> **Prerequisite** — you must first **connect your own domain** to the site, from the **Domains** tab. The interface says so explicitly: the proxy isn't available as long as the site only has its temporary `.faaaster.dev` address. The setting is reserved for the Owner, Admin and Member roles.

## What the proxy gives you

According to the interface: "Your domain is served through the edge network (`proxy.faaaster.cloud`): CDN, WAF, and cache as close to visitors as possible."

So, three things:

- **CDN** — your content is served from the point closest to the visitor;
- **WAF** — a web application firewall in front of your server;
- **edge cache** — pages are cached as close to visitors as possible.

## Turning it on

1. Connect your custom domain from the **Domains** tab.
2. Open the **Performance** tab.
3. In the **CDN & edge cache** section, turn on **CDN Proxy, WAF & Edge caching**.
4. The **Enable proxy / CDN** window opens: at your registrar, point your domain to `proxy.faaaster.cloud`, click **Verify**, then **Enable proxy**. That button only becomes active once DNS is compliant; propagation can take a few minutes.

The status is shown next to the label — **inactive** until it is turned on, **active** afterwards. Depending on the site, the switchover happens without downtime or with a brief restart: the notification displayed tells you which.

![The CDN & edge cache section of the Performance tab, with the proxy status.](https://storage.crisp.chat/users/helpdesk/website/-/9/d/2/d/9d2d3e0b7134b800/act-perf-cdn-en_dq6avo.png)

## The requirement: a subdomain

> ⚠️ **A root domain cannot use the proxy.** The interface explains it: "A root (apex) domain cannot carry a CNAME: it stays in Standard mode."

This is a technical DNS constraint, not a Faaaster limitation: the standard forbids a CNAME at the root of a domain, and the proxy needs one. On a root domain, the **Enable proxy / CDN** window shows "The proxy requires a subdomain (e.g. www): a root domain cannot carry a CNAME" instead of the **Enable proxy** button.

**The solution**: serve your site from `www.yourdomain.com` — or another subdomain — and redirect the root to it. This is also Faaaster's recommendation, shown directly on the domains screen.

## The two domain states

In the **Domains** tab, the **Proxy** column of the table shows **Enabled** or **Disabled**. The domain's DNS settings panel, for its part, offers two modes:

| Mode | What it means |
| --- | --- |
| **Standard** | Proxy disabled — traffic goes directly to your server. |
| **Proxy / CDN** | Proxy enabled, with CDN, WAF and Edge Caching. |

## Purging the edge cache

The **Clear cache** button in the **Performance** tab — like **Clear cache** in the site banner — purges the server cache and, when the proxy is active, the edge cache. Note: the server cache (FastCGI) is **already cleared automatically** whenever content changes — a manual purge is mostly worthwhile after a code change.

> **If a change doesn't show up even though you've cleared the cache**, clear your browser's cache too, or test in a private window. The most stubborn cache is often your own.

👉 [How do I connect my domain name?](https://help.faaaster.io/en-us/article/connect-a-domain-3t4zf9/) · [My site is slow](https://help.faaaster.io/en-us/article/my-site-is-slow-1ng4uql/)