But if I invoke **yast **it combines all the vhost.conf files into a single ip-based_vhosts.conf file and deletes all the vhostn-ssl.conf files (yikes!!), disabling SSL. And it won’t let me change to namebased vhosts. And no manner of googling reveals documentation on how to avoid these effects.
Basically, yast http-server is broken and has put itself out of business.
Bottom line: do the .conf files manually in /etc/apache2/vhosts.d and do not touch yast http-server.
I have saved the working site as another directory so that if something else mucks it up I can just recopy and restart the server.
But this is NOT satisfactory. I’ll file a bug report.
I’ve never been able to use YaST to get a site to be configured properly. I think I first tried around 2011 or maybe 2012. I normally install Apache 2 and enable mod_ssl with YaST and then leave it at that. Normally I just do what you did, Alavarre, and manually tweak the apache conf files and hope that I never have to enter the http config module again (which will obliterate the manual config) or that a patch doesn’t just obliterate the manual config. I’ve only had my config obiterated about twice over the years and I learned my lesson to back it up after the first time.
I always used to configure and compile from source (so obviously I had to configure Apache manually), but I decided to switch to just managing the servers through YaST to make it easier to panage patch application. Maybe it’s because I started out manually configuring Apache that causes me to find it so hard to use YaST to configure Apache? I dunno. It’s the thing I dread the most when trying to get set up after installing a new version of OpenSuse though. The only thing that stops me from just giving up and going back to source compilation is the thought of having to faff about with manually patching Apache.