Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

HTTP 500 error when logging in via Liferay App Screen

Written By

Alfonso Crisci

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

  • Users may occasionally be unable to authenticate in Liferay DXP with Liferay Screens for Android. The following errors might be observed in the web server logs:
    POST /c/portal/login HTTP/1.1" 500
    And the mobile devices may show: 
    Cookie invalid or empty

Environment

  • Liferay DXP 7.0+
  • Liferay Screens

Resolution

a) If you are using login mode cookie:

  1. Stop the application server
  2. Add this line to your portal-ext.properties file: auth.token.ignore.origins=com.liferay.portal.action.LoginAction
  3. Start the application server
  4. Go to Control Panel > Configuration > Access "Server access policy"
  5. Disable SYSTEM_USER_PASSWORD and click Save
  6. Re-enable SYSTEM_USER_PASSWORD and Save

b) If you are using login mode oauth2:

  1. Go to Control Panel > Configuration > Access "Server access policy"
  2. Disable SYSTEM_USER_PASSWORD and click Save
  3. Re-enable SYSTEM_USER_PASSWORD and Save
  4. Repeat the operations for all portal instances

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?