It’s bothered me for some time that I was unable to host SSL on more than one domain. And the structure of the directories in my web server was not appealing to me. So I decided to rearrange some things — with varying levels of success.
I relocated directories for a couple of the internal webapps I run. This was largely no problem, and mostly handled by telling webapp-config to upgrade the directory. However, Cacti was a problem. I had a mess of things to tidy up — the cron job that runs the poller, every single data source record (they had a hard-coded path to the RRD file). Then, when it seemed like everything was fixed, I decided to fix up the display issue where Cacti picked up one of the alias IPs on my server Ethernet connection instead of the primary IP. Suddenly, it could not see any data sources.
I tore out my hair checking all the database updates, config files, and so on — nothing. So, I turned to Google, and in fairly short order came up with this link. Looks like it’s always been this way, and was bound to cause some kind of problem eventually. So I redefined the Cacti database tables like they said, et voila!
None of this had anything much to do with the SSL enablement question. Well, when I was fighting with the network config on the server earlier, I added a couple of alias IP addresses. Then in the Apache config I switched from using “VirtualHost *:443” (which can’t work more than once, to which the error messages on startup attested) to specifying an IP for each domain. Error messages gone, and everything works!
Now to get the reverse proxying config enabled so that I can present my newly-enabled SSL virtual hosts to the world!
Crossed Wires 