Note: please note that Liferay has renamed its Liferay Experience
Could offerings to Liferay SaaS (formerly LXC) and
Liferay PaaS (formerly LXC-SM).
Issue
- After modifying the webserver service to add new custom domains, the server doesn't start.
- The changes were added to the LCP.json file of the webserver service.
- One of the new custom domains is a wildcard with a format like this one
*.wrongdomain.com. - The fail is the following:
Deployment interrupted: {"message":"Bad Request","status":400,"errors":[{"reason":"certificateDoesNotCoverDomain","context":{"message":"The SSL certificate does not cover domain .wrongdomain.com","domain":".wrongdomain.com"}}],"deploymentUid":"aweauvjdsrdasdfasdfasdf"}
Environment
- Liferay PaaS
Resolution
- The wildcard value produces the error. This kind of wildcard isn't valid as a custom domain.
- Liferay PaaS cloud allows wildcard use in certificates but is not valid for custom domains.
- The solution is to set each custom domain without using a wildcard.