Liferay PaaS: Custom domains are not SSL certified by Liferay
Written By
Solyom Nagy-Györkös
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
- We have domains that are NOT using custom SSL certificates, however, they refuse to use https connection.
Resolution
- The correct methodology to achieve these results is modifying your LCP.json file of your Webserver service like the following:
-
"prd": {
"loadBalancer": {
"targetPort": 80,
"cdn": true,
"certs": [
{
"customDomains": ["custom-domain.with-custom-certificate.example"],
"key": "@ssl-key-secret-multidomain",
"crt": "@ssl-crt-secret-multidomain"
},
{
"customDomains": ["custom-domain.with-default-certificate.example"]
}
]
}
- Proper changes in certificate generation may take a couple of hours.
Did this article resolve your issue ?