IIS 6：在端口 443 上的同一服务器上设置 2 个 SSL Web 应用程序
我被要求在安装了 sharepoint 2010 的服务器上使用 ssl 创建一个 sharepoint Web 应用程序。问题是这个端口似乎正在用于托管我们的颠覆存储库。因此，当我尝试浏览我的共享点站点时，它只显示一个包含我的存储库的页面。我读过有关安装证书和使用主机标头在一个端口上配置多个站点的信息，但我从未成功完成这项工作。我真的很感激这里的一些帮助。
谢谢！
I was asked to create a sharepoint web application with ssl on a server with sharepoint 2010 installed. The problem is that this port seems to be in use for hosting our subversion repository. So when i try to browse my sharepoint site, it just shows a page with my repository. I've read about installing certificates and configuring multiple sites on one port with host headers but i never succeeded to complete this job. I would really appreciate some help here.
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
假设您谈论的是单独的 SSL 证书（而不是单个通配符证书），我相信每个网站都必须有自己的 IP 地址。据我所知，不可能在同一 IP 地址下运行具有多个 SSL 证书的多个网站。
根据服务器的托管者，您需要为服务器分配一个新的 IP 地址，然后在 IIS 中针对新网站的主机头使用新的 IP 地址。您应该会发现证书工作正常，如果没有，请尝试从网站中删除证书并重新分配它。
仅当网站的主域相同（例如 website1.mydomain.com 和 website2.mydomain.com）时，您才能使用通配符证书。
Assuming you're talking about individual SSL certificates (as opposed to a single wildcard certificate), I believe each website HAS to have its own IP address. AFAIK it is not possible to run multiple websites with multiple SSL certificates under the same IP address.
Depending on who is hosting the server, you would need a new IP address to be allocated to the server, and then within IIS you use the new IP address against the hostheader of your new website. You should find that the certificate works correctly, if not then try removing the certificate from the website and re-allocating it.
You would only be able to use a wildcard certificate if the primary domains of the websites were the same (e.g. website1.mydomain.com and website2.mydomain.com).
托马斯，
我之前遇到过类似的情况，要求规定我们使用 1 个 IP 地址，但域会有所不同（例如 website1.com、somesite.org、website2.us）。
您可以通过使用具有主题备用名称的统一通信证书来实现此目的。目前，Digicert 提供的 UC 证书可以实现此目的，但其他一些 CA 则不能。
本质上，您将有 1 个证书绑定到同一 IP 地址上的 :443。这样做的一大缺点是，如果证书出现故障，所有站点的 SSL 将无法工作。
然而，您必须手动（通过 powershell）将每个域绑定到端口 443，但说明相当简单。
服务器名称指示是另一种方式，但它甚至不是 IIS 6 中的一个选项
Thomas,
I've run into a similar situation before where the requirements dictated that we use 1 ip address, but the domains will be different (eg. website1.com, somesite.org, website2.us).
You can achieve this by using a Unified Communications certificate with Subject Alternative names. Currently, Digicert offers a UC certificate that can achieve this, but some other CA's will not.
Essentially you will have 1 certificate bound to :443 on the same ip address. The big drawback to this is that if the cert goes down, all the sites SSL will not work.
You have to manually (via powershell) bind each domain to port 443 however, but the instructions are fairly simple.
Server Name Indication would be another way, but it's not even an option in IIS 6