EmberlyEmberly Docs

Custom Domains

Serve your uploads from your own branded domain with automatic TLS certificates.

Cloud only. Custom domains run on embrly.ca's managed Cloudflare integration and aren't available on self-hosted instances — see Cloud vs. Self-Hosted.

Custom domains let you host your Emberly files under your own domain — e.g., files.yourbrand.com — with automatic TLS via Cloudflare.

Domain Slot Limits

Your total domain slots come from three sources:

PlanBase Slots
Spark3
Glow5
Flare10
BlazeUnlimited
InfernoUnlimited
EmberUnlimited

Bonus slots stack on top:

  • GitHub contributors earn +1 to +5 slots — see Contributor Perks
  • Discord boosters earn +1 to +3 slots — see Discord Perks
  • Additional slots can be purchased individually in your dashboard

Total = Base Plan + Perk Bonuses + Purchased


Setting Up a Custom Domain

Step 1: Add Your Domain

  1. Go to Dashboard → Domains
  2. Click "Add Custom Domain"
  3. Enter your domain (e.g., files.yourdomain.com)
  4. Click "Add Domain"

The domain is created with status awaiting_cname.

Step 2: Configure DNS

Add a CNAME record at your DNS provider:

TypeTarget / ValueTTL
CNAMEcname.embrly.ca300

For a root domain (@), use a CNAME-flattening provider (Cloudflare supports this natively).

Cloudflare users

Set the record to DNS only (grey cloud) during verification. You can enable proxying (orange cloud) after the domain is active.

Step 3: Verify

  1. Return to Dashboard → Domains
  2. Click "Verify" next to your domain
  3. TLS is automatically provisioned — verification usually completes within a few minutes

Setting a Primary Domain

Your primary domain is used for all new uploads automatically:

  1. Open your domain list
  2. Click the ⋯ menu next to a verified domain
  3. Select "Set as Primary"

You can still select a different domain per-file during upload.


Troubleshooting

StatusMeaning
awaiting_cnameDNS record not yet detected
pendingCloudflare is provisioning TLS
activeDomain is live and serving files
errorVerification failed — check DNS

CNAME not detected?

  • DNS changes can take up to 24 hours to propagate
  • Verify the target is exactly cname.embrly.ca
  • Use dig CNAME yourdomain.com to check the current value

Certificate errors?

  • Ensure the domain is verified (active) before enabling Cloudflare proxying
  • If using Cloudflare, temporarily set to DNS-only and re-verify

For more detail see the Domain API reference.

On this page