SSL certificate is being configured. Check back later.

[Veganbod]

Hi 

"SSL certificate is being configured. Check back later" I've had this message displayed for a couple of days now in relation to my site www.olivertan.com. Help is much appreciated. Thanks.

[PaulMathews]

@Veganbod Did you re-publish your site?

[Veganbod]

Hi, Yes, I did, thank you. I also did it again after I read your message. The enable SSL option reappeared so I tried that again. I'm still getting the

"SSL certificate is being configured. Check back later" message, but maybe trying it again may help. We shall see. Thanks again.

[PaulMathews]

@Veganbod To enable SSL on a Weebly site, after you click the enable button, you'll see the notice indicating the IP address that must be used in your DNS as part of the enablement. If your domain is registered by a third-party, e.g., Godaddy, you have to log in to your registrar account and update the relevant DNS A records (that point the domain to your Weebly site) with the new IP address. In my experience, it typically takes 3-5 hours to enable SSL. Periodically, you just return to your site settings and check to see the status of the SSL enablement. If it takes substantially longer than this, you may want to directly contact your registrar for assistance with the IP addresses.

Weebly support article: https://www.weebly.com/app/help/us/en/topics/configure-ssl-for-a-site

[Veganbod]

Thank you for your helpful advice and link.

After I clicked the SSL enable button on Weebly, I did not receive a notice indicating the IP address for updating the DNS record. Does that mean that the DNS record is correct? 

The DNS settings are as follows:-

A

@

199.34.228.71

A

*

199.34.228.71

Thanks again.

[PaulMathews]

@Veganbod Take a look at the SSL configuration article, scroll down to the bottom and you'll see a screenshot of the notification dialog you see when you click the Enable button. In that dialog will be the IP address for the domain where the SSL certficate is to be installed. It's possible that you won't see this if the originally provided IP address is the one where the installation will occur. In that case, the enablement should happen without the need for an IP update. Just check that in addition to the records named "*" and "@", you also updated the record named "www" if it exists.

[Veganbod]

Hi Paul,

Thanks for taking the time to respond.

I have a couple of sites with domains registered with Godaddy and hosted by Weebly. I was looking at the DNS information of each and noticed that one had…

CNAME

www

@

and another had…

A

www

199.34.228.71

Should I be using one over the other?

I read an article on the Weekly Support Page “Use a GoDaddy Domain with Your Site" (https://www.weebly.com/app/help/us/en/topics/use-a-godaddy-domain-with-your-site)  stating the following:- 

“Back on the Records page, locate the CNAME for www and make sure it points to @ as shown below. If it doesn't, just edit it and change it so the record says @.”

Thanks.

[PaulMathews]

@Veganbod Out of curiosity, for the domain that is not updating to SSL, which record type is named "www" (A or CNAME?).

[Veganbod]

Hi Paul,

It's currently CNAME. 

I don't recall, but it may have been A record at one time. 

[Adam7 · Accepted solution]

I think the renewal of the certificate was stuck for some reason, @Veganbod. I started it again and it completed successfully this time. Sometimes this can happen if there happens to be some kind of DNS issue that times up with when we try renewing the certificate.

[Veganbod]

Thank you Adam! That's great! 

[ChrisCartwright]

I am experiencing the very same problem with the SSL certificate not being configured in a timely manner.

www.chriscartwrightcomms.com

I continue to get the message in settings : SSL certificate is being configured. Check back later. 

This is extremely frustrating as I have launched my website today to the business community and there has been publicity indicating our new website url... it looks very unprofessional when potential clients go to my site to see it is unsecure!

I have sent email messages to Weebly Support about this issue but I am not getting any response, and I am losing potential business as a result.

This SSL issue taking forever to be configured seems to be a recurring problem and I don't understand why Weebly/Square do not fix it?

Please can anyone help - thank you

[Adam7]

Hi @ChrisCartwright.

It looks like something got hung up when issuing the certificate. I restarted the process and it successfully issued an SSL certificate for your site.

[ChrisCartwright]

Adam - I can't thank you enough for helping to sort this out - really appreciate your prompt attention to my predicament. BTW do you know why Weebly/Square take such a long time to configure SSL certificates... my web developer says it seems to happen with every site he has built/published on Weebly?

Cheers!

[Adam7]

You're welcome!

That's a really good question, although it should be happening within a few minutes at most. I wonder if the developer you talked to enables SSL shortly after updating the DNS of a custom domain used with the site. If the DNS changes hadn't fully propagated it would cause it to pause until they do.

[MarcAPA]

Hi Adam,

We have the very same issue with our webiste www.ap-advisers.com 

In the SSL section it says 'SSL certificate is being configured. Check back later.' since several hours.

Would be very grateful if you could check and help to fix this.

Kind Regards,

Marc

[Bernadette3]

Hi @MarcAPA It looks like you are logged into a contributor account. Can you please confirm the site url, and let us know if the site is published? 

[MarcAPA]

Hi Bernadette,

The site url is www.ap-advisers.com 

I have unpublished it as it showed as not secure. Do I need to publish it in order for you to look into it?

Kind Regards,

Marc

[MarcAPA]

I have published it again now but still seeing the same message.  "SSL certificate is being configured. Check back later."

[Bernadette3]

Sometimes the SSL can take up to 24 hours to configure. Can you leave the site published until tomorrow? Everything looks correct on the backend, and may just be taking a little longer than usual. 

[MarcAPA]

Thanks for your help Bernadette. Just checked again and it still says configuring. Nearly 48hours have past now since I initially disabled and enabled the SSL. Is there anything else we can do?