Getting we could not verify the certificate: reason = expired for website

David Hurley

• February 08, 2024 21:51

It seems that somehow our A record got changed and was no longer pointing to Brizy for the brizy hosted site. I switched the A Record back and now I'm getting "we could not verify the certificate: reason = expired"

This is for https://www.autolube.express

0

• 

  KC George

  • February 09, 2024 07:04

  Hi David,

  On April 12, 2021, your Brizy Cloud Studio subscription was canceled, and as a result, you no longer have an active Brizy Cloud subscription. In order to add SSL to your custom domain, you need to have a Pro plan. (If the A record remained unchanged, the previously added custom domain would have continued to function well)

  To publish your website on a custom domain, you have these options

  1. Buy one of the existing plans at https://www.brizy.io/pricing-cloud
  2. Publish the website to a 3rd Party Free hosting provider via GitHub and and add the custom domain to your website through the provider you have chosen. You can read more about it at https://www.brizy.io/introducing-3rd-party-free-hosting-netlify-render-fast-io-vercel  Depending on the provider you choose, the process for adding custom domain can be different. For instance, you can follow the process outlined at https://docs.netlify.com/domains-https/custom-domains/ for Netlify.
  3. Export the HTML and upload it to a hosting server and add custom domain to the sever. You can read more about it here https://support.brizy.io/hc/en-us/articles/360026945332-Export-HTML

  Server Sync technology has a few limitations. Hence this is not a recommended option.

  

   

  0
• 

  David Hurley

  • February 09, 2024 17:34

  This is a cloud account and has been working fine. This is a grandfathered account. It is launched by custom domain already. You can see inside the account. A record and www is pointed correctly. The issue is on your end. The website has been launched for a long time and there are 10 or 15 other sites also launched the same way experiencing no issues. Please resolve the SSL issue.

  Thank you.

  0
• 

  David Hurley

  • February 09, 2024 21:19

  The client has now had to buy their own account in order for this site to be relaunched again and hosted by Brizy. My account, per the terms of the account agreement, was to have 2 years of cloud hosting. This site was launched within that time and has not been UNLAUNCHED from cloud hosting. Someone on your end disconnected the cloud hosting and now I no longer have access to it. You can see my clients live chat to see that it was working fine, the A record was wrong, and then I fixed it, and experienced the SSL issue. After that it was indeed an error on your end. Someone on your side turned it off and then I was required to upgrade.

  0
• 

  KC George

  • February 10, 2024 07:56
  • Edited

  Hi David,

  After you corrected the wrong A record, you encountered the SSL problem. We had to delete and then re-add the custom domain in order for it to auto-generate the SSL certificate. Since you don't have a current subscription, in your case, your custom domain could not be added again after it was deleted.
  
  As long as nothing changes, other websites that were created with a previous Pro subscription will continue to function. We have to remove your custom domain and add it again to auto-generate SSL whenever the A Record or the CNAME record changes. Our systems are currently configured so that regenerating SSL certificates require an active Pro subscription.

  0

Please sign in to leave a comment.