This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 1%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
I migrated a working IIS web server from on-premise Hyper-V, which is using a SSL certificate that will not expire for one year. Strangely, the HTTPS website no longer works in Chrome and Edge even for localhost even though it works on-premise. Even if I allow insecure content in Chrome, the site will not load. I get errors that the site cannot be reached. The https site now only works in IE, which we never use. Has anyone run across this problem? Any idea what the solution might be?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 82%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBZ%3C/text%3E%3C/svg%3E)
Hi @lkrjgejkrtegnjkerg ,
How you migrate the IIS from Hyper-V to local? When you use chrome, you can click F12 to check security part. It will show you insecure information of certificate. Then you will know if the certificate is expired, invalid or lost.
Another thing is can you show the binding of site? It is better to use the all unassigned in the site binding instead of setting the ip address.
Don't forget to clear cache and cookie, restart DNS client and try again.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
so is the dns name the same for the new site as the on-prem dns name? if not, you need a new cert, as they are ties to the dns name.
The dns name for the site is exactly the same, and I have tried using a localhosts file to have it use both the server ipaddress as well as 127.0.0.1 separately.