Apache + mod_ssl

alienDog · 02-27-2012, 05:04 PM

I tried setting up a secure webserver as described in this how-to:

http://www.linuxquestions.org/linux/...ache_SSL_Howto

My apache however simply refuses to co-operate. apachectl startssl says "/usr/sbin/apachectl startssl: httpd started", but http really isn't started at all (there are no running httpd processes). error_log says this:

[crit] (98)Address already in use: make_sock: could not bind to port 80

apachectl start starts apache normally, but without ssl enabled.

bathory · 02-28-2012, 01:18 AM

Hi,

Please note that "apachectl startssl" is not used in newer apache versions. If you've configured ssl correctly, then using apachectl "start" should start both the http and the https instances.
You didn't mention your distro, but you can easily find a tutorial about configuring apache with ssl for your distro. If you face any problems afterwards, we'll be happy to help. And don't forget that you can check apache error_log to see what is wrong with your configuration

Regards

alienDog · 02-28-2012, 10:03 AM

The system is Slackware 11.0 with old apache 1.3.41. I think that's what the how-to I tried to follow also used. Could you maybe point me to a good tutorial for apache+ssl?

Thanks

bathory · 02-28-2012, 11:24 AM

Hi,

I have to ask: is upgrading Slackware and/or apache an option? Can you compile from source a newer version of apache?
If not, you should get mod_ssl and the latest openssl from here, and use installpkg/upgradepkg to install them.
Unfortunately I couldn't find a tutorial for slackware+apache-1.3.x+mod_ssl, but once you've installed everything, follow the instructions of the howto you used and if you have any problems post here along with config file(s), logs etc

Regards

alienDog · 02-28-2012, 02:03 PM

Upgrading is always an option, but since this installation is pretty well tuned and does what I need it to (well, except for the ssl...), I'm not planning on upgrading it anytime soon. However I could compile a newer apache from the source. Then again, I might just go with lighttpd while I'm at it. It's supposedly easier to configure than apache.