Skip to main content

Troubleshoot your custom domain

Most custom domain problems come from a handful of causes: an old A record still in place, a root domain that can't take a CNAME…

M
Written by Michael Bollinger

Most custom domain problems come from a handful of causes: an old A record still in place, a root domain that can't take a CNAME, missing certificate records, or nobody clicking Verify after the records were added. Find what you see below, then follow the fix. For the full setup, see Connect your own domain.

Before you start:

  • You make DNS changes yourself at your registrar (the company you bought the domain from). PayHOA support doesn't log in to registrars. Never send your registrar password to anyone, including PayHOA support.

  • Don't know your registrar? Look your domain up with any WHOIS lookup tool. The Registrar line tells you.

  • Your site uses CNAME records only. You never need an A record or an IP address for it.

Quick checks

Before anything else, at your registrar's DNS page check that:

  1. There's no A record on @ (or blank) or on www. Delete any you find, especially one pointing to an address starting 199.34.228. (old Weebly sites).

  2. www is a CNAME pointing to {your-name}.site.payhoa.com. Your exact address is on the Domain tab under Base domain.

  3. Both certificate records from the setup dialog are there: CNAMEs with names starting with an underscore, _xxxx and _xxxx.www.

  4. The root domain either forwards to https://www. your domain (permanent 301, no masking) or has an ALIAS record, if your registrar can't take a CNAME on @.

Then open the Domain tab and click Verify on the Custom domain card.

Where the Custom domain card is. Open Other Tools → Website builder and click the Domain tab. The Custom domain card is there, under Base domain. It isn't under Site settings, and the builder no longer has a General Settings tab. Verify is the only check you can run on your domain from your account. There's no diagnostic button for customers; PayHOA support can run a fuller check of your domain's records and certificate from their side, so if Verify doesn't explain the problem, contact support (see What to send support).

What you see and what to do

What you see

Why

What to do

Pending verification for days

Nothing checks the domain on its own. It stays pending until someone clicks Verify, or the certificate records are missing.

Check the certificate records are in place, then click Verify.

"Validation in progress" or "SSL certificate validation is in progress. This usually takes 30 minutes and can take up to 48 hours. Check back here later and click Verify again."

Your certificate records haven't been picked up yet.

Wait and click Verify again later. If it's still pending after about 3 days, see "SSL certificate cannot be issued" below.

"No certificate yet" or "No SSL certificate found. Please ensure you've added the DNS validation records and wait for certificate issuance."

The certificate records are missing or not live yet.

Add both certificate records from the setup dialog (Edit → Continue to DNS setup shows them), wait, then click Verify.

"Still checking" or "SSL certificate status unknown. The certificate may still be pending validation."

The certificate is probably still being set up.

Try Verify again in a few minutes.

"SSL certificate cannot be issued" or "Your SSL certificate could not be issued and cannot recover (status: …)"

The certificate records weren't found in time (about 3 days), or an A record on that name blocked them. The message names the address that failed.

Delete conflicting A records and check the certificate records. Then save the domain again to get a new certificate (below), replace the old certificate records with the new ones, and click Verify.

"Certificate needs our help" or "SSL certificate was validated but failed to attach to load balancer. Please contact support."

Your records are right. The last step has to be finished on PayHOA's side.

Contact PayHOA support (see "What to send support"). Don't change your records or keep clicking Verify.

"Error" / "DNS verification failed. Please try again." every time you click Verify, even after waiting a minute

The check couldn't finish on PayHOA's side. One cause is that the certificate was issued but your site couldn't be routed to it. The screen shows only this general message.

Wait a few minutes and click Verify again. If it keeps happening, contact support (see "What to send support").

Points elsewhere, "{your domain} is not reaching your PayHOA site.", or "Domain still points elsewhere"

Your certificate is fine, but your domain still sends visitors to another host: an old A record (an old Weebly site, a parked page, Squarespace, Wix, a previous host), or www isn't a CNAME to your PayHOA address.

Delete every A record on @ and www. Make www a CNAME to {your-name}.site.payhoa.com. Forward the root to https://www. your domain once www loads your site.

Your old Weebly site or an old website still shows

An old A record is still in place.

Delete every A record on @ and www, including any to 199.34.228.x. Make sure www is a CNAME to your PayHOA address.

Your registrar won't let you add a CNAME on @

Most registrars don't allow a CNAME on the root domain.

Skip the @ CNAME. Add the www CNAME, then forward the root to https://www. your domain (permanent 301, no masking), or add an ALIAS record on @ if your registrar offers one. See Connect your own domain.

