Enabling SSL for virtual hosts on Apache traditionally requires one IP address per virtual host. With the introduction of Server Name Indication (SNI), it is possible to enable SSL for multiple virtual hosts all sharing a single IP address. SNI allows each to serve a correct certificate bound to the virtual hostname.
There is an excellent article that describes how to set up SNI using mod_gnutls here:
http://www.g-loaded.eu/2007/08/10/ssl-enabled-name-based-apache-virtual-hosts-with-mod_gnutls/
BEWARE BEWARE BEWARE
mod_gnutls works great on vps link (I'm using CENTOS 5 LAMP), but BEWARE; if you follow the instructions presented in the article, you will BREAK your vpslink virtual server.
The dangerous command from the article is:
# yum groupinstall "Development Tools"
DO NOT GROUPINSTALL "DEVELOPMENT TOOLS" ON A VPSLINK VIRTUAL SERVER! YOU WILL NOT BE ABLE TO SSH INTO YOUR SHELL IF YOU DO. Any currently-connected sessions will continue to work, so it could take you some time to discover the problem.
My theory is that there is a package somewhere in the development tools group that has some dependency on a graphic environment. There is probably a way to fix it, as scp still works just fine (after a forced reboot of the server); however, the solution I used was to re-install the O.S., which is also a somewhat inconvenient thing to do if you have a lot of data to back up and restore.
There is an easy workaround, though. Instead of doing a group install on "Development Tools", do this:
# yum install flex gcc redhat-rpm-config strace \ rpm-build make pkgconfig gettext automake strace64 \ gdb bison libtool autoconf gcc-c++ binutils \ subversion textinfo python-ldap patchutils byacc rcs \ automake14 automake15 automake16 automake17 doxygen cvs
This is a subset of the packages installed by the group "Development Tools". This subset is sufficient for compiling mod_gnutls, so if you continue and follow the rest of the instructions from the article, everything will work fine.
The remaining packages from "Development Tools" not installed are:
Most of these are probably safe, but at least one of them is dangerous.
vpslink support says:
"It is not uncommon for udev to be added in a given package. udev on an openVZ product will always cause issues. Often, this can be remedied by recreating the pty's and tty's after removing udev from the system."
I have not investigated which, if any, of the above packages might depend on udev.
Copyright © 2009 VPSLink, a subsidiary of Spry
