Date: Mon, 10 Dec 2018 17:56:22 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: certbot lost certificates , and registration data Message-ID: <5314f953-78f4-234a-0a66-5874f9d4fe41@FreeBSD.org> In-Reply-To: <CAHu1Y73NDZk%2BQ2C5GVAGwB48_pGVFFmA4yqUK-xtB_2p4brvrA@mail.gmail.com> References: <4290f82e-ce3a-0ce3-aab7-df21a9c636e6@ifdnrg.com> <fb8d0574-dcae-a7f9-d417-5b3af57a5284@ifdnrg.com> <80637ff8-1c6a-d23b-6bda-bc8b48b5c51b@ifdnrg.com> <CAHu1Y73NDZk%2BQ2C5GVAGwB48_pGVFFmA4yqUK-xtB_2p4brvrA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/12/2018 17:48, Michael Sierchio wrote: > On Mon, Dec 10, 2018 at 6:44 AM Paul Macdonald via freebsd-questions < > freebsd-questions@freebsd.org> wrote: > >> I think this is due to the config dir defaulting to /etc/letsencrypt in >> the latest update, >> >> symlinking /usr/local/etc/letsencrypt to /etc/letsencrypt is a quick fix >> tested as working for me.. > > > +1 > This was due to an upstream change moving where various paths are defined to a different file, and so making the port's attempt to modify the settings in the original file pretty futile. I'll be working on a fix later tonight. Cheers, Matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5314f953-78f4-234a-0a66-5874f9d4fe41>