Hello all,
Thanks Dave and all of you for your help. It is much
appreciated.
I think we have solved the problem - although I never
figured out how or why
I reinstalled the whole package again. This time, I
was finally able to see error in the error_log. (I
was not able to before). Now,
Er---Isn't the command "apachectl startssl" and NOT "apachectl sslstart"??
--On Thursday, March 22, 2001 07:43:04 PM -0800 David Rees
[EMAIL PROTECTED] wrote:
You definately don't need to be running both sslstart and then start, just
running sslstart should start up both http and https
Ted Fines wrote:
Er---Isn't the command "apachectl startssl" and NOT "apachectl sslstart"??
Cunningly, the current version of apachectl will start SSL with any of
the following arguments: startssl|sslstart|start-SSL (have a look in the
script).
At the end of the day, the real command
It sounds like you are not running "apachectl startssl", and just running
"apachectl start".
Personally, I've found those IfDefine SSL statements a PITA.
What I do is replace all IfDefine SSL statements with IfModule
mod_ssl.c, except for the ones around the mod_ssl LoadModule and AddModule
Thanks Dave,
Here are the results...
I have been starting the server with
/usr/local/sbin/apahectl sslstart
Then
/usr/local/sbin/apahectl start
(Am I supposed to do both - in that order?)
I installed curl (http://curl.haxx.se/) and
tested via the terminal
When I type...
You definately don't need to be running both sslstart and then start, just
running sslstart should start up both http and https servers running on port
80 and 443.
You should have these statements in your httpd.conf
Port 80
IfDefine SSL
Listen 80
Listen 443
/IfDefine
If not, something else