cdnca
Browse all docs

Site user guide

For regular users: your sites, DNS, purge and prewarm, origins, HTTPS, false positives, plans and bills, and account security.

For regular users (site owners) on a control plane: managing your own sites, origins, HTTPS, cache, protection, plans and account in the user console.

Whether you can create sites, see plans and bills or create API keys depends on your account's permissions. If a button is missing, ask your control-plane administrator; do not borrow an admin account.

Add or manage your sites

  1. Sign in to the user console and open "Sites → Site list".
  2. If your account can manage sites and the page shows "Add site", create one here: choose a plan, enter the domains and origin and submit (fields are explained in add a site). Otherwise search for your own or assigned domains.
  3. Open the site and use the "Basic", "Origin", "HTTPS settings", "Cache" and protection tabs as needed.
  4. Click "Save changes" at the top after editing. If the page warns about unsaved changes, save or discard them before leaving.
  5. Go back to the list or refresh to confirm the change stuck.

If a site will not open, check that it belongs to or is assigned to your account. On a save conflict, load the latest configuration, make sure you are not overwriting someone else's change, then edit again.

Point your domain

  1. Find the site in "Site list" and copy the value in the "CNAME" column.
  2. Sign in to the DNS provider for the domain and add a CNAME record. For www.cdnca.com the host is www and the value is the full CNAME you copied.
  3. Save, wait for DNS to update and open the site. For HTTPS continue with enable HTTPS.

If the CNAME column shows "Generating", wait; the page refreshes by itself. If it shows "Generation failed" or stays empty, send the domain and the message to your administrator. Never use the origin IP as the CNAME value.

Purge and prewarm

When visitors still see old content after an update, purge the cache.

  1. Open "Sites → Purge and prewarm" and choose "Purge URL", "Purge directory" or "Prewarm".
  2. Enter one full address per line in the URL list:
  • Purge URL and prewarm: for example https://www.cdnca.com/assets/logo.png.
  • Purge directory: ending in /, for example https://www.cdnca.com/assets/.
  1. Click "Submit task". In "Create purge/prewarm task" enter this site's "Site ID" and check the task type and targets. Leave the node field empty to send it to every node serving the site.
  2. Click "Submit task" in the dialog and close it once you see the result.
  3. Open "Operation history", find the task by site and state and click "View details" for each node's result.

"Site ID" is the site's full identifier, not the domain and not the short number shown in the list. If unsure, ask your administrator for it; do not type the domain there. Up to 500 addresses per task; the page shows today's quota.

If some items fail, read the reason in the details and click "Retry failed items". If the connection drops after submitting, check the history before creating the same task again.

Change the origin

  1. Open "Sites → Site list" and go to the site's "Origin" tab.
  2. Edit or add an origin and fill in the address, port and other required fields. Use only origins you manage and the nodes can reach.
  3. Click "Confirm" in the origin dialog. This only updates the draft; check the origin list on the site page.
  4. Click "Save changes" at the top and wait for the result; reopen the site to check the address and publish result.

Fix validation errors as the fields say; if the result is pending, click "Load latest configuration" before editing again. If the site breaks after switching, switch back and ask your administrator to check the access logs; do not submit untested fallback addresses.

Enable HTTPS or handle expiry

  1. Open "Sites → Certificates" and make sure a valid certificate covers the site's domains. If not, click "Request certificate" on the "Automatic" tab, or upload and activate one on the "Certificate assets" tab.
  2. Open the site's "HTTPS settings", turn on "HTTPS access" and set the HTTPS ports. Turn on "Force HTTPS" if HTTP should redirect.
  3. Under "Certificate" choose a valid certificate for the site's domains and click "Apply certificate"; the page confirms it is bound and the publish task is queued.
  4. Check the certificate, expiry and publish result, then open https://www.cdnca.com in a browser.

If a request fails, check DNS and the validation method; if it is bound but HTTPS fails, check the domains it covers and the publish state. Near expiry, confirm auto-renewal first and do not unbind a still-valid certificate. Request and renewal progress is on the "Certificate orders and renewal status" page, which is not in the sidebar yet: add /dashboard/site/cert/orders to your control-plane address.

False positives

  1. Note the time, domain, request address (without sensitive parameters) and the request ID shown on the page.
  2. Open "Analytics → Site block log", "WAF log" or "Block events", find the record by domain and time, and see which rule matched and what happened.
  3. Send the rule, time, cleaned address and request ID to your administrator. If your account manages that rule and you understand the impact, you may change only that rule or add a narrow exception. Do not turn off protection for the whole site or allow broad networks.
  4. Test the affected request and normal requests again, then check the logs.

If you find nothing, widen the time range and check the log type. Never submit request content with passwords or tokens.

Plans, usage and bills

  1. "Plans → My plans": name, status and expiry.
  2. "Plans → Buy plans": check product, price, limits, term and amount before buying or renewing.
  3. "Plans → Traffic packs" and "Usage": traffic balance and usage history, or usage per plan and date; one query covers at most 167 days.
  4. "Plans → Monitoring alerts": plan alerts and period status.
  5. "Account → Consumption records" for orders; "Account balance" and "Balance ledger" for top-ups and charges.

If an order exists but the plan does not show, check the order; if a payment is unclear, do not pay again. For expiry or alert problems, note the plan, time and request ID and contact your administrator.

Account and security

  • "Account → Profile": details, password and sign-in security.
  • "API keys": give a key only the permissions it needs; it is shown once, so store it safely. If it leaks, "Revoke" it at once and create a new one.
  • "Members & sub-accounts" and "Custom roles": accounts and permissions for others under your account (needs the right permission).
  • "Message subscription", "Messages" and the bell icon: reminders such as a site under heavy attack or a CNAME that must change.
  • "Tickets": submit a ticket; you are notified according to your message subscription when support replies.

Never send a full API key in screenshots or chats.

Plugins

Plugins your administrator provides are confirmed, upgraded and disabled in "Plugin market"; see plugins. "Plugin market" is not in the sidebar yet: add /dashboard/sys/plugin-market to your control-plane address, for example https://console.cdnca.com/dashboard/sys/plugin-market.