On Sun, Aug 7, 2011 at 1:42 PM, Robert Madsen wrote:
> When you say type "httpd -S" on the command line, are you talking about the
> Windows prompt? I tried this and it said httpd is not recognized.
>
> Also, if it helps to know I am running Windows 7 Ultimate Service Pack 1.
>
Yes, the Windows c
I'm not sure what you mean by "use a client that tells you what's wrong when
it can't connect to the server". Do you have any suggestions or examples?
Thanks!
Robert
On Sun, Aug 7, 2011 at 11:21 AM, Nick Kew wrote:
>
> On 7 Aug 2011, at 17:43, Robert Madsen wrote:
>
> > I just did a test...whe
On 7 Aug 2011, at 17:43, Robert Madsen wrote:
> I just did a test...when I type in https://myipaddress, there isn't a single
> entry generated in any of the logs. So it looks like it isn't even hitting
> the server. (When I use http://myipaddress, all is well and it serves the
> page, so I K
I just did a test...when I type in https://myipaddress, there isn't a single
entry generated in any of the logs. So it looks like it isn't even hitting
the server. (When I use http://myipaddress, all is well and it serves the
page, so I KNOW I'm typing the right IP address!).
Thanks.
Robert
On
On Sun, Aug 7, 2011 at 3:40 AM, Robert Madsen wrote:
> I have been able to successfully configure the server so that if I type
> https://localhost, it serves up the correct page.
>
> However, if I use the IP address (remotely or on the server) e.g.
> https://xx.xx.xx.xx, I get the error message:
>
On 7 Aug 2011, at 08:40, Robert Madsen wrote:
> Any suggestions would be appreciated.
What does the error log say?
(If nothing, your client is lying when it tells you 404).
--
Nick Kew
-
The official User-To-User support for
I am using WAMP 2.0 with Apache2.2.11. I am trying to configure my server
to access SSL connections.
I have been able to successfully configure the server so that if I type
https://localhost, it serves up the correct page.
However, if I use the IP address (remotely or on the server) e.g.
https:/
