My domain does not open — what do I do?
"It doesn't open" has four distinct causes, and the order of the diagnosis matters: there is no point touching the DNS if the real problem is that the funnel was never published.
Before you start
- Role: Owner or Admin to change domains.
- Have access to the DNS panel at the provider where the domain is registered.
1. Check the status in the platform
Open Domains and look at the status:
Also open the domain's details with the pencil on its row. If the screen shows the Connect the domain in 3 steps card (or Finish the migration in 3 steps, or All set! when the domain is connected), the domain is on the new version; if it shows none of them, it is on the previous version. The records to check in step 3 are different for each.
2. Give propagation time
Propagation can take up to 48 hours. During that window the behaviour is inconsistent by nature: it works on one network and not another, it opens on the phone and not on the computer. That is expected.
Do not redo the configuration while you wait — every change restarts the clock.
On the new version, click Recheck once the record is in place. If something is still missing, the Not connected yet notification says what it is. The platform keeps checking for about an hour; if it does not find the records in that time, the domain goes back to Disconnected and the footer of the steps card says the automatic check ended without finding the records. Nothing is deleted: check the records and click Recheck — the check starts again for another hour.
3. Check the records at the provider
Review the records in the panel of the provider where the domain is registered.
New version: screen with the 3 steps
Each step on the card shows a badge: Done, In progress, Your action or Waiting. The records to create, with the copy buttons, show inside the pending step marked Your action. Compare your provider with those records:
- Does the domain's CNAME point to
domains.clickmax.space? Without it, the domain stays in Connecting: the CNAME is what confirms the domain is yours and unlocks the security certificate. - Did the provider complete the name on its own? Some append the domain to the Name, so
www.mystore.combecomeswww.mystore.com.mystore.com. In that case, type only what comes before the domain, for examplewww. - Is there an old conflicting record for the same name, such as an old
Arecord? Delete it: a CNAME cannot live alongside other records on the same name.
If the domain came from the previous version through the migration, steps 1 and 2 ask for TXT records and the CNAME is in step 3. Also check:
- Do both TXT records exist, with the name and value copied from the screen? Without the
_cf-custom-hostnameTXT, the domain is not confirmed. Without the_acme-challengeTXT, the certificate does not activate. - The certificate does not activate even with the TXT in place? The value of the
_acme-challengeTXT can change after the domain is confirmed, and the screen warns about it under the record. Compare the value on screen with the one at your provider and, if it changed, update the record. - With step 2 (certificate) already Done, is the domain still in Securing? If step 3 is not Done yet, the CNAME still has to be switched to
domains.clickmax.space— the Missing: CNAME pointing to Clickmax notification confirms it. If all three steps are done, wait a few minutes: that is the confirmation that the site answers. - Did you switch the CNAME before the certificate step showed Done? The site has no HTTPS until the certificate is issued. Check both TXT records and click Recheck until the step shows Done — see how to migrate the domain to the new version.
Previous version: screen without the 3 steps
Once the 48 hours have passed, review the record:
- Is the type CNAME?
- Is the host exactly the subdomain you registered (for example
www)? - Is the target correct (
entri-domains.clickmax.space), with no stray space or trailing slash? A domain that came from V2 often still has the old target,entri-domains.clickmax.io— replace it with the new one. - Is there an old conflicting record for the same host? This is the most common finding — an old
Arecord keeps answering and wins over the new CNAME.
4. Check for a block at the provider
Some providers block the domain over incomplete registration details, an unpaid invoice or suspected abuse — and in that case no DNS configuration will fix it. See what to do if the domain is blocked (Portuguese).
5. If the domain is Connected and still does not open
If you are migrating the domain to the new version, check the CNAME first: during the migration the status stays Connected, and switching the CNAME before the certificate step shows Done leaves the site without HTTPS until the certificate is issued. Go back to step 3.
Otherwise, the domain is not the problem:
- Is the domain linked to a project?
- Is the funnel published? Saving does not publish.
- Is the funnel disabled? Visitors reaching a disabled funnel see an error page or get redirected.
- Are you looking at browser cache? Test in a private window.
Related
- Domains
- Connect a domain you already own
- Publish with your own domain
- Migrate the domain to the new version
If it didn't work
- Everything looks right and it is still down: check the error codes reference (Portuguese).
- The domain works without
wwwbut not withwww(or the other way round): the record for the other host is missing.