But maybe there is no upgrade, and the answer is manually edit them and then cross your fingers a future update fixes this.Ĭertbot 0.31.0 is the newest version packages for Buster, but it’s not the newest version that exists. So I hope it’s as simple as deleting the certs, upgrading Certbot and regenerating them. I could manually edit them and probably fix this for now, but I can’t help wanting to know why it’s failing, and would feel better knowing all the automated aspects worked as I prepare to cron the cert renewal. conf files have these except for these two. ![]() I know the reason these are failing is due to a lack of any paths being written below ]. I read there was a bug in this version that could account for this, but I when I apt-upgrade Certbot it insists I’m on the latest version. ![]() Operating System: Debian GNU/Linux 10 (buster) I have run certbot delete on these and tried generating new certs, but they still fail on the renewal dry run. When I run certbot renew -dry-run all my certs are primed to renew – except the two for these domains which fail with a “Missing command line flag or config entry for this setting” error.
0 Comments
Leave a Reply. |