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 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 weird is going on.
>
> -Dave
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED]]On Behalf Of AndersonCreations.com
>>
>> 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...
>> /usr/local/bin/curl http://localhost/
>> my home page shows up fine
>>
>> When I type...
>> /usr/local/bin/curl https://localhost/
>> I get curl: (7) Connection refused.
>>
>> Oh, and I also tested with the default config that
>> is installed with mod_ssl and got the same results.
>>
>> Any other ideas? It seems that port 443 does not
>> get along well with SSL, only non-SSL.
>>
>> -Deborah
>
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
