Your new domain is not yet setup. Please allow 48 hours for the setup process to complete- Weebly

[chohakkaifan]

Hi there, I've a Weebly account that I've renewed, and I noticed that this site has an archived Weebly discussion board, so I thought I might as well try asking here. 

I renewed everything on the account (domain, site package, etc.) and, upon attempting to put my site back up, I received the message "Your new domain is not yet set up. Please allow 48 hours for the setup process to complete." I didn't think anything of it at first, but now, after three weeks, I'm still receiving the message whenever I attempt to publish it.  The domain says it is listed as active, and I can't think what else would be causing such a delay.

Website is SketchMeow.com

Does anyone have any ideas?

[rtfulk]

@chohakkaifan  Welcome to the community. I just went to your site and it is active.  Are you saying it's active, but when you try to publish it from the online side you get the message your domain is not set up yet? That means something is broken in the domain connection process. That message is only supposed to appear during initial DNS propagation, which usually completes within a few hours to a max of 48 hours. Here is a few things to try.

If your domain is hosted externally (e.g., GoDaddy, Namecheap), your DNS records must point to Square’s servers.

The A record should be:

199.34.228.164 (for Weebly/Square sites)
And your CNAME record for www should point to:

yourdomain.com
If this isn't set correctly, Square can’t connect to your domain—and that error stays active.

Even if the domain is renewed and active:

You still need to assign it to a published website.

In Square Online:
Go to Website > Domains > Assign Domain to Site and make sure your domain is linked to your current website project.

Sometimes the SSL setup fails silently, especially if the DNS records weren’t correct when the domain was connected.

Fix:

Turn SSL off in the domain settings, wait 5–10 minutes, then turn it back on.
This forces Square to retry generating the certificate.

Visit https://dnschecker.org and enter your domain—check if the A record points to 199.34.228.164

Hopefully one of these solutions will fix the problem.