31 Mar
2017
31 Mar
'17
11:33 a.m.
Dominic Cleal said:
I don't, sorry. One guess is that given how long the site hasn't
actually been live, the .conf file was still using the Apache 2.2
directives. Would Augeas decide that's an error if it knows it's looking
at Apache 2.4?
The reason I couldn't spot them is that they didn't exist - after the
default failed, I'd been using the certonly option and forgot to remove
it when reusing and editing lines from my history. (Blush!)
Thank you for your work.
Ian
What's
made it work is deleting the other site's .conf file. It wasn't
actually being used, but Apache had no problems with it.
If you have the original file still, then I'd be interested in obtaining
a copy to ensure we're tracking or are fixing the bug. I don't
see a new version of vhosts - do you have your sites in a single
file, or in separate files in /etc/apache2/sites-available? - but it's
not difficult to do.
They're in separate files in sites-available, so I now have: