Re: Can connect to SSL using localhost but not remotely

[Robert Madsen <madsen.robert@xxxxxxxxx>]

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 <nick@xxxxxxxxxxxx> wrote:

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 KNOW I'm typing the right IP address!).

Sounds like your routing/firewall.

I'd suggest you use a client that tells you what's wrong when it can't connect to the server.
You can check it by typing an address you know to be bogus: then if it tells you 404 you
know it's lying, and useless for any kind of development/diagnostic work.

--

Nick Kew
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx