Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1672
  • Last Modified:

No binding for SSL on default web site

When running Windows best practice analyser it keeps reporting  “No binding for SSL on default Web Site”. I have checked the bindings and tried to add a new https binding as per the instructions on best practice analyser. However, it tells me that the “specified port is being used by a different binding” although I have tried selecting each certificate.
0
paulmac110
Asked:
paulmac110
1 Solution
 
HarsemCommented:
Hello,

it sounds like you already have another site that uses the Port that you are trying to use for that site. If this is SSL then most likely you are trying to use Port 443.

Can you confirm if this web server is already hosting another site, and if this is already using that port. You cannot have 2 sites sharing the same port.

If you need to create a second site with the SSL certificate you only have 2 options:
- create the binding on another port (such as 9443 or 444)
   This tends not to be doine as this is a non-standard port and most firewalls will block this communication.
- Give this server a second IP address (it can be on the same subnet with the same default gateway) and bind the site to this new IP address on port 443.

Please note however that with option 2 above you need to change your site binding away from the default "*" in the Ip address to the actual IP address of an interface.

If you continue to struggle with this can I ask for print-screens of the IIS config on that server.

Hope this helps

Jens
0
 
BlueComputeCommented:
Is this an SBS server?  If so the https 443 binding is on the SBS Web Applications site rather than the default website.
0
 
Ben KeyserOwner/EntrepreneurCommented:
If I can reopen this question - I have a 4 box-standard SBS 2011 installations. All giving this error/issue. I checked all the sites and ONLY the default sites use 443. Also, the bindings on all the sites are the same, and as I mentioned these are out of the box installations. So, any ideas why the analyser keeps on kicking out this response?

The discussions above does not really seem to present a solution (in my case anyway)

Ben
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now