[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] webserver shuts down after submitting a self signed ssl cert



> From: "Charles Williams \(CEO\)"
> <hosting.mailing.list.account@xxxxxxxxxxxxxxx>
> Reply-To: cobalt-users@xxxxxxxxxxxxxxx
> Date: Sat, 19 May 2001 17:55:21 +0200
> To: <cobalt-users@xxxxxxxxxxxxxxx>
> Subject: Re: [cobalt-users] webserver shuts down after submitting a self
> signed ssl cert
> 
> 
> ----- Original Message -----
> From: "Rod Poplarchick" <rod@xxxxxxxxxx>
> To: <cobalt-users@xxxxxxxxxxxxxxx>
> Sent: Saturday, May 19, 2001 5:35 PM
> Subject: [cobalt-users] webserver shuts down after submitting a self signed
> ssl cert
> 
> 
>> webserver shuts down after submitting a self signed ssl cert.
>> 
>> I try to Follow all the steps in the Manual but my web server locks up.
>> 1 enable ssl on main site
>> 2 generate a self-sign-cert
>> This is as far as I get because the server reboots I click on go to ssl
>> admin page and every time the page loads something I get a SSL error
> window
>> I click continue and finally get to the main menu.
>> 
>> I could not get to any http: pages at all I could only get to  the admin
>> https: page to remove the self signed cert.
> 
> You are doing name based hosting?  If so you may need an extra IP for each
> domain needing SSL.  I don't recall if this is 100% the rule but I don't
> remember reading anything differant.
> 
> chuck

Thanks chuck but I am using 1 Ip but only my mail site will have the ssl
I check Every SSL directory I could find and there is no Personal Key or
cert on file.

> 
>> 
>> My httpd log shows this.
>> 
>> 
>> [Wed May 16 14:33:02 2001] [crit] (98)Address already in use: make_sock:
>> could n
>> ot bind to port 80
>> 
>> [Wed May 16 14:34:49 2001] [warn] VirtualHost 209.155.26.151:443 overlaps
>> with V
>> irtualHost 209.155.26.151:443, the first has precedence, perhaps you need
> a
>> Name
>> VirtualHost directive
>> 
>> [Wed May 16 14:34:49 2001] [crit] (98)Address already in use: make_sock:
>> could n
>> ot bind to address 209.155.26.151 port 443
>> 
>> [Wed May 16 14:45:12 2001] [warn] VirtualHost 209.155.26.151:443 overlaps
>> with V
>> irtualHost 209.155.26.151:443, the first has precedence, perhaps you need
> a
>> Name
>> VirtualHost directive
>> 
>> [Wed May 16 14:45:12 2001] [crit] (98)Address already in use: make_sock:
>> could n
>> ot bind to address 209.155.26.151 port 443
>> 
>> [Wed May 16 14:53:53 2001] [warn] VirtualHost 209.155.26.151:443 overlaps
>> with V
>> irtualHost 209.155.26.151:443, the first has precedence, perhaps you need
> a
>> Name
>> VirtualHost directive
>> 
>> [Wed May 16 14:53:53 2001] [crit] (98)Address already in use: make_sock:
>> could n
>> ot bind to address 209.155.26.151 port 443
>> 
>> After I deleted the Cert the SSL setup window still showes the SSL request
>> key.
>> 
>> I want to make sure this will not happen again when I put the real SSL
> cert
>> in for if I delete it I will have to pay for a new one.
>> 
>> Does any one know where to start on this problem?
>> 
>> 
>> <(©¿©)>
>> Rod Poplarchick
>> Climate Control Systems
>> Oakhurst, Ca

>