Legacy Knowledge Base
Published Jun. 30, 2025

Add New Custom Domains and Avoid Downtime while Let's Encrypt certificate Is Generated

Written By

Ricardo Couso

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.

Issue

  • When new custom domains are appended to to the existing list under "customDomains" in the "certs" part of the webserver LCP.json file, a new Let's Encrypt certificate is issued to include them. In the mean time the old domains will appear as having no current certificate.
  • Is it possible to add new custom domains to an existing Let's Encrypt certificate without temporarily affecting the certificate of the existing domains?

Environment

  • Liferay PaaS

Resolution

  • To avoid this temporary lack of certificate for the old domains, add the new domains in a separate customDomains block within the certs array of the LCP.json file. This will generate a new certificate for the new domains, while keeping the existing certificate for the existing domains active, preventing downtime.
    "certs": [
      { "customDomains": ["existing.domain.com", "www.existing.domain.com"] },
      { "customDomains": ["new.domain.com", "www.new.domain.com"] }
    ]
    
  • This approach only applies to certificates generated by Let's Encrypt, not to custom certificates (Custom SSL) added via secret variables key and crt.
Did this article resolve your issue ?

Legacy Knowledge Base