https://bz.apache.org/bugzilla/show_bug.cgi?id=65860
--- Comment #5 from Stefan Eissing <[email protected]> --- Under the premises that no one is messing with the file system, e.g. a job that distributes certificates among nodes or other such production jobs, it should never have happened in the first place. In 2.4.49, an additional sanity check was added that "staging" file sets do not get activates if cert+key do not match. Assuming that is what affected your site. You can check in "md/archive/xxx.com* if there is an archived set from the time the problem occurred. That would indicate that a renewal was made and the faulty set of file came from there. If there is no archived set from that time, then this did not happen on a renewal. Then then files in "md/domains/xxx.com" that were working got changed. Since mod_md replaces only directory and has no read/write access there when handling traffic, it strongly hints to an outside agency that messed with the files. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
