Home All Groups Group Topic Archive Search About

SSL Site showing Page not found

Author
23 Jun 2005 11:07 AM
TonyR
I've installed a trial cerificate from verisign on my IIS 5. 

Now when I connect to the server using a browser with http://... it says
that the page must be viewed over a secure channel.  If I connect with
https://... it says that the page cannot be displayed.  When I turn off SSL
in IIS and connect using http:// it works fine.

I am using the same common name in the URL that I used when setting up the
certificate.

I have ensured that port 443 is being allowed through my firewall.

Any other suggestions?

Author
23 Jun 2005 12:48 PM
clrscr
Do you have "require secure channel" checked in Site
Properties>Directory Structure>Edit Secure Communications? If you do
than connecting under http will give you that error. You can fix this
by making a page that forwards users to your https site and replacing
the 403;4 error page with it in the custom errors tab.

I am looking at IIS6 but it should be roughly the same.

As far as the page being unable to display when you put in https make
sure that you have a page in the directory and that the main page is
listed under the documents tab as a default content page.
Author
26 Jun 2005 11:17 AM
David Wang [Msft]
It is not clear you set up SSL correctly nor successfully.

Use SSLDiag to troubleshoot.
http://www.microsoft.com/downloads/details.aspx?FamilyID=cabea1d0-5a10-41bc-83d4-06c814265282&DisplayLang=en

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"TonyR" <To***@discussions.microsoft.com> wrote in message
news:D6944369-F4B3-4938-B657-C845D0B5AB06@microsoft.com...
I've installed a trial cerificate from verisign on my IIS 5.

Now when I connect to the server using a browser with http://... it says
that the page must be viewed over a secure channel.  If I connect with
https://... it says that the page cannot be displayed.  When I turn off SSL
in IIS and connect using http:// it works fine.

I am using the same common name in the URL that I used when setting up the
certificate.

I have ensured that port 443 is being allowed through my firewall.

Any other suggestions?