SSL Pending

  • Unknown's avatar

    Hi,

    I understand that WordPress include a SSL certificate, but my site says it is pending and when I click on the Provision Certificate button, I get the following message:- sorry, we weren’t able to provision the certificate. Please verify your DNS configuration and try again

    My site is live with no difficulty in all the pages loading, it simply shows Not secure in the address bar.

    How do I verify my DNS configuration where WordPress provide the SSL certificate?

    The blog I need help with is: (visible only to logged in users)

  • Unknown's avatar

    Hello @peterhorridge! I’ll be happy to help you with this.

    I went ahead and issued an SSL certificate for your domain, so it’s now secure.

    However, to also issue the certificate for the www version of your domain, you’ll need to restore the CNAME records to their default settings. You can follow the steps in this guide to do that:

    https://wordpress.com/support/domains/custom-dns/view-or-restore-default-dns-records/#restore-default-cname-record

    Once that’s done, you can manually request the SSL certificate for the www version by following this guide:

    https://wordpress.com/support/domains/https-ssl/#manually-provision-ssl

    Feel free to go through those steps, and let me know how it goes. I’ll be here ready to help further if you need anything else!

  • Unknown's avatar

    Many thanks for issuing the SSL certificate.

    The CNAME records, as well as the MX & TXT records, were updated this morning as part of dealing with loss of email when I updated the name servers with our domain registrar. If I restore the CNAME record to its default setting, would this cause an issue with my email again?

    I must confess to being confused about the difference between the domain, which you have issued the certificate for, and the www version, which a SSL certificate is still needed.

  • Unknown's avatar

    Thanks for sharing this information, @peterhorridge. In this case, please add the following CNAME record:

    http://www.example.com pointing to example.com

    (Just make sure to replace “example” with your actual domain name.)

    You can follow this guide to add the CNAME record:

    https://wordpress.com/support/domains/custom-dns/add-a-new-dns-record/

    To answer your question, the www version is considered a subdomain, so it needs to be connected correctly via DNS in order for a certificate to be issued for it as well.

    If you still don’t see the SSL certificate after making the update, try clearing your browser’s cache using the steps in this guide:

    https://wordpress.com/support/browser-issues/

    Feel free to follow these steps, and we’re here if you have any questions!

  • Unknown's avatar

    Hi elcristofue, I looked into the change, I was unsure if you were suggesting I add another CNAME record or amend the existing one, I was leaning towards the latter as the former required me to add a subdomain, which there was no mention of in your last reply.

    However, I see today that the site no longer has unsecure noted and now shows HTTPS.

    I am assuming there is now no need to apply any changes, and, if that is the case, many thanks for your help, but if that is not the case, still thank you to date, but what else should I be doing to secure the site?

  • Unknown's avatar

    Hi @peterhorridge,

    I see that the SSL certificate has been issued for the non-www version of your site. However, if someone adds www to your site address—for example, http://www.yourdomain.com—instead of redirecting to the non-www version, the visitor will get an error saying the site cannot be reached. This can reduce traffic to your site.

    You can read more about how WordPress.com handles www redirection here:
    https://wordpress.com/support/www-versus-non-www-domains/

    I understand your concern that restoring the default CNAME might remove your currently published CNAME records. Kindly note that this will not happen. Restoring the default CNAME will only update the required default CNAME for your domain. Your other DNS records will remain intact.

    If you’d prefer not to through the route of restoring the default CNAME, that’s completely fine. You just need to manually add the CNAME record below to enable redirection for the www version of your site:

    Once this CNAME record is published, let us know and we’ll be glad to assist you in issuing the SSL certificate for the www version of your site. This way, visitors who go to the www version will be redirected safely to the non-www version without any error.

    I look forward to your response.

  • Unknown's avatar

    Hi adusman402, Thank you for the explanation.

    I have done the change, hopefully correctly, and look forward to the certificate being issued.

  • Unknown's avatar

    Hi @peterhorridge,

    Thanks for the update. I can confirm that you’ve correctly published the CNAME record for the www redirection. I’ve gone ahead and issued the SSL certificate for the www version of your site.

    Now, if someone visits the www version of your site, they will be redirected to the non-www version without any error.

  • Unknown's avatar

    Many Thanks, adusman402, I have just checked and it is now showing.

  • Unknown's avatar

    I’m glad to hear that everything is looking correctly on your end!

    I’ll be closing this thread for now, but If you run into any other issues or need additional help, since you are on a paid plan, you can contact us directly from your account by following this guide:
     
    https://wordpress.com/support/help-support-options/#how-to-contact-us 

    You can also email us at  help@wordpress.com , and we’ll be happy to continue helping you from there. 🙂

  • The topic ‘SSL Pending’ is closed to new replies.