In addition to setting the DocumentRoot in /etc/apache/conf/commonapache.conf, I found that to get SSL working I had to add the following lines: Add LoadModule ssl_module extramodules/libssl.so Include conf/addon-modules/mod_ssl.conf Include conf/vhosts/ssl.default-vhost.conf Note that that the forum topic: <a href="http://forums.gentoo.org/viewtopic.php?t=10737">apache + mod_ssl - no response from https://localhost</a> provided some useful information on fixing this.
when mod_ssl is emerged, it displays a msg: einfo "Execute \"ebuild /var/db/pkg/${CATEGORY}/${PF}/${PF}.ebuild config\"" einfo "to have your apache.conf auto-updated for use with this module." einfo "You should then edit your /etc/conf.d/apache file to suit." if you do run that command, it will add all the appropriate lines to your conf file
Missed that message the first time around, too. There just aren't many ebuilds that require running an extra script, so it's easy to overlook. I assume there's a solid reason to not just automate these steps in this case.
Ok... I went through a lot trouble that could've been avoided. Code: /usr/sbin/apachectl is missing the following code to start ssl Code: startssl|sslstart|start-SSL) if [ $RUNNING -eq 1 ]; then echo "$0 $ARG: httpd (pid $PID) already running" continue fi if $HTTPD -DSSL; then echo "$0 $ARG: httpd started" else echo "$0 $ARG: httpd could not be started" ERROR=3 fi ;; And then, edit Code: /etc/apache/conf/vhosts/ssl.default-vhost.conf to change the root directory to whatever u speficied. After that, you should be able to run apachectl startssl with no problems
