Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: Liferay 7 CE GA4 - Cancel button is not working on server
Hello,
I am facing same issue. On many pages cancel button is not working.
I did the same configurations but didn't worked.
We have deployed our application on AWS in private subnet. this can be accessible by AWS Load balancer.
172.16.98.72 is the private IP of the server and AWS Load balencer doesn't have any public ip , it has only DNS name (A Record)
The Load balencer is mapped with DNS name.
We are accessing the application via DNS only.
Please see my for configurations,
direct.url.ips.allowed=172.16.98.72,127.0.0.1,SERVER_IP
redirect.url.security.mode=ip
redirect.url.domains.allowed=
redirect.url.ips.allowed=127.0.0.1,SERVER_IP
Any suggestions?
I am facing same issue. On many pages cancel button is not working.
I did the same configurations but didn't worked.
We have deployed our application on AWS in private subnet. this can be accessible by AWS Load balancer.
172.16.98.72 is the private IP of the server and AWS Load balencer doesn't have any public ip , it has only DNS name (A Record)
The Load balencer is mapped with DNS name.
We are accessing the application via DNS only.
Please see my for configurations,
direct.url.ips.allowed=172.16.98.72,127.0.0.1,SERVER_IP
redirect.url.security.mode=ip
redirect.url.domains.allowed=
redirect.url.ips.allowed=127.0.0.1,SERVER_IP
Any suggestions?
chandrakant Lotke:
Hello,
I am facing same issue. On many pages cancel button is not working.
I did the same configurations but didn't worked.
We have deployed our application on AWS in private subnet. this can be accessible by AWS Load balancer.
172.16.98.72 is the private IP of the server and AWS Load balencer doesn't have any public ip , it has only DNS name (A Record)
The Load balencer is mapped with DNS name.
We are accessing the application via DNS only.
Please see my for configurations,
direct.url.ips.allowed=172.16.98.72,127.0.0.1,SERVER_IP
redirect.url.security.mode=ip
redirect.url.domains.allowed=
redirect.url.ips.allowed=127.0.0.1,SERVER_IP
Any suggestions?
Did you Resolved the issue i am also facing same issue.
srini vasulu:
Please give us some clues about your exact setup: What's the protocol between loadbalancer and server? What is your configuration? What do you observe? What have you tried already?
Did you Resolved the issue i am also facing same issue.
Olaf Kock:
Hi Olaf Kocksrini vasulu:Please give us some clues about your exact setup: What's the protocol between loadbalancer and server? What is your configuration? What do you observe? What have you tried already?
Did you Resolved the issue i am also facing same issue.
in portal-ext.propeties added below propertiesredirect.url.security.mode=ip
redirect.url.domains.allowed=domain name(like ssss.ssss.net)
redirect.url.ips.allowed=server ip,127.0.0.1,SERVER_IP
in tomcate config folder in service.xml <Connector port="80" protocol="HTTP/1.1" scheme="https" secure="true" proxyPort="443"
connectionTimeout="90000"
redirectPort="8443" URIEncoding="UTF-8" />
cencel buttons of roles edit, user edit and file move popup addFolder, addsubfolder buttons are not working .
if we remove scheme="https" secure="true" proxyPort="443" and above properties then with ip address it's working fine.
If you want to allow redirects based on domain, you should set
redirect.url.security.mode=domain
redirect.url.security.mode=domain
srini vasulu:
The scheme https on port 80 is quite unusual, and most likely you'll need some update to the loadbalancer's configuration when you change between serving http vs https on your appserver.
if we remove scheme="https" secure="true" proxyPort="443" and above properties then with ip address it's working fine.
That's actually fine if you terminate SSL on a reverse proxy/loadbalancer. It just tells the tomcat server and the applications: Trust me, browsers think that they are talking https with you. So, please, if you generate urls, make them https://...
As long as SSLEnabled is false, port 80 will still use http protocol.
As long as SSLEnabled is false, port 80 will still use http protocol.
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™