none
IIS 10.0 binding self-signed certificate based website cannot be accessed RRS feed

  • Question

  • I have set up an IIS 10.0 binding HTTPS-based website using self-signed certificate. A couple of months ago, it can still work perfectly. However, during the past 1 month, it cannot be accessed with the following error message:

    Can’t connect securely to this page

    This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website’s owner.

    Try this:

    • <id id="tlserror_goback">Go back to the last page</id>

    Thereafter I have used all kinds of methods (from the URL https://windows101tricks.com/cant-connect-securely-to-this-page/), trying to fix it, but no help at all.

    Can you please give me a help on this issue? Thanks.

    Thursday, October 17, 2019 3:18 PM

All replies

  • Well, after inspecting the certificate: Is it outdated? Does it use unsafe TLS?
    Thursday, October 17, 2019 3:22 PM
  • Hi, Stefan,

    I was using a self-signed certificate just created by IIS 10.0 itself and then bound it with IIS default web site immediately. I don't believe that it can be outdated so soon.

    Friday, October 18, 2019 12:08 AM
  • I have uploaded a packaged zip file into the URL

    https://onedrive.live.com/?id=8FFA4A1C66CFCED9%21517&cid=8FFA4A1C66CFCED9

    wherein I have included the following two files:

    1) cannot_connect_surely_error.jpg - the screenshot of the https website "Cannot connect surely ..." error message.

    2) site_binding_in_IIS.jpg - the screenshot of the configuration of binding the self-signed certificate (created by IIS 10.0) with the "Default Web Site" of IIS 10.0 server.

    Thank you.


    Friday, October 18, 2019 12:17 AM
  • Some system configuration info is briefed as below:

    1) OS: Windows 10 Pro, Version 1809 (OS Build 17763.805)

    2) IIS: Version 10.0.17763.1

    3) Microsoft Edge: 44.17763.771.0


    Friday, October 18, 2019 12:36 AM