Hosting 2 Sites

I am trying to host 2 sites on the same 10.4 server. I have them both configured to "any" for the ip address. I have purchased domains for both and have them pointing back to my public address. Whenever I go to either site i get the message:
RTSP/1.0 400 Bad Request
Server: QTSS/5.5.2 (Build/489.0.3; Platform/MacOSX; Release/Update; )
Cseq:
Connection: Close
I also have a third site running. It is my webmail. I have it configured to be ssl. So to log in to webmail you just go to https://mydomain.com. This site works fine even when the other two do not. The same domain without ssl just plain http://mydomain.com i get the message. I also get it going to http://mydomain2.com also.
What can i do to fix this???

It looks like you have QuickTime Streaming Server set to stream on port 80. Try turning that off, for starters, if you can.
The HTTPS site runs on port 443, that's why there's no conflict there.

Similar Messages

  • Error Accessing Host Named Site Collections In SharePoint Foundation 2013

    We have a new SharePoint Foundation 2013 server that has one web application two host named site collections. We get the "This page can't be displayed" message when we try to navigate to either of the site collections. Adding the server's IP to
    the host file on the machine we are testing from doesn't help. We can ping the new sites from that machine. The web application does not have a host header.
    Web application URL = http://servername
    Site collection #1 URL = http://customer.company.com
    Site collection #2 URL = http://vendor.company.com

    Hi,
    I recommend to verify the things below:
    Check if site can be accessed with site collection administrator.
    Add the SharePoint sites to a trusted zone to see if the issue still occurs.
    As this issue can be caused by many reasons, you may check the ULS log for more detailed errors.
    For SharePoint 2013, by default, ULS log is at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS.
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • How can I create a host name site collection when I have a 443 web application already created for App model?

    Hi all,
    I have a 2013 farm set up with the App model
    1 web application for path based site collection using host name
    1 web application with SSL (no host name)
    1 web application for mysite
    My business request is that  I need to migrate SSL enabled 2007 content to this farm and use host name site collections.  I tried to create one more web application for this without any luck (the 443 IIS folder is already used by another web application). 
    I thought I bind the previous 443 web application with another IP address should be fine.  Seems like the IIS site is taken (https://server name:443) so it will not let me create one more.  How can I solve this problem so I can create the web application
    to host those host name site collections?  Any suggestion is greatly appreciated.
    Thanks in advance.
    Sally

    Hi Trevor,
    Thanks again for your quick reply.  I try the option 2 right after your post.  I use my front end server name for public URL (https://WFEName:443) and it fails again.  The error message is:
    The directory C:\inetpub\wwwroot\wss\VirtualDirectories\443 is already being used by another IIS Web Site.  Choose a different root directory for your new Web application.
    After reading more, I saw mix Hosted Name Site collection and Path-based site collection aren't recommended.  Unfortunately I already have Path-based site collection created with App model web application
    (the web application without host name) in my farm.  In my Option 2, that web application without host name is used for App routing.  This takes the root folder 443 which will not allow any other web application to use the same name again. 
    Does that mean we can't create Host Named Site collection in the same farm?  Is there any configuration I need to check?
    Thanks again.
    Sally

  • How can I create a new Host Url Site Collection in SharePoint 2013?

    Hi,
    This may sound really daft, but someone is trying to create a new Team Site Host Url Site Collection. We have the one Web Application at
    http://main and all site collections sit underneath. When we try and create a new Site Collection we have URL set as
    http://main/sites.  Our new site should be
    http://newsite. I tried to remove root and sites from http://main managed paths and you can't do it.
    Is it just me, but do you have to create a web application. Create Site collection for that web application and then move to under
    http://main like a SharePoint 2010 migration?
    Help Appreciated.
    John. 

    In that scenario, you would need to create a new Web Application, yes. There is another function called Host-named Site Collections which would get you what you want, but it takes a bit of work:
    https://technet.microsoft.com/en-us/library/cc424952.aspx
    http://blogs.msdn.com/b/russmax/archive/2013/10/31/guide-to-sharepoint-2013-host-name-site-collections.aspx
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Noob needs help with hosting multiple sites

    Hello I am new to this multi hosting. I have looked on the forum for answers but haven't found any. I am trying to figure out how to host multiple sites. I have my dns working for my default site "example1.com", but need to know if I need to add another dns record for my second site. "example2.com". Also when I point to the new fold that has the second site in it and I assign it port 82 for testing purposes I get an error message saying 403 access forbidden. I need to find out how get permission to view the site for the public. Its in a separate folder on an external hard drive right now for testing purposes. Can any body help me or point me in the right direction? Thanks so much!!!
    -Kcam1999

    {quote}
    While what you are telling him is technically functional, it is not correct
    I beg to differ, Paul. You are the one that is not correct.
    CNAMES have been deprecated as of some years ago
    What? huh? really?
    Please show me any official document that states this (and not someone who just started a rumor because he didn't understand them). Indeed, the DNS RFC makes no such claim.
    {quote}
    I stand very much corrected. CNAMEs are not officially deprecated. Interestingly, your post cites precisely what happens when CNAMES used carelessly. How many transactions are needed to resolve Apple's CNAME chain below? RFC1912 (http://www.faqs.org/rfcs/rfc1912.html) has some recommendations that suggests Apple's own network folks have, like me and perhaps even others here, some learning to do. Is that a 'best practice?'
    {quote}> Then make sure you tell Apple since this site depends on the use of CNAMEs:
    dig discussions.apple.com
    discussions.apple.com. 492 IN CNAME discussions.apple.com.edgesuite.net.
    discussions.apple.com.edgesuite.net. 4427 IN CNAME a1399.b.akamai.net.
    a1399.b.akamai.net. 2 IN A 128.241.220.82
    a1399.b.akamai.net. 2 IN A 128.241.220.72
    In fact, it uses TWO CNAMES in a chain. Oh my.{quote}
    From RFC1912 (which I'm sure many have now read here), section 2.4 is as follows:
    {quote}... having chained records such as CNAMEs pointing to CNAMEs may
    make administration issues easier, but is known to tickle bugs in
    some resolvers that fail to check loops correctly. As a result some
    hosts may not be able to resolve such names.{quote}
    {quote}> It is not valid to say "don't use these because they could cause problems'. A records can be just as problematic, as can PTRs. Let's not even talk about MX.{quote}
    How, exactly, does is an A record problematic? No chains, no additional lookups, no wasted cycles...
    We differ here -- and if we are dealing with a newbie, we don't need to enter into unnecessary complexity UNTIL it is a requirement for their solutions.
    {quote}> There are many valid reasons to use CNAMEs in DNS, not least of which is the ease of moving a service if it uses CNAMEs. For example, if you have 10 A records all pointing at the same server and you want to migrate to a different machine you have to locate and update all 10 records. If they used a CNAME to the physical server you could move them all at once using a single change. This is especially important in cross-domain links where you may not control all the origin zone files.
    {quote}
    You're somewhat reaching here, and it is well beyond the scope of the OP's post or needs (well, until they tell us more about their needs, I suppose). There is nothing difficult about 'finding' and updating the necessary records. The final example you gave is a good one and I'll say THAT is an appropriate use of a CNAME, 'though there are other workarounds for it.
    Thanks for keeping me honest.

  • Help Hosting a Site on My Mac mini

    Hey guys, this is my first time posting on the Apple forums, so pardon me if I do something wrong. The problem I have is I'm trying to host a site from my Mac mini, I have purchased a domain name, and set up web sharing w/in System Preferences, and I already had an iWeb page made for my previous domain (Which was set up for me, hence me not knowing what to do). I am interested in using my Mac mini as a server for my site, but I do not know how to do so. I have read this article to try and get instructions: http://www.omninerd.com/articles/Servinga_Website_from_a_Home_Network_on_Mac_OSX
    But it doesn't work for me. All help is appreciated! Thanks in advance!
    Matt

    Whatever application you use, you either publish to the Sites folder in your Home directory or to the Documents folder in /Library/Webserver/
    Check with forums that deal with Unix and Apache.
    Read this article, the part from "Adding a domain to httpd.conf" :
    http://www.wyodor.net/Domain/
    And this page you'll have to translate, but it has links to Apache related documents :
    http://www.wyodor.net/ActiverenPW.html
    http://localhost/manual/
    Once configured correctly, it's great fun.

  • Load balancing host named site collection

    I am jumping into the realm of host named site collection. While the learning experience has been good, still there are some questions unanswered. Please bare patience since my questions are long.
    - I have a non host header site on port 80 that has https certificate added to IIS for supporting app store in https mode.
    - I tried to created the host name site collection using https in this default port 80 non host header web application and was greeted with error. Then i extended the web app to different  zone with port 443 . Then created the host header site collection
    with https with web application name for extended 443 one. Creation went in fine.
    - I tired to use IPs on now extended IIS site and bind certificates on that one. The site does not load. I do the same again in the default zone iss site, bind ips on that one and site loads. Now question is even though host header site collection was created
    using extended web application url , why binding had to be done on default zone IIS site?
    - Second test, i changed the authentication mode for extended, no effect on host named site collection but as soon as i changed it in default zone it reflected in host named site collection. I am confused why it needs extended zone url to create the https
    site but every change done in default zone is getting reflected on this host named site collection.
    Now for load balancing , it works fine with IP? But how to load balance these host named site collection using url. I talked with f5 team and they said i need to send some reply query string from each site. Where do i do that? Or is it even needed? 
    Accoring to this link : https://devcentral.f5.com/articles/name-based-virtual-hosting-with-ltm
    . If the site hosts an application, though, the monitor should request a dynamic page on each webserver which forces a transaction with the application to verify its health and returns a specific phrase upon success.
    For application monitoring, the recommended best practice is to create such a script specific to your application, configure the monitor Send string to call that script, and set the Receive string to match that phrase. 
    Has any one done this before? I tired to search for resource regarding this for iis or sharepoint but was not able to get anything.
    Thank you for your patience for reading such a long question. 
    Adit

    first part of question:
    Default Web Appliction in port 80: Creating https host named site collection fails.
    Extend default web application on port 443 : Https hostnamed site collection created when web application name is passed for extended web application on port 443. This means this site collection is associated with this extended web application correct? But
    all the changes made in IIS only reflect if it is made to port 80 web application. Also changing authentication scheme from Central Admin, only changes on default zone reflects on site collection not the one in extended web application? Why  if the site
    was only created on extended web application paremeter, changes on default are reflecting on it but not from extended.
    Second part of question:
    Each Hostnamed site collection when load balanced thorough f5 using IP for 3 WFE uses 3 IPs for each. This way we will run out of IPs pretty soon. I want to know if there is way to load balance these sites using Hostname or anyother paramenter through f5
    and if any body has done it? 
    https://devcentral.f5.com/articles/name-based-virtual-hosting-with-ltm link talks about sending reply string
    from application but i do not know where to set it up or how to do it? No resources in the net. Just asking if any one else has done it. 
    Adit

  • Using Mac Mini running OSX Server (10.8) to host web sites on LAN

    I would like to know how to use a Mac Mini running OSX Server (10.8 ML) to host web sites on my home network (LAN).
    I am developing web sites and previously (before ML) I used my Mac Pro to 'host' the sites I was developing to test them out before publishing them to my hosting package.  That was when I was using 10.7 Lion and theer was an option in the System Preferences to turn web sharing on.
    I have since upgraded my Mac client to 10.8 ML and have configured it to do the same - even though there is no System Preferences option for web sharing any more.
    I also have a Mac Mini running on my LAN and its been upgraded to OSX Server 10.8.
    Im now trying to configure it to host the web sites I am developing but with no success.
    I thought it was just a matter of adding them as sites in the Server's Websites panel (see screen shot)
    but so far Ive had no success.
    On my Mac client I can simply add a folder in the Sites directory and then open the web site by putting http://myhost/~myuser/name-of-folder and it will load the default file in the folder e.g. index.html
    How do I achieve the 'same thing' on OSX Server?

    Hi Johnfromglenver,
    There are no Mac drivers for the HP Officejet K60 printer. Therefore it is not compatible with the Mac operating systems. Please call our technical support at 800-474-6836. If you live outside the US/Canada Region please click the link below to get the support number for your region. http://www.hp.com/cgi-bin/hpsupport/index.pl. There may be other solutions that could work for you.
    I hope this information helps.
    Advance 23
    I work on behalf of HP

  • Best Practice for Host Named Site Collections and Web Apps

    Looking for advice on setting up the host named site collections.  If I am reading many of the technet articles and blogs correctly I should 1) have only 1 top level web app for host named site collections and 2) not have a host header for that web
    app.  If that's correct I am looking for advice.  We have 7 separate domains that we support in our farm.  Currently each of those domains is divided into web applications based on the domain,  *.contoso, *.trains.com, *.bakers.com, etc.
      Is the concept now that all of the host named site collections fall under that one web app?  How do we deal with the SSL for each of those separate domains which all have their own certificates? 
    Thanks in advance for your comments. 
    NLewis

    Yes, for creating host named site collections, first you create a host header less web app and then create host named site collections under that web app. However this is only for the cases where all the host named site collections ends in one domain. So
    you can create host named site collections as intranet.contoso.com, my.contoso.com, portal.contoso.com etc as they are all ending in *.contoso.com.
    As per your environment, if you have web apps which caters to different domains like *.contoso.com, *.trains.com, *.bakers.com, you need to create separate web apps as they are all ending in different domains. Then you can have a separate wildcard SSL certificate
    for each of those web apps.
    Hope this helps.
    Thanks
    Mohit

  • Content Search Web Part over HTTPS for a Host Named Site Collection

    Hello
    I have a host named site collection http://media.contoso.com which is a media portal that stores videos and pictures. On my parent site collection http://site.contoso.com homepage I have a Content Search Web Part that displays videos from the media portal.
    Both sites work over https.
    When I edit the content search web part and enter the URL http://media.contoso.com in the 'Change Query' box, search returns the results as expected but when I enter the URL as
    https://media.contoso.com no results are returned.
    I have removed the binding in IIS to point to http://media.contoso.com.
    I need it to be https so that I don't see "HTTPS security is compromised by http://media.contoso.com" on my site collection homepage.
    Any idea why this is happening?
    Thanks
    Yoshi

    http://technet.microsoft.com/en-us/library/ee792873%28v=office.15%29.aspx
    In the Search SSL Settings dialog box, do one of the following:
    If you do not want the crawler to crawl a site when there is an SSL certificate warning, make sure that the
    Ignore SSL certificate name warnings check box is cleared. For security reasons, the check box is cleared by default.
    If you want the crawler to crawl a site even if there is an SSL certificate warning, make sure that the
    Ignore SSL certificate name warnings check box is selected.
    If this helped you resolve your issue, please mark it Answered. You can reach me through http://freeit-support.com/

  • Crawl issue - warning: "This URL is part of a host header SharePoint deployment and the search application is not configured to crawl individual host header sites. This will be crawled as a part of ....a start address"

    Hello all,
    I have a multi-tenant environment in SharePoint 2010 server. Different tenants are hosted by one web app.
    One content source has been created to crawl the all shared environment. (the only URL added in the content source settings = URL of the
     web app)
    Crawl everything under the hostname for each start address has been selected when creating this content source.
    Now I have created a new tenant hosted by the same web app. For this new tenant I want to have a different crawl schedule. Simple , I just create a new content source and add the host URL of this tenant. With the same settings has the other content source.
    After having started a full crawl I get 0 success and 1 warning : “This URL is part of a host header SharePoint deployment and the search application is not configured to crawl
    individual host header sites. This will be crawled as a part of the host header Web application if configured as a start address.”
    The first content source is well crawling the new tenant freshly created. Could you tell me where I’m wrong?
    Thanks in advance
    Regards
    Baldo

    Baldo,
    In the configuration that you described you now have 2 content sources set to crawl the same content. If you have a content source with a start address of http://servername/ then it is going to crawl everything past that address. If you are now changing
    the crawl schedule based on the individual site collections, you will need to move your start addresses further down the URL.
    For Example:
    1st Content Source:
    http://servername/ as a start address would now become
    http://servername/site1
    http://servername/site2
    2nd Content Source:
    http://servername/site3
    Also remember that all crawling must happen on the default zone. If you are trying to crawl a zone that the web application has been extended into, that will not work.
    ScottC - Microsoft SharePoint Support

  • Can i host a site on mac os x server?

    hellow guys i need some help, this is my site http://www.inauzwa.com, can i use the mac os x lion server to host this site?
    thank you
    regards arnold gabriel
    cofounder @ http://www.inauzwa.com

    Short Answer: Yes
    Extended Answer: You should have some knowledge of Networks in order to make your site available to the General public if you are trying to host from home - for example you will need a paid service like what DynDNS.com offers - unless you happen to have two static IP's (which is possible to get if you are on cable internet with sufficient bandwidth and yes them 2 IP's would be adressable with only one modem).
    If you get DynDNS ... they explain pretty much everything u need to know to get things running.
    If you get two static IP's you can bind both IP's to your network adapter and then you would need to know a few things about DNS setup and configuration - if you do it properly you can host easily more than "just one" website.
    Technical prerequisites for "website". As long as your website is HTML or PHP/MySQL based u will have no problems at all (I used to administer a XServe Dual G5 Unit which was hosted / colocated in a professional data ceneter up until not to long ago) - unfortunately the last Server OS working on it was 10.5.8 ... then the support and updates stopped (Thanks by the way Apple Inc ... kindda ****** at you guys, that was a perfectly good 1U Rackmount Server)

  • Migrating a Path Based Site Collection to a Host Named Site Collection where the content database is greater than 135 GB

    Hi
    I have a 136 GB content database which will not back up via Backup-SPSite ( Microsoft say you cannot backup more than 100GB).
    So with out Backup / Restore how can I convert a Path Based Site Collection to a Host Named Site Collection  with my 136 GB content database which incidentally uses Remote Blob Storage ?
    Thanks
    Nigel 
    Nigel Price NJPEnterprises

    I see two options:
    Make the Backup-SPSite work despite being over 100GB (that's going to be a supported limit rather than a hard boundary)
    Externalise some of the content and then re-insert it after the move.

  • Having thousands of Host-Named Site Collections - which authentication type?

    So Microsoft seems to state the claims + Host-Named Site Collection (HNSC) approach is the way to go forward.
    Assuming we have thousands of site collections, and we don't want to go with good ol' NTLM authentication as our claim authentication type, then how should we authenticate?
    Both Kerberos and SAML would be a nightmare to manage, since for Kerberos we need to register a Service Principal Name (SPN) per HNSC. For SAML we would end up in a similar situation, since this would require us to configure a relying party
    + realm for every HNSC.

    Please see the documentation on using managed paths with host named site collections.
    http://technet.microsoft.com/en-us/library/cc288637(v=office.14).aspx#section5
    You would be very unlikely to have thousands of individual host names, I would never recommend such an architecture to a customer.  Instead, you are much more likely to use managed paths (/sites/, /personal/, etc) in combination with host names, significantly
    reducing the number of individual host names while still allowing you to easily scale to thousands of site collections.
    In Office 365, each tenant is provisioned with 3 top-level host names (<tenant>.sharepoint.com, <tenant>-public.sharepoint.com, and <tenant>-my.sharepoint.com), all subsequent site collections are provisioned using managed paths.
    Note that this is not really a question particular to HNSC.  If you decide to not use host-named site collections but want to use individual host names using web applications, you get far less.  According to our Software Boundaries and
    Limits document, you get maximum 20 web applications per farm with a maximum 5 AAMs per web application, yielding a maximum 100 individual host names. 
    http://technet.microsoft.com/en-us/library/cc262787.aspx
    While you can achieve more host names using HNSC, I would strongly discourage this design and instead seek to leverage managed paths. 
    Kirk Evans
    Architect, Azure Modern Apps Center of Excellence
    Microsoft Corporation
    Microsoft Certified Master, SharePoint 2010
    http://blogs.msdn.com/kaevans

  • Migrating SP2010 host-named Site Collections

    Hi all, 
    I'm currently having an issue when upgrading Host-Named site collections from SP2010 to SP2013. Once upgraded into SP2013 (Database attach), It keeps on prompting me for credentials, even after adding my user as a Web Application user. 
    Is there any resources or considerations when upgrading Host-Named sites?
    Cheers

    Loopback check is the most common cause of this behaviour:
    http://www.harbar.net/archive/2009/07/02/disableloopbackcheck-amp-sharepoint-what-every-admin-and-developer-should-know.aspx
    To confirm, add a hosts file entry on a non SharePoint machine and then connect from there. It'll probably work.

  • Managed path for host named site collection is farm level or web application level?

    Hi,
    I would like to get advice.
    I created a webapplication for host named site collections.
    these are my host named site collections (except http://sp2013) under my webapplication
    Root Site Collection: http://sp2013
    Site Collection: portal1.sg
    Site Collection: portal1.sg/research
    Site Collection: portal1.sg/intranet
    research and intranet managed paths are farm level
    all my host named site collection will be accessed by http and https except "intranet" site collection will be only accessed by https
    so I changed the Intranet zone for site collection using Set-SPSiteUrl
    Set-SPSiteUrl (Get-SPSite "http://portal1.sg") -Url "https://portal1.sg" -Zone Intranet
    Set-SPSiteUrl (Get-SPSite "http://portal1.sg/research") -Url "https://portal1.sg" -Zone Intranet
    Set-SPSiteUrl (Get-SPSite "http://portal1.sg/intranet") -Url "https://portal1.sg/intranet" -Zone Intranet
    Now I need to create "search" site collection for "Enterprice Search Center"
    My question is that for the "search" managed path ... should i use farm level or web application level?
    "search" site collection will be will be accessed with both http and https also.
    Thanks a lot!

    managed path for HNSC is farm level and u can have 20 managed path
    while managed path for path based is 20 per web application in your case if you are going to have a a separate web application for search then u will use web app
    Kind Regards,
    John Naguib
    Technical Consultant/Architect
    MCITP, MCPD, MCTS, MCT, TOGAF 9 Foundation
    Please remember to mark your question as answered if this solves your problem

Maybe you are looking for