Skip to main content

Custom domain on a dedicated gateway

You can serve a dedicated gateway from a custom domain (e.g. cdn.example.com instead of my-gateway.myfilebase.com). Filebase auto-provisions a Let's Encrypt TLS certificate for the domain.

Third-party CDN policy

Point your custom domain directly to Filebase. Proxying IPFS gateway traffic through another CDN is not permitted. See the third-party CDN policy.

Add a custom domain​

  1. Open the gateway in the console.
  2. Settings → Custom Domain → Add Domain.
  3. Enter the hostname.
  4. Filebase shows you the CNAME target.
  5. Add a CNAME record at your DNS provider: 
    cdn.example.com.   CNAME   my-gateway.myfilebase.com.
  6. If you use Cloudflare DNS, set the gateway record's proxy status to DNS only, with proxying disabled. Keep the record DNS-only after the certificate is issued. See Cloudflare's proxy-status documentation.
  7. Wait for DNS propagation (usually a few minutes).
  8. Filebase verifies the CNAME and provisions the certificate.

Once issued, the gateway is reachable at https://cdn.example.com/ipfs/{CID}.

Root domains​

For root domains (e.g. example.com), use an ALIAS / ANAME record if your DNS provider supports it. Cloudflare's CNAME flattening, Route 53's alias records, and most modern DNS providers support root-domain CNAMEs. Keep root-domain gateway records pointed directly to Filebase as well. On Cloudflare, use DNS only with proxying disabled; CNAME flattening does not require enabling the CDN proxy.

TLS auto-renewal​

Filebase auto-renews the Let's Encrypt certificate before expiry. As long as the CNAME stays valid, no manual action is required.

If you receive 403 Forbidden with the message CDN proxying is not allowed, follow the CDN proxy troubleshooting steps.

What's next​