Hi all,
I have been hours troubleshooting this issue, I am deploying Enterprise 11.2, I can't open HTTPS localhost web page with IIS. I have tried many different methods such as:
1- Install all features/services of IIS.
2- Re-Install the IIS
3- Turn off firewall
4- the 80 & 443 ports are already works by default, but for double check I added the ports in the Windows Defender Firewall Rules.
5- each change I was removing the browser caching, using incognito/inprivate browsing, and in addition using two browsers Edge and Chrome.
6- already update IIS bindings to include 443 port with https, and selected the self signed certificate i issued.
7- SSL is turned off
8- anonymous access is enabled
However none of these troubleshooting works, and every time I open HTTPS://localhost or HTTPS://FQDN it gives me:
""
It looks like the webpage at https://localhost/ might be having issues, or it may have moved permanently to a new web address.
Solved! Go to Solution.
Quick update:
I resolved the issue by running a simple PowerShell command (as Administrator) to generate a new personal SSL certificate for IIS. After that, I updated the HTTPS binding on port 443 with the newly created certificate — and it worked!
New-SelfSignedCertificate -DnsName "localhost" -CertStoreLocation "cert:\LocalMachine\My" -FriendlyName "IIS Localhost Cert" -KeyUsage DigitalSignature, KeyEncipherment -Type SSLServerAuthentication
I’m still not sure why it fixed the problem, since both certificates appeared to be of the same type. But for some reason, this one was accepted without any SSL compatibility errors.
Quick update:
I resolved the issue by running a simple PowerShell command (as Administrator) to generate a new personal SSL certificate for IIS. After that, I updated the HTTPS binding on port 443 with the newly created certificate — and it worked!
New-SelfSignedCertificate -DnsName "localhost" -CertStoreLocation "cert:\LocalMachine\My" -FriendlyName "IIS Localhost Cert" -KeyUsage DigitalSignature, KeyEncipherment -Type SSLServerAuthentication
I’m still not sure why it fixed the problem, since both certificates appeared to be of the same type. But for some reason, this one was accepted without any SSL compatibility errors.