Depending on the commands you used for your initial cert generation, you might
not need the standalone option. If you did DND or webroot validation you’re may
need to tweak the command line.
-Sent from my Pip-Boy 3000
> On 13/12/2019, at 4:47 PM, ChandranManikandan <kand...@gmail.com> wrote:
>
>
> Thanks Chris,
>
> Let me try out above all of your options and update you.
>
>> On Wed, Dec 11, 2019 at 1:54 AM Chris <boh...@gmail.com> wrote:
>> Running certbot nightly is excessive. You can't renew until you get near
>> the end if the current expiration period. Also, there are other things you
>> may need to do as part of the cert replacement on a qmailtoaster box. I
>> have this cronjob:
>>
>> 1 1 1 * * /root/migration/certbot.sh
>>
>> That runs this script: (/root/migration/certbot.sh)
>>
>> #!/bin/sh
>>
>> qmailctl stop
>> systemctl stop dovecot
>> systemctl stop httpd
>>
>> TIMESTAMP=`date +"%Y%m%d-%H%M%S"`
>> cp -a /var/qmail/control/servercert.pem
>> /var/qmail/control/servercert.pem-$TIMESTAMP
>> certbot renew --agree-tos --standalone
>> cat
>> /etc/letsencrypt/live/[SERVERNAME-REDACTED]/{cert,chain,fullchain,privkey}.pem
>> > /var/qmail/control/servercert.pem
>> chmod 640 /var/qmail/control/servercert.pem
>> chown vpopmail.vchkpw /var/qmail/control/servercert.pem
>>
>>
>> qmailctl start
>> systemctl start dovecot
>> systemctl start httpd
>>
>>> On Tue, Dec 3, 2019 at 9:03 PM ChandranManikandan <kand...@gmail.com> wrote:
>>> Hi Friends,
>>>
>>> I have installed letsencrypt on COS7 and i try to make cron job as per the
>>> below steps, but the cert renew and certbot folder are not there in /opt.
>>>
>>> 0 0 * * * /root /opt/certbot renew
>>>
>>> Is any other way is there or did i made any mistake?
>>> Anyone had the same problem?
>>>
>>> --
>>> Regards,
>>> Manikandan.C
>
>
> --
> Regards,
> Manikandan.C
