ÃÛ¶¹ÊÓƵ

Transcript

This is Russell with ÃÛ¶¹ÊÓƵ, how to resolve an expired SSL certificate on the integration environment on ÃÛ¶¹ÊÓƵ Commerce Cloud. This tutorial covers when you visit the LumaBase website, in particular, one of the integration or your other dev environments. For our dedicated staging, if one exists or production or another staging environment, there’s another process that maintains these SSL certificates. This is only for integration and other dev environments.

You’ll notice that I’ll be using the out-of-the-box Luma Storefront and just not pertain to any site using PWA Studio, Edge Delivery Services or other headless implementations. In this example, you can see some missing and broken images and the browser also shows problem with HTTPS. This is a sign that the certificate is expired. You can see that I’m looking up the URL for the image and I’m gonna put that in the browser and I’m gonna hit enter and I’ll get a message that the site is not secure. So I’m highlighting here that the URL shows that it is not secure, even though I am on HTTPS and if you look at the certificate, it expired on October 1st, which is a while ago and this is indeed while the browser’s complaining. To fix it, all you need to do is do a full deployment, not a redeploy. By this, I mean edit at least one file, commit it and push it to your cloud environment and you’ll see here I’m highlighting there’s a step in the process that provisions a new certificate if needed. Once the deployment is complete, the site looks fine, there’s no errors, there’s no warnings about the site being insecure, HTTPS is valid and the shirt shows that it’s available and current.

There you go. You have successfully reissued the SSL certificate and your project can be used again without those annoying issues and warnings.

I hope this helps you understand how to fix an expired SSL certificate and please continue to use Experience League to learn more about ÃÛ¶¹ÊÓƵ Commerce and the other ÃÛ¶¹ÊÓƵ products.