Stefan Eissing in gmane.comp.apache.devel (Mon, 5 Aug 2019 10:23:27 +0200): >Trying to sum up what you are saying: mod_md 2.4.40 does not introduce a >new problem, but testing with it exposed an issue that affects both. >There is no regression in 2.4.40.
It was not an noticable issue in 2.4.39 and previous versions. The SSLCertificateChainFile statement may have been superfluous, but it did not prevent Apache from running and it also did not prevent mod_md to do what it is supposed to do: generate a new certificate when the time is there. It had been working flawlessly for the last 7 months. >As to the problem: the SSLCertificateChainFile directive made mod_ssl >fail in conjunction with mod_md and an empty MDomain. Probably, the >fallback certificate was conflicting with the additional chain file. >This fallback is installed until mod_md gets the "real" certificate >from Lets Encrypt. The fallback certificate does not conflict with the SSLCertificateChainFile directive in 2.4.39. Any idea why it fails in 2.4.40, but does not in 2.4.39? >I try to add a test case for that and see how we can improve the interworking. Thanks for your continuing work on the mod_md module! -- Jan
