I don't know if the following reason is also the reason for the
problems in your case, but such a problem happens usually because of
a non-writable log directory or a log location which was mis-
configured. Sometimes the normal HTTP server can write to its logs
while the SSL stuff has problems (it sounds funny, I know! It must
be an idiotic thing, but I never had the time to examine it...).
Look at your log files (both access_log and error_log); You'll
probably find a warning about this problem.
I can witness that I had the same problem (although there was no PHP
or Perl or FP in that installation), and after fixing the permission
problem, everything worked perfectly.
BTW: You mentioned PHP; Does anybody know when PHP4-beta3 will be
released? There were already 3 deadlines, but no sign for a final
date...
Brett Peters wrote:
>
> I had the same problem with a similar configuration... What's in your error
> logs?
>
> Brett
> [EMAIL PROTECTED]
>
> ----- Original Message -----
> From: Pete Navarra
> To: [EMAIL PROTECTED]
> Sent: Sunday, October 24, 1999 6:12 AM
> Subject: I need help with this....
>
> I have recently installed Apache 1.3.9, and mod_ssl 2.4.5 along with
> FrontPage extensions, PHP, and mod Perl. Everything installed perfectly,
> and I am having no problems except for one thing. When you try to connect
> to my site using HTTPS, you get my certificate presented like it should,
> however, once you accept the certificate, I get one of two errors saying
> there is either no data to send (in Netscape), or that the DNS Server could
> not be reached. ( in Explorer). It doesn't display my website, and pops up
> with nothing. Any suggestions?
--
Eli Marmor
[EMAIL PROTECTED]
El-Mar Software Ltd.
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