www.yourdomain.com works, yourdomain.com doesn't

Root forwarding (or ALIAS) is missing, or an A record on @ is in the way.

Delete any A record on @, then forward the root to https://www. your domain as a permanent (301) redirect with no masking.

yourdomain.com works, www.yourdomain.com doesn't

The www CNAME is missing, or www points at the root (@).

Make www a CNAME to {your-name}.site.payhoa.com. If your registrar offered to point www at the root when you set up forwarding, undo that.

The browser warns the site isn't secure, for example Your connection is not private, This server could not prove that it is {your domain}, or a certificate that doesn't match your domain even though it hasn't expired

The certificate isn't in place yet, or the domain still reaches another host, so the browser is shown that host's certificate and not yours. An old A record is the usual cause.

Delete every A record on @ and www, and make www a CNAME to {your-name}.site.payhoa.com. Don't add an A record to 199.34.228.72: that address is for old Weebly sites only. Then click Verify and read the result. Don't keep editing the domain; each save starts a new certificate.

The domain shows your registrar's own page (parked, for sale, expired)

The domain has expired or is on hold, or a parked A record is still there.

Renew the domain with your registrar. Delete the parked A record on @.

DNS status went back to Pending verification after Edit

Saving the domain again resets it and requests a new certificate. That's expected.

Check the certificate records still match the ones in the dialog, then click Verify.

"Error" / "DNS verification failed. Please try again." right after you clicked Verify

You can verify once every 30 seconds. A second click inside 30 seconds shows this general message. It doesn't mean your records are wrong.

Wait 30 seconds and click Verify again.

Ask Penny shows on your .site.payhoa.com address but not on your own domain

Penny runs only on the domain saved on the Domain tab, with or without www, and only over https://. She doesn't show on an http:// address, or on a second domain that forwards to your site with masking.

Open your site at https:// plus the domain on the Domain tab. If Penny is still missing, check she's on (The AI chatbot (Penny) on your website), publish your site again, then contact support.

When the status says Points elsewhere

Points elsewhere means the certificate is fine but your root domain (the domain as you typed it, without www) doesn't reach PayHOA. PayHOA accepts either of these: the root points at your PayHOA address, or the root forwards to https://www. your domain and www points at your PayHOA address. If only www works and the root does nothing, the status stays Points elsewhere.

Once a domain is Verified, the Verify button no longer shows, so you can't ask for a new check. PayHOA keeps the result of its last check for up to 6 hours. After you fix your records, wait up to 6 hours, then reload the Domain tab.

Save the domain again

Do this when the certificate can't be issued, or when you've changed your records and the domain still won't verify after a few days.

  1. On the Custom domain card, click Edit. If the domain is verified, read Edit custom domain? and click Continue.

  2. Check the domain and click Continue to DNS setup.

  3. Compare the certificate records in the dialog with the ones at your registrar. If they've changed, delete the old _… records and add the new ones.

  4. Click Verify DNS configuration, or Complete verification later and come back to Verify on the card.

Each save requests a new certificate. The dialog says validation "usually takes 30 minutes and can take up to 48 hours"; a request that still hasn't been validated after about 3 days expires and can't recover, which is when you save the domain again.

Remove the domain and start fresh

If you've tried everything above and the domain is still stuck:

  1. On the Custom domain card, click Remove → Remove domain. Your site stays at your .site.payhoa.com address.

  2. At your registrar, delete the old certificate records (the _… CNAMEs). Keep the www CNAME.

  3. Set the domain up again from the start. See Connect your own domain. You get new certificate records; add those.

  4. Click Verify.

Using a subdomain like hoa.example.com

The setup dialog is written for a root domain. If the domain you're connecting is itself a subdomain (for example hoa.example.com, not example.com), the names it shows are wrong for your registrar:

  • It shows @ and www for the records that point to PayHOA. For a subdomain those names mean example.com and www.example.com, not hoa.example.com.

  • It shortens the two certificate record names to _xxxx and _xxxx.www, leaving out your subdomain.

Contact support before you add any records, so they can give you the exact record names for your subdomain.

What to send support

When you contact PayHOA support about your domain, include:

  • your domain, and the name of your registrar;

  • a screenshot of the Domain tab showing the Custom domain card;

  • the exact message you see (copy and paste it);

  • a screenshot of your DNS records page at the registrar.

Don't send your registrar password or login. Support doesn't need it.

What's next

Did this answer your question?