Can't connect securely to this pageRSS

3 replies

Last post Oct 11, 2019 08:01 AM by Yuk Ding

  • Can't connect securely to this page

    Oct 09, 2019 02:10 PM|sn002|LINK

    Hello everyone,

    Windows server 2012 r2.  IIS8.

    I manage a CAC enabled website and recently it gives me errors below.  It is been working fine and suddenly I got that errors. I have tried different suggestions but did not work.  Hopefully someone here point me to the right solution.  Thank you.

    Error: This page can't be displayed.  or Can't connect securely to this page.

    This might be because the site uses outdated or unsafe TLS security settings.

  • Re: Can't connect securely to this page

    Oct 10, 2019 03:16 AM|Yuk Ding|LINK

    Hi sn002,

    When did you start face this issue? Did you apply any update before this issue happen? Could you create and access a simple http site from the same server?

    The error message just looks like Schannel configuration has been changed in server side. So rollback the update being installed recently could help. 

    Besides, you could try to enable all TLS configuration with IIS Crypto to check whether this is an Schannel issue.

    Best Regards,

    Jokies Ding

    Yuk Ding

    MSDN Community Support
    Please remember to "Mark as Answer" the responses that resolved your issue.
  • Re: Can't connect securely to this page

    Oct 10, 2019 01:10 PM|sn002|LINK

    Hi Yuk,

    It has been a week or so.  The update done by someone else though and it is being pushed by the network team.  This is DOD network so it is most likely only allow https sites to go thru their network.  Where do I go in server side to change Schannel configuration?  Can you give me more details.

    Thank you.

  • Re: Can't connect securely to this page

    Oct 11, 2019 08:01 AM|Yuk Ding|LINK

    Hi sn002,

    The third-party software provide a GUI way to change schannel configuration.

    https://www.nartac.com/Products/IISCrypto/Download

    You could try to enable all protocol or disable SSL 3.0 and leave TLS 1.0 1.1 1.2 open.  Please try different combinations to find a workaround.

    Since the root cause could be complicated, figure out what operation did they do before this issue occur would be the best plan.

    Besides, you could try to monitor ssl handshake with network monitor. Maybe it would give us some insight about how to fix this.

    https://www.microsoft.com/en-us/download/details.aspx?id=4865

    Best Regards,

    Jokies Ding

    Yuk Ding

    MSDN Community Support
    Please remember to "Mark as Answer" the responses that resolved your issue.