Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

404 Not found error when managing a site from a localized virtual host if the referrer site does not support the same languages

Written By

Jorge García Jiménez

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 navigating from a site with some language configured to other site that don't support that language, a 404 error is shown.

  1. Create a site "Site-us" and set English as the default language. Remove the other languages.
  2. From the "Site-us" settings, configure a virtual host for the public-pages / English language: site-us.liferay.com.
  3. Create an empty public page /home in "Site-us".
  4. Create another site "Site-es", set Spanish as the default language of this site, and also remove the other languages.
  5. Create an empty public page /home in "Site-es".
  6. Access site-us.liferay.com:8080 and sign in.
  7. Go to manage site pages and, using the site selector, select "Site-es".
  8. A 404 error is shown.

Environment

  • Liferay DXP 7.2, 7.3

Resolution

  • To avoid showing a 404 when the URL locale is not supported on the site, set the property: 
    locale.use.default.if.not.available=true
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?