https not running on Internal IP address.

Hi I am using windows server 2008 and IIS7,I have setup my website publically,I have even taken https certificate for that.It working fine when i try to access https on public URL but if I try to access using internal IP then same site not running on HTTPS.Please help me whats going wroung.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dan McFaddenSystems EngineerCommented:
So there are a few things going on here:

1. The SSL Cert is fixed to a specific domain or hostname in a domain.  Depends on the certificate type.  for example:  if you use an SSL Cert for www.YourDomain.ext on a server with www.NotMyDomain.ext, you will get an error stating that the hostname of the website does not match what is configured in the SSL Cert.

2. If a site in IIS is setup to be accessed on a specific IP, it will not answer if you try to access it with another IP.  Irrelevant if the server has more than 1 IP configured on it.

Is there a reason you want your internal users to access the secure website from an internal IP?

SudhanshumAuthor Commented:
Let me explain again.Suppose my public url is I have taken certificate for that . Now in IIS ,my internal URL is http: for ,if I m trying to access it using https:,Then it does not work But https:\\  is working.

Dan McFaddenSystems EngineerCommented:
Well, the URL matches what is in the SSL Certificate configuration.  If you go to the website using the IP, you will get an error because the SSL Cert does not care what the site's IP is.

The Cert will only properly function if the hostname, domain and extension match what is in the SSL Cert.

There is nothing wrong with your certificate.

If you intend to serve content using https, then everyone should access the website using the URL (fully qualified domain name - FQDN) that is in the certificate.

Pankaj ParmarCommented:
Hello Sudhanshu,

If you want to access the site using IP Address with HTTPS protocol then please go through following article.
It is possible to attach SSL to IP address as well, you will need wild card certificate to achieve your goal.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.