Admin Panel Not Accessible After The Upgrade

Development Upgrades
1

Dear Liferay Community,

I have upgraded my Liferay Portal from 7.3.6-ga63 to Liferay CE 7.4.3.132-ga132. The Liferay DB was Oracle 19c which I first converted to the PostgreSQL using the ora2pg tool. Then I performed the upgrade and it worked well. My Liferay Portal was also connected to LDAP but for now, I have removed the LDAP configuration from the portal-ext.properties file because of the testing purpose. But there is an issue that I am facing after the upgrade, I am unable to access the Liferay 7.4’s admin panel. I have tried ‘host:port/c/portal/login’, the URL does get change, but the login page doesn’t open up. I have tried multiple other URLs, but nothing worked so far. I want to access the admin panel so that I can log in as an admin and then I will be able to see the Site Menu, the Global Menu and do everything as per requirement. What could be the solution for this problem?

Regards,

1 Answer

1
2

Hi,

Normally, after successful login, admin functionalities are accessed through the Product Menu / Global Menu.

Since /c/portal/login changes the URL but the login page itself does not render, the issue is likely related to one of the following:

  • Incomplete upgrade process

  • Theme/JSP incompatibility from 7.3

  • Database migration inconsistencies after Oracle → PostgreSQL conversion

  • Authentication or virtual host configuration issues

  • Errors during startup preventing login components from loading

A few things to verify:

  1. Check server logs during startup and when accessing /c/portal/login

    • Look for JSP, authentication, OSGi, or database-related exceptions.

  2. Try accessing:

    • /web/guest

    • /group/control_panel/manage

    • /home

  3. Temporarily switch to the default theme:

    • Custom 7.3 themes can break login rendering in 7.4.

  4. Verify these properties:

    • company.security.auth.type

    • virtual.hosts.valid.hosts

    • web.server.host

    • redirect.url.security.mode

  5. Clear:

    • osgi/state

    • work

    • temp

    • Tomcat cache folders
      Then restart the server.

  6. Confirm the upgrade completed successfully:

    • Check Release_ table entries

    • Verify all upgrade processes reached completion

  7. If LDAP was previously enabled, ensure no stale LDAP auth configuration remains in the database or OSGi configs.

Most commonly in these upgrade scenarios, the root cause ends up being:

  • incompatible custom theme/modules, or

  • errors during DB migration/conversion.

If you can share the browser console errors and relevant startup logs, it would help identify the exact cause.