I am very new to Orchard, and am having a most difficult time setting up IIS bindings. I am not proficient at IIS, and am new to web development in general.
Say I have domain1.com which is the main Orchard site (landlord). I properly set up domain2.com in the Multi-Tenant module. My DNS records on the server work properly if I have domain1.com and domain2.com as separate sites (i.e., I can type in domain1.com and see the Orchard landlord site, I can type domain2.com and see the default page used by my control panel).
I guess I am just having a hard time binding. I fiddled around with DNS settings using my servers control panel - no luck. I then tried using IIS to "bind" domain2.com to domain1.com but am pretty sure I have made a mess of it. :)
I've searched around for an answer, but nothing seems to work or otherwise I am unable to fully grasp the concept. The Orchard documentation doesn't really deal with IIS bindings (it deals with using the development machine to host the multi-tenant sites, but I am dealing with a live server - all my "development", such as it is, is done).
Any suggestions? Thanks.
To get bindings working for multi-tennancy working you can do one of two things.
Set a catch all domain binding:
Create a site in IIS with the binding set to all unassigned IP addresses and no host name. Any domain pointing at the IP of your server will point at this site and Orchard multi-tennancy will decide which of your Orchard sites to point it at. Only one IIS site can have this setting or they will clash.
Add multiple domain bindings: In ISS create a site for bound to domain1.com, then under edit site click bindings and add a new binding for domain2.com.
Related
I am new to Hetzner so I am sorry if my question doesn't make sense.
Long story short, this is my situation:
I have 2 WordPress Websites and each of them is hosted in a different hosting, from a different hosting provider (not Hetzner).
My goal is to host both of my WordPress Websites in one account on Hetzner (one hosting).
I asked this question before and I got told that I should buy Web Hosting Level 9 package, so that I can add both of my sites as add on domains and that they can be literally 2 different WordPress Websites but they would have the same hosting (site1.com and site2.com , but same host).
And I did just that. I purchased Web Hosting Level 9 package and during the purchasing process I had to claim a free domain. I did that and used "aisolutionmontenegro.com" , but I don't plan on don't anything with this particular domain.
Now after that I added the domain my first WordPress Website as a add on domain, and it showed up.
The problem that I am facing is that I want to install WordPress to this first add on domain, but I can not see the option "WordPress" on the Services part, like I see it when I am on the main domain that I claimed for free "aisolutionmontenegro.com".
The domain I claimed for free
Remember, I don't need aisolutionmontenegro.com at all, I just want to add two add on domains and on each of them install WordPress. Is that possible and how?
The domain of my site
Thank you in advance!
I found out what the problem was.
When I added the "main" domain with I claimed for free while buying Web Host Level 9 package from Hetzner, I had to go to "Products" and then select the "main" domain.
After I selected the main domain, in the left side menu, go to Services and you can see there WordPress. We click WordPress and then go to the installation process.
During the installation process you have to choose a root directory for your site, and here is where you need to be careful.
If you want to install your WordPress site on an add on domain (let's assume its called "site1.com") then you need for the root directory to create a new folder called the name of your site (in this case create a folder "site1").
After that you can continue with the installation process normally.
And for every add on domain that we want to install WordPress on we do the same thing, we click on the "main" domain, and then we click WordPress. During the installation process as the root directory we create a new folder called like the add on domain (for example our second add on domain is called "site2.com", we create a folder called "site2").
i'm running sharepoint 2010 foundation, on win7. since installing SP2010, none of my other localhost websites load in the browser. i'm either prompted for a login, or it just returns blank pages. i've tried putting my other websites within the SP-80 directory in iis7, which allowed the pages to load, but required a login. i tried various combinations of windows authentication on different iis7 directories, but nothing worked. i'm left with the impression that iis7 requires a single port 80 directory, rather than distinct, named directors, with separate permissions. the issue could be complicated by having my other sites mapped to a virtual directory, requiring my admin creds, to allow iis access to the files.
my question is, is it possible to host public, unprotected, port 80, web sites, along with SP2010? i'm not very experienced with IIS, so please forgive me if i'm overlooking the obvious.
sure it is possible. While creating WebApplications in SharePoint you're able to specify the port, the WebApplication will run on.
You should have a look at your Site Settings within IIS. SharePoint is by default not running on anonymous authentication mode.
Please analyze if you do have site collections created under Web Application using Powershell or from Central Admin
If you have Web Application created but no Site Collections, then you will get same issue
Sandeep
If you want other sites on IIS on the same port on the same machine, you'll need to declare IIS host headers. When you create a new Site in IIS, there is a bindings section (IIS 7.5 - in IIS6, I believe it's just called Host Headers) - set your bindings to be myotherwebsite.com or myotherwebsite.local. Make sure the names you use in your bindings match DNS names that are pointing to that machine, either through public DNS (if it's a public site) or through your local hosts file (\windows\system32\drivers\etc\hosts) if it's only for your local use.
Going the host headers route, you bypass the sharepoint execution stream completely - set your site up just as you would any other.
I am working under localhost.
In IIS Manager 7.5, windows server 2008.
After adding a new application in "Application pools", I added a new asp.net web application site using that application pool.
The problem is how can I run that website on localhost to check whether the site is working correctly or not?
People told me that I have to add bindings "domains" for that site and run the site using those domains. But that is not convenient as every time adding a new site on IIS, I need to have a domain to check the result?
I think it should be possible to run the site under localhost somehow but I dont know.
Any ideas?
Thanks in advance.
The simplest way is to add a virtual directory to your default web site within IIS. Point that virtual directory to the directory to which you installed/copied your website.
The you can either browse from IIS or type the virtual directory name (preceeded by localhost/) into your browser address bar.
If the problems is with "domains" yo do not have to buy domains. By asigning different port numbers on localhost you can add new bindings.
As I know adding binding is essential for IIS to understand which site should be opened.
For example you can assign port numbers like
80 -default- , 81,82 ... 8090...
Is there a way to setup subdomains udner Xp Pro IIS for something like test.localhost
Can it be done via IIS or the hosts file? Need to do a tets on a site that uses pathign back to the root so having the site ina virtual directory like localhost/test causes issues.
As you're probably well aware that out of the box IIS 5.1 only supports one web site. What you can do is use the adsutil.vbs tool to create a second site in IIS 5.1 and configure it to use that.
The following article explains the process:
IIS: Creating Multiple Web Sites within IIS on Windows 2000 and Windows XP Professional
There's even a GUI widget to make life easy:
http://www.firstserved.net/support/downloads
So in a nutshell:
Create a second site using one of
the methods above (set the IP
address to your machine's primary IP
address)
Add a host header for
test.localhost domain to the new
site
Edit the HOSTS and add an entry for
test.localhost pointing at the IP
address above
Easiest way is to just switch the document root of the lone site you already have to the different folder with the target site. Then you can switch it back when done.
If you are building stuff in virtual directories off the root, this shouldn't even effect any ongoing projects.
I seem to recall there was a tool which did this for you, but I've forgotten it's name and coordinates.
Create a new website in IIS. The host header value should be your subdomain like "sub.localhost", and then add the domain to your hosts file.
open with notepad the file c:\windows\system32\drivers\etc
and add this line:
127.0.0.1 mysuper-site.com.net.blabla
Then browse to this site: http://mysuper-site.com.net.blabla
We've installed Windows Search Server Express on one of our servers, which apparently runs on top of sharepoint.
Sharepoint was installed on port 80, where our "normal" intranet runs. When I disable the intranet and run the sharepoint site, everything works as intended. The intranet is linked in many places it would be a pain to move it, so I'm trying to move sharepoint to another "place" (hoping this is less of a pain), either a different port or as a virtual directory under the main site.
First, when I make any of these changes, it fails to get access to the intranet root. Not sure what it is looking for there, but ok, I give "Network service" (the acocunt the "Sharepoint 80" application pool is running under) access to the intranet root. This gets me one step further, I am stumped:
When I move the Sharepoint website to another port, it complains that it can't find default.aspx (there is none, but also it doesn't need it when running on port 80)
When I move it to a sub folder of the existing site, and try to open the global.asax in the browser, ti tells me that this extension is prohibited, even though the "Application configuration" is - as far as I understand - identical to that of the Sharepoint site, and allows GET, HEAD, POST, DEBUG for .asax.
Any suggestions?
Sharepoint sites should be able to run on any port- if you go into Sharepoint Central Admin and create or delete web applications without a problem.
Is it your intention to run heterogenously with Sharepoint and your regular site both on Port 80? I know that you can create a web application on 80 and then not have a root site collection ( Sharepoint applications consist of a Web Application that runs on a certain port and any number of Site Collections within that, each of which has it's own directory path and can contain lists, libraries, other Site Collections and so on ) just creating one on a different path, but I don't know for sure how that would work alongside an existing web site on the same port- it may not play nice. Again, you can create and delete site collections from the Sharepoint Central Admin page, which is linked from your Administrative Tools list on your server.I would try this first, as if it works it's an easy solution.
Is Windows Search Server Express related to Sharepoint's own search facilities? If it is you may find that it expects to run using some of the Shared Service Provider facilities, which even Sharepoint doesn't expect to be running on the same port as the sites it's providing services for.
An even better way would be to create another alias (cname) in your DNS for your server, just set a different host header for each web site.
for example, in DNS your machine might be named 'intranet'. Create an alias for that machine named 'sharepoint'
In IIS, create a new website for sharepoint, and set the host header for that site to 'sharepoint.domain.com', where domain.com is your domain.
Do the same for the intranet website, but set the host header to 'intranet.domain.com'
That way, your users don't have to use another port in the URL.
Thank you! I found the option in the sharepoint administration website.
I add this response to detail the steps I have taken - maybe they are useful for someone else.
In the sharepoint administration website (running flawlessly on another port), I chose "create or extend web applications", then "extend existing web application".
There, from the the drop down "Web application", "change web application" opens a popup with the web applications available. Search server was installed as "Sharepoint 80", so I selected that.
Then I selected "Create new IIS website", with a new name and a new port. All the other options looked fine to me as default.
Clicking OK, this creates a new web site in IIS, which was configured correctly. it doesn't work via the IP address of the server (http://192.x.x.x:8080), only using the server name - but that's ok with me :)
I still had to make some adjustments with the access rights, but the full crawl is running and I can find a few documents already. Yay!
This is much easier when you first backup your site and then create a new site from the central admin with a new port number and then restore the backup to it(overwrite)