I have created a new liferay instance with the following details,
Web ID: demo5.floor.com
Virtual Host: demo5.floor.com
Mail Domain: floor.com
Max Users: 100
Active: Yes
After giving the above above details I saved the portal instance. The instance got saved successfully. After that I restated the liferay server and tried to access the newly added portal instance with following URL in the browser, http://demo5.floor.com But I am not able to access the page (Web page is not available).
Did I miss anything in the portal instance creation process? Do I need to add the domain names anywhere in the system properties or property files?
Any suggestions?
Is this demo5.floor.com a public host??
If not, Please add host entry in your local system for
127.0.0.1 demo5.floor.com
after that, hit following URL in browser
http://demo5.floor.com:8080
if you are running on port 8080.
Related
I created the Container App where i would like to access from its website using host url
My container app into the vnet and it is having specific resource groups and and it contains specific NSG rules
Also, I have created and configured the private DNS zone in which I create a Virtual Network Link associated to VNET,
than I added a dns record set with name *.[same container app address] and container app ip address
When i tied to access the container app using app url i am not able to access it is showing the below error
{"statusCode":404,"message":"Cannot GET /","error":"Not Found"}
when i close ad reopen the url again got one more error
I deleted entire app and created newly got the one more error
Any help will be needed, Thankyou.
I tried to check same in my environment and got the below results
I created the virtual network with subnets
After that created the container app environment
If I check the application URL in the browser I am not able to access because I did not set the private dns zone record set
created the private dns zone and linked with the virtual network
I have added the dns record with container IP address to access the web
When I check in the command prompt I am able to see the that my container app URL is working
nslookup app-container.icycliff-187ffXXXXXXXXX.io
When check in the browser using app URL I am able to get application
NOTE:
1). After creating private dns zone must add the dns record with container app static IP address
2). 404 error message when website content has been removed or moved to another url
3). server responsible for the website is not running or the connection is broken
I am new to iis. I have create a website in my iis for my website content. Want to ask how can i bind the domain name with the site in iis for internal use.
this is what i have tried so far.
When you want to bind the domain name locally you have to bind it in the host file which is located at C:\Windows\System32\drivers\etc\hosts.
add your machine IP and domain name as suggested in the below format:
192.168.6.52 domian.com
by using this method you can only access it on your machine. the host file is only for the machine in which you are accessing the site.
now set the iis site binding as shown below:
clear browser cache and history and browse your site.
I know this may be straight forward and may have already been asked but I have been unable to get proper online articles on this or atleast I don't know how to ask google. so here's a scenerio.
I have a Windows Server which will be hosting applications.
These applications need to be accessible over the internet.
NOTE I'm aware I can just port forward and users can access the apps via a public IP. This isn't how I want it.
Users should be able to access my apps through www.my-apps.com. This domain will be registered with e.g. Godaddy, etc.
How do I go on about this ? No matter how complicated this maybe, I am ready to get my hands as dirty as possible to implement this.
You can modify the hosts file of the server hosting your site to point to the local machine's IP when visiting the www.my-apps.com domain should do it.
Open the IIS Manager, in the Connections pane of IIS, expand the Sites and select the website which you want to access via IP address.
Click on Bindings link and you will see current bindings of that website.
Click on Add button to add a new binding, On the Add Site Binding window, keep website Type as http. Select an IP address from the drop-down menu upon which you want to bind the website, then type www.my-apps.com in the Host name, click OK and then Close.
open this file: c:\Windows\System32\Drivers\etc\hosts.
Add the following entry to the file: IP Address www.my-apps.com
Save to save your changes
I am using multiple domains to access liferay portal instance.
For example following are the domains mapped in hosts file of windows:
www.liferaytest1.com
www.liferaytest2.com
and in Liferay's Control Panel → Portal Settings, www.liferaytest1.com is set as virtual host.
I can access portal instance with all above mention domains along with localhost.
When I access portal with www.liferaytest1.com then I can access Guest site pages directly. Say, home is a page in Guest site then instead of accessing with www.liferatest1.com/web/guest/home I can access it directly with www.liferaytest1.com/home
So URL is shortened to some extend.
So far so good.
First Concern
Now when I try to access portal via www.liferaytest2.com and when I click any sites listed in My Sites portlet of Liferay, it redirects me to that site with the domain mentioned in virtual host i.e. www.liferaytest1.com instead of retaining www.liferaytest2.com.
Suppose I have a Site named Help, so when I click on help site link in My Sites portlet then instead of staying with www.liferaytest2.com domain it redirects me with www.liferaytest1.com domain.
This is due to virtual host mapping done in liferay.
Second Concern
When I am accessing the portal with www.liferaytest2.com and subscribe to any of the Assets then the links in email contain the virtual host domain i.e www.liferaytest1.com.
How to overcome above mention issues?
My requirement is to stay relative to the portal accessing domain.
When I access portal via www.liferaytest2.com then it should not redirect me to www.liferaytest1.com on-click of any of the Site-links as explained above and also emails that I would be getting should also be relative to the domain I am accessing i.e. www.liferaytest2.com.
First of all: You're not required to use that feature - it's implemented in a certain way (e.g. as you describe) and if that doesn't suit your needs, there's no need to configure individual virtual hosts. There's no problem serving all content through just a single virtual host or do the resolution on Apache (e.g.) - that is, fully external to Liferay. The only drawback is that you'll need the clue of the site you want to access (e.g. /web/guest as part of the URL) so that Liferay knows what content to serve.
However, you might be closer to what you'd like to achieve if you change URLs to a structure like test1.example.com and test2.example.com - this way you share at least the toplevel domain and might be able to do some cheaper single-sign-on (you can still do SSO with completely different domains)
You don't need to change the virtual host in Control Panel → Portal Setting for such requirement. Rather keep it to localhost. This will resolve both of your concerns.
Next you want to access portal using two different domain, you can do it through DNS settings. Map both to same IP (the IP of Liferay portal) and you will reach Liferay portal using any one. It will not change the url and will stay from the name initiated.
Context
We have a SharePoint site set up on a Windows Server 2008 VM box.
We also developed a SP event receiver in C# and registered it with the appropriate SP site and subscribed to the following events:
ItemDeleted;
ItemFileMoved;
ItemUpdated;
The following is list of SP info:
local machine name: testsp;
local ip: 10.152.0.248;
port: 80;
Alternate Access Mappings
internal Zone public
http://localhost default http://testsp
http://testsp default http://testsp
http://10.152.0.248 default http://10.152.0.248
Issue/Symptom
When using SP site is accessed from IE using localhost as a URL, and when a document is deleted and added, the subscribed events fire. But if I use testsp or the ip address the events don't fire.
My suspicion lies with AAM but cannot figure out where.
Please help
If any SP guru could point out the issue, I'd be most grateful.
TIA,
Cullen
It turned out that the user who logged in to upload to SharePoint has no permission to write to Windows Event Log.