Browse all docs

Start here

cdnca entry points and accounts, what to do when a menu is missing, good habits, and how these docs are organised.

cdnca is made of several separate platforms. Each has its own accounts and permissions; signing up with the same e-mail or username does not link them. Before you start, check which platform you need and which account to use.

Entry points and accounts

Entry pointWho uses itWhat it is forCommon mistake
Licence centre (portal)Customers who buy or claim a control-plane licenceView and renew licences, generate the install command, top up, view orders and profileTreating it as your control-plane console
Licensing consolePlatform operatorsCustomers and licences, identity reviews, payment settings, releases, market reviewsSigning in with a customer or control-plane admin account
Control-plane admin consoleYour control-plane administratorNodes, sites, plans, users, DNS, certificates, security, plugins, settingsDoing admin work with a regular user account
Control-plane user consoleRegular users (site owners) on a control planeTheir own sites, certificates, cache, protection, plans and accountOpening admin settings or someone else's site
Seller centreNode suppliers, plugin developersOnboarding, payout accounts, deposit, income and settlement, disputesExpecting to create node offers there

Things that are easy to mix up:

  • The admin console and the user console are two views of the same control plane. Both sign in at /dashboard/login on your control plane; the menu depends on the account.
  • Node offers are created, published and bought in "Node market" on your own control plane. The seller centre only handles onboarding, payouts and settlement.
  • A regular user's "Plugin market" manages plugins already provided to that account. Administrators buy plugins in "Plugin store". They are different pages.

When a menu is missing

A missing menu is not always a permission problem. Check in this order:

  1. You are on the right platform (page title and address).
  2. You are signed in as an administrator or as a regular user (account in the top-right corner).
  3. The service is enabled (some modules need a licence that includes the feature).

If the entry is still missing, send the menu name, your account and the page address to the right administrator: your control-plane administrator for control-plane menus, the platform for licence-centre and market menus. Do not borrow someone else's account.

How these docs are organised

Each page covers what a task is for, who does it, where to start, what to prepare, the steps, how to confirm success and what to do if it fails. Menu paths use "→", for example "Sites → Site list". Menu names are quoted as they appear in the Chinese interface where no English label exists.

Good habits

  1. Read back after saving: return to the list or reopen the details to confirm the change.
  2. When a result is unclear, check before acting again: refresh the details, look at the order or task record, and do not create or pay twice. If the page offers "retry with the same request", use it to continue the original action.
  3. Note what helps locate the problem: page, object, time, order or task number, and the request ID shown on the page.
  4. Protect accounts and data: never put passwords, codes, API keys, DNS keys, private keys, full payment details or ID documents in screenshots, tickets or chats.
  5. Ask the right person: the platform for licences and orders; your control-plane administrator for its resources; your direct supplier for nodes; your administrator or the plugin provider for plugins.

All domains are examples: console.cdnca.com for the control plane and www.cdnca.com for a site. Use your own.