Home/ Questions/Q 7747307
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T10:29:48+00:00

Can someone explain to me how I can fix this problem. I have two

  • 0

Can someone explain to me how I can fix this problem.

I have two sites hosted on the same IIS7 server.

Site 2 has SSL setup and can be found at https://www.site2.co.uk

Site 1 does not have ssl setup and is binded on http://www.site1.co.uk

Now if you go to https://www.site1.co.uk it throws this error on google:

This is probably not the site that you are looking for!
You attempted to reach http://www.site1.co.uk, but instead you actually reached a server identifying itself as http://www.site2.co.uk

I’ve tried using URl rewrite in webconfig file in site1 to stop it looking at port443 but had no luck :(.

Also tried editing applicationhost.config to include the following line but that did not work as well

Any help would be great on this matter.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is due to a limitation in the original design of SSL, where the server must present a certificate without knowing what hostname the client wanted. So if you host two sites on the same IP address, the server has to pick one hostname to present to the client.

    TLS SNI fixes this, but is not available in IIS 7 (available as of IIS 8):

    http://en.wikipedia.org/wiki/Server_Name_Indication

    Since many browsers also don’t support SNI, it is common to run a single web server with multiple IP addresses, one IP address per site.

    • 0