Foren
Virtual Hosting peoblem
gagan singh, geändert vor 9 Jahren.
Virtual Hosting peoblem
New Member Beiträge: 2 Beitrittsdatum: 05.12.14 Neueste Beiträge
Hi ,
I am new at using liferay . I am using liferay portal 5.2.2 at localhost with tomcat . When i type my ip like http://localhost:8086/ the webpage opens and i am able to login . Same is the case if use my ip address instead but whenever i use a domain name like http://whythisnowork.com , then it says "Unknown host" error .
I made changes to host file as 127.0.0.1 whythisnowork.com and went to control panel ->portal-> settings and made changes to virtual hosting under main configuration but it's not working .
Please suggest a solution .
I am new at using liferay . I am using liferay portal 5.2.2 at localhost with tomcat . When i type my ip like http://localhost:8086/ the webpage opens and i am able to login . Same is the case if use my ip address instead but whenever i use a domain name like http://whythisnowork.com , then it says "Unknown host" error .
I made changes to host file as 127.0.0.1 whythisnowork.com and went to control panel ->portal-> settings and made changes to virtual hosting under main configuration but it's not working .
Please suggest a solution .
David H Nebinger, geändert vor 9 Jahren.
RE: Virtual Hosting peoblem
Liferay Legend Beiträge: 14919 Beitrittsdatum: 02.09.06 Neueste Beiträge
If you type "ping whythisnowork.com" on the command line, does it try to send pings to 127.0.0.1?
You're actually going to be looking for two issues. First, make sure whythisnowork.com actually does resolve to 127.0.0.1. The second issue, if http://localhost:8086/ works, then the url to try is going to be http://whythisnowork.com:8086/ (you're only changing the host name, not the port).
This has nothing to do with virtual hosts at all, really.
You're actually going to be looking for two issues. First, make sure whythisnowork.com actually does resolve to 127.0.0.1. The second issue, if http://localhost:8086/ works, then the url to try is going to be http://whythisnowork.com:8086/ (you're only changing the host name, not the port).
This has nothing to do with virtual hosts at all, really.
gagan singh, geändert vor 9 Jahren.
RE: Virtual Hosting peoblem
New Member Beiträge: 2 Beitrittsdatum: 05.12.14 Neueste Beiträge
Hi David , i tried that and it did not work .
The exact command i typed in cmd was
ping whythisnowork.com
I got this as a result
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
After that although i have tried that before , i tried "http://whythisnowork.com:8086/" again and got
"unable to locate server name whythisnowork.com" .
The exact command i typed in cmd was
ping whythisnowork.com
I got this as a result
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
After that although i have tried that before , i tried "http://whythisnowork.com:8086/" again and got
"unable to locate server name whythisnowork.com" .
mark grant, geändert vor 9 Jahren.