On Thu, Mar 31, 2022 at 9:36 AM qji <1706...@bugs.launchpad.net> wrote:
> Isn't this cron config already redundant and unnecessary as there is a
> certbot.timer systemd unit?
The certbot cronjob will short-circuit itself if systemd is running on
the host, so that the systemd timer takes precedenc
Isn't this cron config already redundant and unnecessary as there is a
certbot.timer systemd unit?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706409
Title:
should be possible to disable certbot
[Expired for python-certbot (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: python-certbot (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
On Fri, Mar 15, 2019 at 02:41:22PM -, Jonathan Kamens wrote:
> >You should be able to remove or edit /etc/cron.d/certbot, and by policy
> packaging is required to respect your change. Does this not work?
>
> Yes, this appears to work (at least, after removing the file, `apt-get
> install --rei
>You should be able to remove or edit /etc/cron.d/certbot, and by policy
packaging is required to respect your change. Does this not work?
Yes, this appears to work (at least, after removing the file, `apt-get
install --reinstall python3-certbot` on disco doesn't recreate it), but
as I understand
(and similarly you should be able to disable the systemd certbot.timer
using systemd's usual mechanisms, and this change should also be
preserved by packaging)
** Changed in: python-certbot (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a me
You should be able to remove or edit /etc/cron.d/certbot, and by policy
packaging is required to respect your change. Does this not work?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706409
Title:
(Sorry can't edit my comment - the output of renew that I pasted doesn't
match the cli.ini contents because I ran them at different times and
forgot I'd changed it from one to the other!)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think I've found a solution (for my issue at least):
# certbot --version
certbot 0.17.0
# cat /etc/letsencrypt/cli.ini
deploy-hook = /srv/letsencrypt-post-renew.sh
# certbot renew --dry-run
...
Dry run: skipping deploy hook command: /usr/sbin/service apache2 reload
...
In later versions it
I have the same problem - I'm trying to make sure Apache and MySQL are
reloaded after the renewal happens so they pick up the new SSL
certificate. (I don't know if that's handled by this package already,
but I haven't seen anything to indicate it is - there's no post-renew
hook in the cron job.)
N
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python-certbot (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706409
Titl
11 matches
Mail list logo
