alexzorin

Hi @Nottt, Sorry to hear that. I think we have tried to address all of the problems you're hitting via the instructions on https://certbot.eff.org/instructions. Are you the author of that...

>This probably seems right, however, I then think we need a way to specify that a new key should be created and that key should be used for subsequent renewals....

For sure `renew --reuse-key` is ambiguous. Certbot can always error in that case, directing them to `certonly/run`. >One problem I have is I think --reuse-key is ambiguous, even with --cert-name....

>making this an equivalent, at least at first sight, to the renew verb. Initially I was disagreeing here, because renewal via `{certonly,run}` does not reconstitute renewal params (including `reuse_key`). In...

>Do you feel differently No, I'm onboard with doing nothing. I feel there are going to be some inevitable breakages due to tutorials or whatever and we can deal with...

The debs and rpms for Certbot are maintained by distro packagers, we don't have the scripts to create those. I think publishing this plugin to pypi should work well though....

Yes, I haven't changed anything relating to warning filters or debug mode. `DeprecationWarning` [is filtered out by default](https://docs.python.org/3/library/warnings.html#default-warning-filter) (if not triggered by `__main__`), and we used that in the past...

Oh I see what you mean now. I didn't even notice. I don't recall to be honest! I think it's printing the line of code that is generating the warning:...

@ohemorange are you still able to review this? I can put it back into triage.

Putting aside that Certbot overwrote the certificate in this case (probably because of `--renew-by-default`?), you could avoid this by nominating a name for your certificate: --cert-name duckcorp-mail-cert and it'd be...