Am Mi, den 23.03.2005 schrieb kalin mintchev um 21:31: > >> apache_1.3.33 > >> mod_ssl-2.8.22-1.3.33 > > > > That is no Fedora Core software, as FC ships Apache2. > > This explains why > > you have no ssl.conf. > > does that mean fc2 has problems with apache 1.3.x with ssl? > i'd rather still use 1.3.x for now... Normally not, but as you compiled the Apache 1.3 your own, you are on your own. > > You will have to recheck your configuration. This is no Fedora related > > problem. Check "netstat" output. Make sure to have a valid "Listen" > > directive for port 443. > > i do: > > for the server: > Listen x.x.x.x:80 > > and for SSL: > <IfDefine SSL> > Listen 80 > Listen 443 > </IfDefine> > > and the vhost for ssl: > <VirtualHost x.x.x.x:443> Check "apachectl -S" and "apachectl -t". Your configuration is not correct. "[crit] (98)Address already in use: make_sock: could not bind to address" That error message sounds clear. If it is really SSL related you have to find out where in your config you configured Apache to bind it to 443 twice. "apachectl" should tell you. Alexander -- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.10-1.770_FC2smp Serendipity 00:57:32 up 6 days, 22:53, load average: 0.30, 0.43, 0.54
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil