|
From: <da...@so...> - 2006-01-31 14:08:46
|
Hi again, This time I'll try it from scratch on a test server. From scratch, I'm trying to configure mod_ssl into Apache 1.3.31 I've run the configure ( less the call to the apache source because it's an RPM install) and end up with the following: /usr/libexec/apache/libssl.so /etc/apache/mod_ssl.conf and the following: (I uncommeted the include) ************** # By default, all external Apache modules are disabled. To enable a particular # module for Apache, make sure the necessary packages are installed. Then # uncomment the appropriate Include line below, save the file, and restart # Apache. Note that some modules may need additional configuration steps. For # example, mod_ssl requires a site certificate which you may need to generate. # # Lastly, if you remove a module package, be sure to edit this file and comment # out the appropriate Include line. # ==> mod_ssl configuration settings <== # # PACKAGES REQUIRED: apache (N series) and openssl (N series) # Include /etc/apache/mod_ssl.conf ************************************************************* When, in webmin, I try to configure mod_ssl in reconfigure know mods I end up with mod_apachessl in the apache modules module. There is no mod_apachessl module so restart and apply fail. When I directly add mod_ssl to the configuration nothing shows up in the module except mod_apachessl. When I turn on SSL for the test server I get the following error: Warning: Group directive in requires SUEXEC wrapper. Syntax error on line 1124 of /etc/apache/httpd.conf: Invalid command 'SSLEnable', perhaps mis-spelled or defined by a module not included in the server configuration /usr/sbin/apachectl start: httpd could not be started I guess is it even possible to engage SSL without the Apache source available? Thanks, Dan |