HTTPS not working
in [IIS]
|
From: Jack W. on 10 May 2010 17:53 Hi there, I just set up my own test certificate on my home network server using the server's (web) IP address as the certificate's "common name" (x.x.x.x). I can now access the site through the web via HTTP://x.x.x.x but not using HTTPS. I get the standard "Internet Explorer cannot display the webpage" error or a timeout failure on Firefox. However, if I replace "x.x.x.x" with the server's *local* IP address then I can access it using both HTTP and HTTPS. IOW, it's only when I try to plug in the real (web) IP address for "x.x.x.x" that HTTPS doesn't work. Does anyone have any ideas on what might be causing this. The problem exists regardless of the client machine and I've tried shutting down the firewall (on both server and client). Thanks in advance.
From: Dan on 13 May 2010 07:30 "Jack W." <_no_spam@_no_spam.com> wrote in message news:#LzDrsI8KHA.1760(a)TK2MSFTNGP04.phx.gbl... > Hi there, > > I just set up my own test certificate on my home network server using the > server's (web) IP address as the certificate's "common name" (x.x.x.x). I > can now access the site through the web via HTTP://x.x.x.x but not using > HTTPS. I get the standard "Internet Explorer cannot display the webpage" > error or a timeout failure on Firefox. However, if I replace "x.x.x.x" > with the server's *local* IP address then I can access it using both HTTP > and HTTPS. IOW, it's only when I try to plug in the real (web) IP address > for "x.x.x.x" that HTTPS doesn't work. Does anyone have any ideas on what > might be causing this. The problem exists regardless of the client machine > and I've tried shutting down the firewall (on both server and client). > Thanks in advance. Do you have a firewall in the router that your public IP address maps to? Or does it use NAT? Either way, you need to open up incoming connections for port 443 to allow SSL. -- Dan
|
Pages: 1 Prev: Define default site displayed when typing the IP address? Next: IIS6 and SSL |