It certainly have to be changed to
0 */12 * * * root perl -e ‘sleep int(rand(3600))’; certbot -q renew
to start one cron job per 12 hours, not a 60 jobs per 12 hours!!
I have a user-related apache 2.4 config includes like
/etc/apache2/sites-available/username
which have some sites description. If I start
certbot --apache
than I see not all http sites in the dialog.
I have to move domain.ru and www.domain.ru configs from
/etc/apache2/sites-available/username
to a separate
/etc/apache2/sites-available/domain.ru
to my site domain.ru and www.domain.ru will be shown by
"certbot --apache" normally.
So this is a inconvenient to split such configs for certbot.
It will be good if you fix that in the new versions.
It will be good idea for your project to support new
international (punycode) domains. Waiting for new versions…
It certainly have to be changed to
0 */12 * * * root perl -e ‘sleep int(rand(3600))’; certbot -q renew
to start one cron job per 12 hours, not a 60 jobs per 12 hours!!
I have a user-related apache 2.4 config includes like
/etc/apache2/sites-available/username
which have some sites description. If I start
certbot --apache
than I see not all http sites in the dialog.
I have to move domain.ru and www.domain.ru configs from
/etc/apache2/sites-available/username
to a separate
/etc/apache2/sites-available/domain.ru
to my site domain.ru and www.domain.ru will be shown by
"certbot --apache" normally.
So this is a inconvenient to split such configs for certbot.
It will be good if you fix that in the new versions.
It will be good idea for your project to support new
international (punycode) domains. Waiting for new versions. Thank you!`
That is odd, my cronjob looks like this by default:
cat /etc/cron.d/certbot
# Upstream recommends attempting renewal twice a day
#
# Eventually, this will be an opportunity to validate certificates
# haven't been revoked, etc. Renewal will only occur if expiration
# is within 30 days.
0 */12 * * * root perl -e 'sleep int(rand(3600))'; certbot -q renew
Could you elaborate a bit on that? Is this about the fact that certbot currently doesn't support files with multiple <VirtualHost> tags, or were you having some other issue (in which case the actual config would be useful)?
The <VirtualHost> limitation is a long-standing bug and something that comes up quite often, but it's hard to get it right as there's a gazillion of ways to structure apache config files. Hopefully it will get fixed in 1.0 as currently planned.
Yep, that's currently planned for the end of august! Just an ETA at this point though, so no guarantee that it will be on time.
<VirtualHost 194.177.20.83:80>
ServerAdmin support@maasoftware.ru
DocumentRoot /var/www/maa/data/html/download.maasoftware.ru
# #SuexecUserGroup maa maa
#
#
AssignUserID maa maa
#
ServerName download.maasoftware.ru