Site is insecure after adding a new custom domain into Liferay Cloud
Written By
Matheus Monteiro
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
- After adding a new custom domain, the SSL certificate is no longer working and a website (in which the certificate was working just fine before) is now marked as insecure.
Environment
- Liferay Cloud with no custom SSL
Resolution
- Check if this new custom domain is pointing to the right ingress address. You must check all the custom domains from all the project's environments.
- The certificate in this case is binary: it works either for all of the custom domains or for none of them. If there is a single custom domain pointing to a wrong IP (which is not the environment ingress address), the certificate for all custom domains will be compromised.
- If you are sure that all custom domains points to the right ingress address, please open a support ticket and we will be happy to help you.
Did this article resolve your issue ?