Hi Ádám,

thanks for your reply! Indeed, this solved the issue. On our system the hostname resolves in /etc/hosts to 127.0.1.1 which is not covered by redirect.url.ips.allowed. As soon as I add 127.0.1.1 here, it works! Alternatively I tested with redirect.url.domains.allowed which works fine, too. Any advantages/disadvantages here?

The second issue seems to be fixed by the latest Fix Pack 82. Independent from the redirect issue it did not occur again.

Thanks again,
Mirko

Hi Adam,

Thanks for your assistance! Adding my load balancer service IP to the redirect.url.ips.allowed list resolved the issue.

Thanks again,
Derek

Dear Mirko, Derek,

Without an in depth analysis, but seeing the symptoms I probably have a clue for the first issue (and the " running Server Administration functions").

Please verify the following portal properties in your environment and make sure that all redirect domain names or ip addresses are set which you use.

Snippet from the portal.properties with default values:

Best regards,
Ádám

I also see both these errors after updating to fix pack 77.

I've enabled com.liferay.portal.struts logging and this reported in the logs when running Server Administration functions (Resources, Script, etc)...

10:11:42,133 DEBUG [ajp-bio-9109-exec-7][PortletAction:162] Forward to null
10:11:42,137 ERROR [ajp-bio-9109-exec-7][PortletRequestProcessor:466] Forward does not exist

These issues seem to point to the sendRedirect function in PortletAction.

Same for Liferay Fix Pack 78.