Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

SSL Certification isn't provided by Let's Encrypt, even though it is set up correctly

Written By

Madeleine Clay

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

  • Let's encrypt isn't providing SSL certification to my custom domain, so I'm seeing a warning that my site isn't secure.
  • I ensured that my custom domain is set up to point toward the correct Ingress Load Balancer IP and that the webserver LCP.json is formatted correctly following the Custom Domain documentation.
  • I see confirmation in the Networks tab in my console that the CDN is active and the SSL certification generated correctly.

Environment

  • Liferay PaaS

Resolution

  • It may be that the ingress load balancer didn't update the certificate, and is instead using the temporary certificate.
  • If this is the case, the certificate can be regenerated by removing and then re-adding the custom domain.
  • This will trigger the certificate regeneration on the ingress.

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?