Date: Sat, 20 Apr 2024 21:59:06 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> To: "John Levine" <johnl@iecc.com> Cc: freebsd-questions@freebsd.org, jerry@seibercom.net Subject: Re: certbot Message-ID: <86h6fvajqt.fsf@ltc.des.dev> In-Reply-To: <20240420153432.671268909CE2@ary.qy> (John Levine's message of "20 Apr 2024 11:34:31 -0400") References: <20240420153432.671268909CE2@ary.qy>
next in thread | previous in thread | raw e-mail | index | archive | help
"John Levine" <johnl@iecc.com> writes: > Gerard E. Seibert <jerry@seibercom.net, questions@freebsd.org> writes: > > If I run the command from the command line, it works as expected. I did > > place the following in the environment: CRYPTOGRAPHY_OPENSSL_NO_LEGACY= =3D1 > > I still do not understand why this error only happens from CRON. > > Most likely because that variable is not there. Cron uses a standard > rather sparse environment. See "man 5 crontab". > > In this case rather than messing with the script, just set the > variable on the command line in the crontab, e.g. > > 0 1 * * * CRYPTOGRAPHY_OPENSSL_NO_LEGACY=3D1 certbot ... Even simpler: CRYPTOGRAPHY_OPENSSL_NO_LEGACY=3D1=20 @daily certbot renew --apache put this in, say, /etc/cron.d/certbot. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86h6fvajqt.fsf>