



domain without prefix (www) works while domain including prefix (www) won't work.

Imporant Edit: It seems that IE11 can handle only the non-prefix domain and not the prefixed domains when TLS1.2 is enabled. Now to the real questions: Why Why does Internet Explorer 11 is unable to connect to my HTTPS site when TLS 1.2 is enabled within IE? And how to fix it on server side? SSL Labs is telling that everything is fine on my site. But I can't do this on my visitors browsers. disabling TLS1.2 within IE worked and my site is available again. From that point in time my "WTF checklist for IE" contains "disable TLS1.2" as a checkpoint. There was absolutely no sign of an encryption related issue on the entire error page (like normal browser would do).īack a couple of month there was this schannel issue which prevents TLS1.2 enabled IEs to access HTTPS sites. And the typical dummy bla bla like check the DNS and so on. And IE11 shows me a builtin error page witch basically only says "the page could not be shown". Some special function is not working with Chrome or Firefox so I launched IE11 on my Windows 7 machine. Today I discovered an issue with one of my 3rd party services. Every week I run the SSL Labs server test which says IE11 is able to access my sites. I use it only in design time for interface tests (development machine and with unencrypted http). Normally I don't use Internet Explorer at all.
