Legacy Knowledge Base
Published Jul. 2, 2025

Custom domains do not accept wildcard

Written By

David Tello

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

  • 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.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base