-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explicit renewal command in documentation #12
Comments
Good idea, it's just
Yeah, that's a good idea.
I think long propagation times are more exception than a rule. I think the overall best way to handle this would be to add a few lines to the text printed before pausing, indicating that if your DNS propagation times are unfortunately long, you can |
I am also interested in explicit instructions to setup certbot-auto to auto-renew the cert. |
You should follow the recommended Certbot installation instructions on your distribution. Adding If you installed Certbot from a package repository of your distribution of choice, the systemd timer is most likely already installed for you. Check https;//certbot.eff.org/ for detailed instructions for your distribution. |
Thanks. Was able to setup certbot-auto to run in a cronjob and add some deploy hooks in the renewal-hooks/deploy directory. |
I'm having problems with certbot renew. It seems that evertime a new TXT entry is generated, so it always returns like this: Domain: sub.mydomain.com.br Everytime the value is different. What may I be doing wrong? Thank you. |
Will it work to run certbot renew if usage is using "--manual" ? DNS-01 method assume that TXT record is created, renew task assume that this record will be created automatically so we need some plugin for DNS provider to create TXT automatically. So there are a lot of question how to implement it when usage only speak about one time run usage. |
May I suggest to add inn the documentation the exact command required for the renewal and also where "critical" information is stored to avoid deleting a required file. Even after RTFM, oe figures out how to proceed but it would nice to have explicit instructions in the README.
On a different topic, in instances were there is a complex configuration of name servers, the propagation of the CNAME might take quite a while. It would be nice to have the option of exiting at the "Press enter to continue" point and restart the command later. It would be more elegant than having to do a to abort the script. Upon restart, the credentials and the CNAME are already in place and everything works smoothly.
The text was updated successfully, but these errors were encountered: