I'd like to know what parameter exactly I need to add to the [renewalparams] section in my renewal/domain.conf in order to specifiy a profile for the next renewal?
1 Like
Hello @Goonie 
When you opened this thread in the Help section, you should have been provided with a questionnaire. Maybe you didn't get it somehow (which is weird), or you've decided to delete it. In any case, all the answers to this questionnaire are required:
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Thank you for assisting us in helping YOU!
1 Like
Rather than changing config files directly, I'd recommend using the certbot reconfigure command with the new settings you want for the cert, and let it handle updating its renewal configuration itself.
Something like
certbot reconfigure --cert-name example.com --preferred-profile tlsserver
Though be warned I haven't actually tried it.
2 Likes
I just tried it and it did not work. Seems it should but didn't.
Worse, I re-ran my original certonly --webroot ... command with --required-profile tlsserver
It created a cert with that profile but did not update the renewal config file.
So, bug in Certbot and I just noticed it was reported last week at their github
3 Likes
Thanks for the hint, I didn't know about the reconfigure command. However, it yields:
No changes were made to the renewal configuration.
Maybe that's symptom about the bug MikeMcQ mentioned below. I'll investigate.
2 Likes