Posting this because I can't figure the solution after several attempts...
Long story short, updated the system some days ago and now nextcloud complains about the Let's Encrypt intermediate certificate (R3). This is not specific to nextcloud as far as I understand it (seems to be...
This caused me a fair bit of grief last week, so hopefully this saves somebody else some.
The issue is that after running freebsd-update on an existing system, to get to 12.2-RELEASE, that running pkg (or any fetch-related command), errors similar to the following turn up:
I installed acme-client per this document: https://wiki.freebsd.org/BenWoods/LetsEncrypt
When I run:
acme-client -vNn mydomain.com
I get this error:
acme-client: https://acme-v01.api.letsencrypt.org/acme/new-reg: new-reg
acme-client: https://acme-v01.api.letsencrypt.org/acme/new-reg: bad...
Note: this post is amended because the updated port security/acme.sh is now using its own convention home directory /var/db/acme with dedicated user/group acme:acme
The idea is to limit the use of elevated privileges as much as possible.
- What is this about?
I try to use Sendmail with STARTTLS and certificates from Let’s Encrypt.
I am facing a problem I did not success to solve.
When I use my first configuration:
I installed security/py-certbot (which appears to be the new security/py-letsencrypt) using pkg:
pkg install py27-certbot
However, I am not able to run it:
root@medusa:~ # certbot
An unexpected error occurred:
VersionConflict: (parsedatetime 2.1 (/usr/local/lib/python2.7/site-packages)...