Warning: This question is largely academic.

I have a website in IIS 8.5, with an HTTPS binding on port 8443. The relevant netsh lines are:

IP:port                      :
Certificate Hash             : 887250f4acef494ef4583e8dc8f1c7b5a40a90ed
Application ID               : {4dc3e181-e14b-4a21-b022-59fc669b0914}
Certificate Store Name       : My
Verify Client Certificate Revocation : Enabled
Verify Revocation Using Cached Client Certificate Only : Disabled
Usage Check                  : Enabled
Revocation Freshness Time    : 0
URL Retrieval Timeout        : 0
Ctl Identifier               : (null)
Ctl Store Name               : (null)
DS Mapper Usage              : Disabled
Negotiate Client Certificate : Disabled

In Firefox or Internet Explorer, I can access the site without issue using either or https://hostname:8443/. In Google Chrome, I can only access the site using https://hostname:8443. Attempts to access the site as return an error page with this text:

The webpage at `` might be temporarily down or
it may have moved permanently to a new web address.

The client machine is using Windows 7 64-bit, with Google Chrome Version 41.0.2272.101 m.

The server is Windows 2012R2. For testing purposes, Windows Firewall is offf and no antivirus software is installed on the server. I've looked in the event logs on the server, and I see no recorded error in the Application or System logs.

Any insights are greatly appreciated. Thanks in advance!

  • I would be looking into whether Chrome will access HTTPS over port 8443 giving the error ERR_CONNECTION_ABORTED which appears to be a Chrome error. I know this sounds simplistic, but there may be code in how the browser was written and not having to do with the network or the server that prevents this. This may be a security measure or a bug. Who knows? It may be that IE and Firefox are more permissive. For HTTPS it is always suggested that you use port 443. en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers – closetnoc Mar 28 '15 at 21:23
  • The same error happens when using 443. Also, please remember that accessing the site by hostname works, so its very unlikely the issue is related to a port. – Vinny Mar 30 '15 at 13:04
  • Oh yeah. My bad!! Just thinking through my hat for a minute there... – closetnoc Mar 30 '15 at 14:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.