Re: Leaf 7.2.1 lighttpd certificate missing or invalid
Erich Titl <[email protected]> Wed, 5 Apr 2023 17:13:04 +0200
| Newsgroups | gmane.linux.leaf.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Tim Am 05.04.2023 um 16:41 schrieb Timothy Wegner: > Erich, I only renamed the very old lighttpd certificate as a test. I gave > it a different extension. After a save and reboot, the warning message was > gone, and a new certificate with the leaf distribution date appeared, so I > deleted the bad certificate, saved, and rebooted. No more warning messages. Ah, so you always overwrote the newly distributed certificate because there was one in configdb. > > Several lessons learned here. One is to pay attention to boot messages - I > had missed the lighthtp bad certificate for the past five years! I am only assuming here that using the upgrade tool might have saved you from this as it would/should have detected the different certificate and issued a warning. cheers ET ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
OpenPGP_signature
(application/pgp-signature, 840 B) - not displayed