yesterday night i crashed my server (debian sarge). i updated confixx to 3.2.1. he told me that the installation was a complete success, but apache2 (2.0.5x) had something else to say:
Code:
Fangorn:~/confixx# apache2ctl -k start
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
Unable to open logs
Fangorn:~/confixx#
now i found several people who had the same message, and they all had the problem that another app was listening on port 443. ports were free. i now removed a "Listen 443" directive from confixx_mhost.conf and now all userwebpages work as intended (some .htaccess' doesn't work anymore) but the only ssl-secured website, the confixx control panels, do not work at all.
well, i'm wildly looking around for some clues and hints.
apache2 now is listening on port 80 and 443.
Code:
Fangorn:/etc/apache2# netstat -nap --inet |grep LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 9802/apache2
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 9802/apache2
why doesn't confixx send out its ssl sites? i wasn't able to figure that out till now.
now i take a nap and then start to look into all ssl stuff.
please help me on the right track.
greetings,
simon
