Domain connection errors
The custom domain wizard checks your address on the server: it asks your provider’s DNS servers directly, then public DNS, then opens the site over HTTPS. If something is wrong, one banner with the main cause and a “What does this mean” link appears under the check rows — it leads to the section of this page with the same code (for example, CNAME_CONFLICT_A).
Every code has a mark: 🛠 needs a fix at the provider, ⛔ cannot continue without a change, ⏳ waiting (nothing to do), ❔ the check failed (not your fault — we retry ourselves). Record values are not given below: the wizard always shows the exact ones for your address and your provider.
How to add a record in a specific panel — instructions by DNS provider; the general order — Custom domain.
Address and connection terms#
HOST_INVALID — not a domain name#
🛠 needs a fix
What it means. What you entered does not look like a site address: an IP address, spaces, invalid characters, an asterisk (*.site.com) or a name that is too long.
What to do. Enter an address like www.example.com or example.com. Pasting a whole link (https://example.com/menu) is fine — the wizard drops the scheme and path itself. Internationalised domains (мойсалон.рф) work too.
HOST_PUBLIC_SUFFIX — a domain zone, not a domain#
🛠 needs a fix
What it means. com, ru, co.uk are zones where domains are registered, not your domain.
What to do. Enter the whole domain: example.com or www.example.com.
HOST_IS_PLATFORM — this is our platform’s address#
🛠 needs a fix
What it means. The location already has an address on the platform domain (like location.cenaly.ge) — it does not need to be connected as a custom domain.
What to do. Enter a domain you own. The address on the platform is changed in the location’s web settings, site address field.
HELP_HOST_LABEL_INVALID — the help portal needs a service subdomain#
🛠 needs a fix
What it means. The help portal is connected only as a subdomain with a clear name — help, kb, docs, support, faq and the like, not the root domain.
What to do. Enter, for example, help.example.com. The wizard lists the allowed names in the message.
LOCATION_BRAND_MISMATCH — the location belongs to another edition of the service#
⛔ cannot continue without a change
What it means. You opened the admin panel of one edition of the service (for example the international one) while the location lives in another (for example the Russian one). The domain is connected where the location’s data lives.
What to do. Open the admin panel of the edition where the location was created and connect the domain there.
BRAND_NOT_CONFIGURED — custom domains are not enabled here yet#
⛔ cannot continue without a change
What it means. Connecting custom domains is not set up for this edition of the service yet — the issue is on our side, not with your domain.
What to do. Write to support — we will let you know when it works.
NOT_ENTITLED — no free domain on your plan#
🛠 needs a fix
What it means. All domains included in the plan are already connected (the limit is per account, not per location).
What to do.
- Add the “Own website” add-on for this location — it gives a domain beyond the plan.
- Or disconnect the domain of another location, or move to a plan with a bigger limit — see Subscription.
HOST_TAKEN_SAME_ACCOUNT — the address is already connected to another of your locations#
🛠 needs a fix
What it means. This address is used by another location or purpose (for example the help portal) of your own account. One address — one connection.
What to do. Disconnect it there (in that location’s web settings) and try again here. Or connect a different subdomain here.
The domain and its DNS servers#
DOMAIN_NXDOMAIN — no such domain#
🛠 needs a fix
What it means. The domain is not registered or there is a typo.
What to do. Check the spelling. If you do not have the domain yet, buy it (“I don’t have a domain yet” in the wizard) and come back.
DOMAIN_NO_NS — the domain has no DNS servers#
⛔ cannot continue without a change
What it means. The domain is registered but not served — most often it was not renewed or no DNS servers are set at the registrar.
What to do. Open your registrar account: renew the domain and check that DNS servers are set for it (usually the registrar’s own).
DOMAIN_PARKED — the domain is parked#
⛔ cannot continue without a change
What it means. The domain’s DNS servers are the registrar’s “parking” servers: expired domains or domains without DNS management look like this.
What to do. At the registrar switch on DNS management for the domain (the registrar’s or hosting’s free DNS) and renew the domain if needed.
DELEGATION_BROKEN — the domain’s DNS servers do not answer for it#
⛔ cannot continue without a change
What it means. The registrar lists DNS servers, but they know nothing about your domain (the zone was not created there or was deleted). The domain’s site and email usually do not work either.
What to do. Check the DNS server list at the registrar: either create the domain’s zone at the provider the servers belong to, or switch back to servers that have the zone.
AUTH_NS_UNREACHABLE — the DNS servers did not answer#
❔ could not check — not your fault
What it means. Your DNS provider’s servers did not answer our check — it may be a brief outage at the provider or in the network.
What to do. Nothing to change — we retry automatically in a minute. If the message stays for hours, check whether your provider has an outage.
DELEGATED_SUBZONE — the subdomain is served separately#
ℹ️ for your information
What it means. Your address lives in a separately delegated subzone: its records are edited not in the main domain’s zone but in that subzone (often at another provider or in another panel).
What to do. Add the records in the zone the wizard named. If you do not know where it is, ask whoever set up the domain.
How to do it in your provider’s panel — the “Where to edit records” section of the provider page.
NS_MISMATCH_PARENT_CHILD — the registrar and the zone list different DNS servers#
🛠 needs a fix
What it means. The registrar gives one set of DNS servers, while the domain’s zone names another. This happens after moving DNS: you may edit records at the old provider and they will have no effect.
What to do. Decide where the zone should live and set exactly those servers at the registrar. Add records at the provider whose servers are set at the registrar.
How to do it in your provider’s panel — the “Where to edit records” section of the provider page.
DNS provider#
PROVIDER_UNKNOWN — DNS provider not recognised#
ℹ️ for your information
What it means. We did not recognise the provider by the domain’s DNS servers. It is not an error — we just do not have a detailed guide for your panel yet.
What to do. Pick the panel manually (“I use another panel”) or follow the general guide: it is the same for all panels, only the field names differ. If the provider is popular, tell us its name and we will add it.
How to do it in your provider’s panel — the “Where to edit records” section of the provider page.
PROVIDER_REGISTRAR_DIFFERS — the domain is bought at one company, DNS is at another#
ℹ️ for your information
What it means. The domain is registered at one company while another serves its records (for example bought at GoDaddy, DNS moved to Cloudflare). Records at the registrar have no effect in this case.
What to do. Add the records at the provider the wizard named as serving DNS.
How to do it in your provider’s panel — the “Where to edit records” section of the provider page.
What the domain already has#
EXISTING_SITE_DETECTED — a site already opens at the address#
🛠 needs a fix
What it means. Another site works at this address now. After the record changes, visitors will reach the new one — the old site stops opening at this address.
What to do.
- If the old site is no longer needed, confirm the replacement in the wizard and continue.
- If it is, connect another subdomain, for example
menu.orshop.(the wizard offers it with a button). - Moving without downtime — If the domain already has a site.
How to do it in your provider’s panel — the “If a site already opens at the address” section of the provider page.
MAIL_DEPENDS_ON_CHANGED_HOST — email depends on this address#
🛠 needs a fix
What it means. The domain’s email uses the name you are connecting (for example the mail server is on the same name, or the domain has no MX and mail is delivered to the root address). Changing the record may stop email.
What to do. Connect another subdomain (www, menu, shop) or reconfigure email first — see Custom domain and email.
How to do it in your provider’s panel — the “Email on the domain” section of the provider page.
Ownership#
OWNERSHIP_REQUIRED — no ownership record#
🛠 needs a fix
What it means. The record proving the domain is yours is not yet found at the provider’s DNS servers. Without it the address is not reserved for your account and the connection does not start.
What to do. Add the ownership record exactly as in the wizard (usually a TXT _cenaly-verify…, for a subdomain sometimes the CNAME with the request code itself). How — the “Ownership record” section of your provider’s page.
How to do it in your provider’s panel — the “Ownership record” section of the provider page.
OWNERSHIP_MISMATCH — the ownership record has another code#
🛠 needs a fix
What it means. The ownership record exists, but its code does not match the current request — most often it is left from a previous attempt (every attempt gets a new code).
What to do. Replace the record value with what the wizard shows now. Delete the old record with the previous code.
How to do it in your provider’s panel — the “Ownership record” section of the provider page.
HOST_TAKEN — the address is reserved by another account#
🛠 needs a fix
What it means. This address is connected (or was recently connected) to another account of the platform. The other account is not shown — this protects your domain too.
What to do. If the domain is yours, add the ownership record from the wizard: a fresh code of your request releases the old reservation. If that does not work, write to support.
How to do it in your provider’s panel — the “Ownership record” section of the provider page.
DNSSEC#
DNSSEC_BOGUS — DNSSEC signature is broken#
⛔ cannot continue without a change
What it means. DNSSEC is enabled for the domain but the signature does not validate. Validating DNS servers (most of the internet) treat the domain as forged and do not open it at all — not only our site.
What to do. At the registrar turn DNSSEC off (remove the DS record) or ask the registrar’s support to fix it. It usually happens after moving DNS to another provider.
DNSSEC_INDETERMINATE — could not check DNSSEC#
❔ could not check — not your fault
What it means. We could not reliably check the DNSSEC signature chain.
What to do. Nothing to do — we retry automatically.
Root domain#
APEX_NEEDS_ALIAS — the root needs an ALIAS/ANAME record#
ℹ️ for your information
What it means. You are connecting the root of the domain (example.com without a subdomain). The DNS standard forbids CNAME on the root, so an ALIAS, ANAME or CNAME-flattening record is needed — your provider has one.
What to do. Create the record type the wizard named, plus the ownership record (and the certificate record if the wizard shows it). How — the “Root domain” section of the provider page.
How to do it in your provider’s panel — the “Root domain” section of the provider page.
APEX_ALIAS_UNSUPPORTED — the provider cannot point the root domain#
🛠 needs a fix
What it means. Your provider has no ALIAS/ANAME record, and CNAME on the root is forbidden by the standard. example.com itself cannot be pointed to the site in this panel.
What to do.
- Connect
www.example.com(the wizard offers it with a button) — an ordinary subdomain with one record. - At the registrar set up forwarding
example.com→www.example.com. - Details and other options — Root domain and www.
How to do it in your provider’s panel — the “Root domain” section of the provider page.
APEX_ALIAS_CAPABILITY_UNKNOWN — unknown whether the provider supports ALIAS#
ℹ️ for your information
What it means. We do not know for sure whether your provider has an ALIAS/ANAME record for the root of the domain.
What to do. Open “add record”: if the type list has ALIAS or ANAME, connect the root. If not, connect www and set up forwarding of the root, see Root domain and www.
How to do it in your provider’s panel — the “Root domain” section of the provider page.
Site record (CNAME / ALIAS)#
TRAFFIC_RECORD_MISSING — no site record#
🛠 needs a fix
What it means. The record that brings visitors to the site (CNAME for a subdomain, ALIAS for the root) is not found at the provider’s DNS servers. Waiting will not help: the check asks the provider’s servers directly, there is nothing to “spread”.
What to do.
- Check that the record is saved (at RU-CENTER — “Upload zone” pressed).
- Check that you edit records at the provider the wizard named, and in the right domain’s zone.
- Check the record name:
www, notwww.example.com, if the panel appends the domain itself.
How to do it in your provider’s panel — the “Subdomain” section of the provider page.
TRAFFIC_TARGET_MISMATCH — the record points elsewhere#
🛠 needs a fix
What it means. The site record exists, but its value is not our address: a link to the old hosting, a typo or a value from a previous attempt.
What to do. Open the record and replace the value with what the wizard shows (via the “Copy” button). If there are several records with this name, keep one.
How to do it in your provider’s panel — the “Subdomain” section of the provider page.
APEX_POINTS_ELSEWHERE — the root domain points to the old hosting#
🛠 needs a fix
What it means. The root of the domain answers with IP addresses that are not ours — most likely the old hosting’s A records.
What to do. Delete the old A/AAAA records on the root (@) and create the ALIAS/ANAME (or flattened CNAME) record from the wizard. Leave MX/TXT email records alone.
How to do it in your provider’s panel — the “Root domain” section of the provider page.
FLATTENED_TARGET_UNVERIFIED — the root record is not visible as ALIAS#
⏳ waiting, nothing to do
What it means. ALIAS/ANAME/flattening records look like ordinary IP addresses from outside, so DNS cannot tell where they lead. This is normal.
What to do. Nothing to do: the next checks — the certificate and opening the site — confirm it.
How to do it in your provider’s panel — the “Root domain” section of the provider page.
CNAME_CONFLICT_A — another record next to the CNAME on the same name#
🛠 needs a fix
What it means. Besides the CNAME, the name you are connecting has an A, AAAA or TXT record. By the standard a CNAME cannot coexist with other records on the same name: panels either refuse to save it or answer with one record or the other.
What to do. Delete the conflicting record on THIS name (the wizard names its type and value). Leave records of other names — root, mail, MX — alone.
How to do it in your provider’s panel — the “Subdomain” section of the provider page.
AAAA_STALE — an old AAAA record is left#
🛠 needs a fix
What it means. The name still has an AAAA record (IPv6 address) of the old hosting. Visitors on IPv6 — a sizeable share of mobile networks — will reach the old site.
What to do. Delete the AAAA record on this name.
How to do it in your provider’s panel — the “Subdomain” section of the provider page.
RECORD_NAME_DOUBLED — the domain appears twice in the record name#
🛠 needs a fix
What it means. The record was created as www.example.com.example.com: you entered the full name and the panel appended the domain again.
What to do. Delete this record and create it again with only the left part in the name field — www (or the full name with a dot at the end www.example.com. if the panel requires it).
How to do it in your provider’s panel — the “Subdomain” section of the provider page.
RECORD_VALUE_RELATIVE — your domain got appended to the value#
🛠 needs a fix
What it means. The record value was saved without a dot at the end and the panel appended your domain to it: you got address.from.wizard.example.com.
What to do. Change the value to the address from the wizard with a dot at the end.
How to do it in your provider’s panel — the “Subdomain” section of the provider page.
WILDCARD_SHADOW — a wildcard record answers#
🛠 needs a fix
What it means. The name has no record of its own — a * record (for all subdomains at once) answers instead, usually leading to the old hosting.
What to do. Create a separate record for the name from the wizard — it takes priority over the wildcard. Deleting * itself is not required.
How to do it in your provider’s panel — the “Subdomain” section of the provider page.
CNAME_LOOP — records point to each other in a loop#
🛠 needs a fix
What it means. The CNAME chain loops: a record points to a name that points back to it.
What to do. Delete the extra record in the chain (the wizard shows the chain) and point the name straight to the address from the wizard.
How to do it in your provider’s panel — the “Subdomain” section of the provider page.
CNAME_CHAIN_TOO_LONG — the chain of hops is too long#
🛠 needs a fix
What it means. The record reaches its target through too many intermediate CNAMEs — some DNS servers will not follow such a chain to the end.
What to do. Point the record straight to the address from the wizard, without intermediate names.
How to do it in your provider’s panel — the “Subdomain” section of the provider page.
CLOUDFLARE_PROXIED — the Cloudflare proxy seems to be on#
🛠 needs a fix
What it means. Judging by the answers, the record goes through the Cloudflare proxy (orange cloud). It is detected from several signs, hence “seems”. Ownership checks and certificate issuance do not pass through the proxy.
What to do. In Cloudflare click the cloud of this record so it turns grey — Proxy status “DNS only”. The same for the ownership and certificate records. See Cloudflare → proxy.
How to do it in your provider’s panel — the “Proxy” section of the provider page.
Certificate record#
VALIDATION_RECORD_MISSING — no certificate record#
🛠 needs a fix
What it means. Issuing the certificate needs one more record (_acme-challenge… or _cf-challenge…) — the provider does not have it yet.
What to do. Add it exactly as in the wizard. How — the “Certificate record” section of your provider’s page.
How to do it in your provider’s panel — the “Certificate record” section of the provider page.
VALIDATION_RECORD_MISMATCH — the certificate record has a different value#
🛠 needs a fix
What it means. The certificate record exists, but the value is wrong — often it is left from a previous attempt.
What to do. Replace the value with the current one from the wizard.
How to do it in your provider’s panel — the “Certificate record” section of the provider page.
ACME_TXT_CONFLICT — _acme-challenge has records of a previous service#
🛠 needs a fix
What it means. Besides our record, the name _acme-challenge has a TXT of another service (a previous hosting with Let’s Encrypt). Because of it our CNAME does not work and the certificate is not issued.
What to do. Delete everything on this name except the record from the wizard.
How to do it in your provider’s panel — the “Certificate record” section of the provider page.
VALIDATION_CNAME_FLATTENED — the certificate record is “flattened” by the provider#
🛠 needs a fix
What it means. The provider answers the validation CNAME with addresses instead of the name (proxy or flattening mode), so the certificate authority cannot see it.
What to do. Switch the proxy off for this record (DNS only) and turn off “Flatten all CNAMEs” if it is enabled in the zone settings.
How to do it in your provider’s panel — the “Proxy” section of the provider page.
Certificate permission (CAA)#
CAA_BLOCKS_ISSUER — CAA records forbid our certificate authority#
🛠 needs a fix
What it means. The domain has CAA records — a list of authorities allowed to issue certificates. Ours (Amazon or Let’s Encrypt — the wizard names which) is not on it, so the certificate will not be issued.
What to do. Add one more CAA record on the name the wizard gave: flag 0, tag issue, value — the authority from the wizard (for example amazon.com or letsencrypt.org). Do not delete the existing CAA — your other services need them.
CAA_POLICY_UNSUPPORTED — unusual CAA record#
🛠 needs a fix
What it means. A CAA record restricts the validation method or the certificate authority account (validationmethods, accounturi) so that our issuance will not pass.
What to do. Remove the restriction or add a separate CAA record for our authority without it. If unsure, ask whoever set up the domain.
CAA_LOOKUP_FAILED — could not read CAA records#
❔ could not check — not your fault
What it means. We could not get the CAA records. It does not mean “no restrictions” — the check just did not finish.
What to do. Nothing to do — we retry automatically.
Record propagation#
PROPAGATING — all correct, records are spreading#
⏳ waiting, nothing to do
What it means. Your provider’s DNS servers have the correct records ✓. The rest of the internet learns about them gradually — caches keep the old answer for as long as the record’s TTL was. The wizard shows an approximate time.
What to do. Nothing to do. You can close the window — the connection completes on its own and we will write when the site works.
How to do it in your provider’s panel — the “How long to wait” section of the provider page.
NS_INCONSISTENT — the provider’s servers answer differently#
⏳ waiting, nothing to do
What it means. Some of your provider’s DNS servers already see the new record, some do not yet. The provider is updating its servers.
What to do. Wait — this usually settles within an hour. At RU-CENTER check that “Upload zone” was pressed.
How to do it in your provider’s panel — the “How long to wait” section of the provider page.
RESOLVER_UNAVAILABLE — a public DNS did not answer#
❔ could not check — not your fault
What it means. One of the public DNS servers we use to check propagation did not answer — the sample is incomplete.
What to do. Nothing to do — we retry automatically.
Certificate and preparation on our side#
CLOUD_RESOURCE_MISSING — preparing the connection on our side#
⏳ waiting, nothing to do
What it means. The delivery-network resource for your address is still being created.
What to do. Nothing to do — the server completes it.
CLOUD_OWNERSHIP_PENDING — waiting for the record to become visible#
⏳ waiting, nothing to do
What it means. The delivery network does not yet see that your address points to it. As soon as the record is visible, we issue the certificate.
What to do. If you have waited more than half an hour, check the site record using your provider’s guide; the wizard shows the exact cause in a row above.
How to do it in your provider’s panel — the “Subdomain” section of the provider page.
CERT_PENDING — issuing the certificate#
⏳ waiting, nothing to do
What it means. Records are visible ✓, the certificate authority is checking the domain and issuing the certificate — usually 1–10 minutes.
What to do. Nothing to do.
How to do it in your provider’s panel — the “Certificate record” section of the provider page.
CERT_ATTACH_PENDING — the certificate is issued, attaching#
⏳ waiting, nothing to do
What it means. The certificate is issued ✓ and is being attached to the delivery network.
What to do. Nothing to do.
CERT_FAILED — the certificate was not issued#
🛠 needs a fix
What it means. The certificate authority refused to issue. Usual causes: the certificate record is missing or wrong, a CAA record blocks it, the proxy is on.
What to do.
- Check the records in the wizard — the check rows show which one is wrong.
- Press “Retry connection” — the server issues the certificate again.
How to do it in your provider’s panel — the “Certificate record” section of the provider page.
CERT_TIMED_OUT — issuance waited for records too long#
⏳ waiting, nothing to do
What it means. The records did not appear for a long time and the certificate authority’s waiting period expired. The server has already started issuing again.
What to do. Nothing to do if the records are in place. If not, add them as the wizard shows.
CERT_EXPIRING — the certificate expires soon and did not renew#
🛠 needs a fix
What it means. The certificate renews automatically, but this time it failed — usually because the certificate record was deleted or the domain records changed.
What to do. Restore the records the wizard shows (especially _acme-challenge / _cf-challenge and the site record). Renewal then passes by itself.
How to do it in your provider’s panel — the “Certificate record” section of the provider page.
EDGE_DEPLOYING — rolling out to the servers#
⏳ waiting, nothing to do
What it means. The certificate is issued ✓, settings are spreading across the delivery network servers — up to 15 minutes. Meanwhile the browser may show a certificate warning.
What to do. Nothing to do.
PROVISIONING_FAILED — a failure on our side#
⛔ cannot continue without a change
What it means. The cloud refused to create or change the resource for your address. Your provider’s records are not the cause.
What to do. Press “Retry connection”. If it repeats, write to support with the domain and the code.
Secure connection#
TLS_NAME_MISMATCH — the server shows a certificate for another name#
⏳ waiting, nothing to do
What it means. Your address still serves a certificate for another name — the new settings have not reached all servers yet, or the record still leads to the old hosting.
What to do. Usually it clears within minutes. If it lasts more than an hour, check the site record in the wizard.
TLS_CHAIN_INVALID — someone else’s server serves the secure connection#
🛠 needs a fix
What it means. The certificate at your address was not issued by us — traffic goes through someone else’s server, most often a proxy (Cloudflare etc.).
What to do. Switch the proxy off for the record (DNS only) and check that the record leads to the address from the wizard.
How to do it in your provider’s panel — the “Proxy” section of the provider page.
TLS_EXPIRED — the certificate has expired#
🛠 needs a fix
What it means. The address serves an expired certificate: renewal failed (often because the certificate record was deleted) or the record leads to an old server.
What to do. Restore the records from the wizard; renewal and rollout then pass by themselves.
HTTPS_UNREACHABLE — the site does not open over HTTPS yet#
⏳ waiting, nothing to do
What it means. HTTPS does not answer at your address yet (we check IPv4 and IPv6 separately). Most often these are the last minutes of the rollout.
What to do. Wait a few minutes. If an hour passes, check whether the name has an old AAAA record (see AAAA_STALE).
HTTP_UNEXPECTED_STATUS — the site answers with an error#
⛔ cannot continue without a change
What it means. The site at your address answers with an unexpected code (for example 403 or 502).
What to do. Write to support — we will look into it on our side.
Does your site open#
SITE_NOT_OURS — someone else’s site opens#
🛠 needs a fix
What it means. The address opens a site that is not ours — the record still leads to the old hosting (or one of several addresses does).
What to do. Check the site records at the provider: delete old A/AAAA/CNAME on this name, keep only the record from the wizard.
How to do it in your provider’s panel — the “If a site already opens at the address” section of the provider page.
SITE_WRONG_LOCATION — another location opens#
⛔ cannot continue without a change
What it means. The address opens our site, but of another location. This is a routing error on our side.
What to do. We have already been notified; write to support if the message stays longer than 15 minutes.
SITE_BRAND_MISMATCH — a site of another edition opens#
⛔ cannot continue without a change
What it means. The address opens the location under another brand of the service — a routing error on our side.
What to do. Write to support.
SITE_MAPPING_MISSING — linking the address to the location#
⏳ waiting, nothing to do
What it means. The “address → your location” route is published right before activation.
What to do. Nothing to do — a minute or two.
BOOTSTRAP_FAILED — the site does not start at this address#
⛔ cannot continue without a change
What it means. The page opens, but the site application did not load at this address.
What to do. Write to support — we will look into it on our side.
Second address and forwarding#
ALIAS_NOT_READY — the second address is not ready yet#
⏳ waiting, nothing to do
What it means. The second address of the www ↔ root pair (the one forwarding to the main one) is still being set up.
What to do. Nothing to do if its records are added as the wizard shows.
How to do it in your provider’s panel — the “Root domain” section of the provider page.
REDIRECT_LOOP — the forwarding loops#
⛔ cannot continue without a change
What it means. www forwards to the root and the root back to www (usually one forwarding at the registrar, the other on our side).
What to do. Keep one forwarding: to the main address connected in the wizard. Delete the extra one at the registrar.
REDIRECT_TARGET_MISMATCH — the forwarding goes elsewhere#
🛠 needs a fix
What it means. The forwarding from the second address does not lead to the connected main address.
What to do. At the registrar change the forwarding target to the main address connected in the wizard.
How to do it in your provider’s panel — the “Root domain” section of the provider page.
The check itself#
RATE_LIMITED — too often#
⏳ waiting, nothing to do
What it means. There were too many checks in a row.
What to do. Wait — the wizard retries itself after the shown time.
DIAGNOSTICS_UNAVAILABLE — the check is unavailable now#
❔ could not check — not your fault
What it means. Our check did not finish. It is not your fault and does not mean anything is wrong with the domain; the last successful result is shown.
What to do. Do not change the records — we retry automatically.
CHECK_TIMEOUT — one of the checks timed out#
❔ could not check — not your fault
What it means. A single check (the wizard names which) took too long and we stopped it.
What to do. Nothing to do — we retry.
Disconnecting and request lifetime#
DANGLING_TRAFFIC_RECORD — after disconnecting the record still points to us#
🛠 needs a fix
What it means. The domain is disconnected, but the site record at the provider still points to us. While it exists, the address stays reserved for your account — so nobody else can connect your domain to their site.
What to do. Delete the record at the provider (the wizard names it) and press “Check removal”. If you plan to connect the domain again, you may keep it.
How to do it in your provider’s panel — the “How to disconnect” section of the provider page.
CLEANUP_PENDING — finishing the disconnection#
⏳ waiting, nothing to do
What it means. The disconnection is still removing settings on our side.
What to do. Nothing to do — a few minutes.
CONNECTION_EXPIRED — the request expired#
🛠 needs a fix
What it means. The records never appeared within the request’s lifetime, so we removed the prepared resources.
What to do. Start connecting again — the wizard issues new values (delete old records with the previous code).
If nothing helped#
Press “Check now” in the wizard: after a change at the provider the check runs again, an old result is not cached for more than 20 seconds.
Write to support from the admin panel and attach: the domain, the code from the wizard banner (for example TRAFFIC_TARGET_MISMATCH), the name of the DNS provider and a screenshot of the records in its panel. The support code from the admin panel address bar is added automatically.