GoHighLevel Custom Domain Not Working? DNS, SSL and Cloudflare Fixes
You connected your domain to a GoHighLevel funnel or website, and the page still shows an error, a security warning or the wrong site. The good news is that domain problems fall into a small number of patterns, and almost all of them are DNS record mistakes you can fix yourself.
Disclosure: some links on this page are affiliate links. If you start a GoHighLevel trial through them we may earn a commission, at no extra cost to you. We only recommend what we use to build for clients.
Know What Should Be True When It Works
A working setup has three parts: the domain or subdomain points to the address HighLevel gives you, there are no conflicting records on that same name, and an SSL certificate has been issued so the page loads over https. Always copy the exact record values shown inside your own domain settings, because they can differ by account and change over time.
1. You Used the Wrong Record Type
A subdomain such as go.yourbusiness.com normally uses a CNAME record. A root domain such as yourbusiness.com usually needs an A record instead, because many DNS providers do not allow a CNAME at the root. If you added the wrong type, delete it and add the correct one using the values shown in HighLevel.
2. Conflicting Records on the Same Name
Having both an A record and a CNAME on the same hostname is a classic cause of failed connections and certificates that never issue. Open your DNS provider, filter by the hostname and remove duplicates so only the one record you need remains.
3. Cloudflare Proxy Is On
If your DNS is on Cloudflare, a proxied record (orange cloud) can get in the way while the certificate is being issued. Switch the record to DNS only (grey cloud) during setup, wait for the connection to verify, then decide whether you want proxying back on after the site is live.
4. DNS Has Not Propagated Yet
Changes are not always instant. Use a public DNS lookup tool to confirm the record is visible, and avoid judging by refreshing your own browser, because local caches show stale results. Test in a private window or on mobile data instead.
5. The Certificate Is Still Being Issued
A 'connection is not private' warning shortly after setup usually means the certificate has not been issued yet. Once DNS points correctly it is normally created automatically, which can take a while. If it is still failing after several hours, re-check steps 1 to 3 rather than waiting longer.
6. The Domain Is Connected to the Wrong Asset
Adding the domain is only half the job. You must also attach it to the specific funnel step, website or page that should load. If you see a blank or default page, open the funnel or website settings and confirm the domain and the path are selected.
A Short Checklist
- Copy the exact record values from your HighLevel domain settings
- Use CNAME for subdomains and the shown record for root domains
- Delete any duplicate or conflicting records on that name
- Set Cloudflare records to DNS only while connecting
- Test in a private window, not your normal browser
- Attach the domain to the right funnel or website
Why This Matters for Revenue
A domain that fails or shows a security warning kills conversions before anyone sees your offer. If you run paid traffic, test the live URL on a phone before turning ads on. Our funnel setup guide walks through the full launch checklist, and you can practise the whole flow on the 30-day free trial before touching a client domain.
Where to Go From Here
If DNS is not your thing, we handle domains, funnels and tracking as part of our done-for-you setup, or you can book a free call and we will point you in the right direction. Related reading: white label domains and branding.
Frequently Asked Questions
Why does my GoHighLevel domain say connection is not private?
The SSL certificate has usually not been issued yet. Confirm your DNS record is correct and not duplicated, then give it time. If it persists, check for a Cloudflare proxy or conflicting records.
Should I use a CNAME or an A record?
Use a CNAME for subdomains and an A record for a root domain unless your HighLevel settings tell you otherwise. Always copy the values displayed in your own account.
Does Cloudflare work with GoHighLevel?
Yes, but the proxy can interfere while the certificate is issued. Many people set the record to DNS only during setup and adjust it afterward.
How long does a domain take to connect?
Often minutes, sometimes a few hours depending on your DNS provider and caching. If nothing changes after several hours, recheck the record type and look for duplicates.
Related Guides
Ready to Build This Inside Your Own Account?
We help agencies set up, automate, and scale their GoHighLevel accounts, without the trial and error. Whether you need the full build done for you or a specialist placed directly on your team, we can help.