OpenBSD 6.4 acme-client bad CA paths

New acme-client.conf

authority letsencrypt{
api url “https://acme-staging-v02.api.letsencrypt.org/directory
account key “/etc/acme/letsencrypt-privkey.pem”
}

domain www.arborlux.com {
alternative names { arborlux.com }
domain key “/etc/ssl/acme/private/arborlux/arborlux.key”
domain certificate “/etc/ssl/acme/arborlux/arborlux.crt”
domain full chain certificate “/etc/ssl/acme/private/arborlux/arborlux.pem”
sign with letsencrypt
}

domain www.ocuellar.com.mx {
alternative names {ocuellar.com.mx mail.ocuellar.com.mx biblioteca.ocuellar.com.mx}
domain key “/etc/ssl/acme/private/ocuellar/ocuellar.key”
domain certificate “/etc/ssl/acme/ocuellar/ocuellar.crt”
domain full chain certificate “/etc/ssl/acme/private/ocuellar/ocuellar.pem”
sign with letsencrypt
}

Just the same:

acme-client -vvDA www.arborlux.com
acme-client: /etc/ssl/acme/private/arborlux/arborlux.key: domain key exists (not creating)
acme-client: /etc/acme/letsencrypt-privkey.pem: account key exists (not creating)
acme-client: /etc/ssl/acme/private/arborlux/arborlux.key: loaded RSA domain key
acme-client: /etc/acme/letsencrypt-privkey.pem: loaded RSA account key
acme-client: https://acme-staging-v02.api.letsencrypt.org/directory: directories
acme-client: acme-staging-v02.api.letsencrypt.org: DNS: 104.102.202.177
acme-client: https://acme-staging-v02.api.letsencrypt.org/directory: bad CA paths
acme-client: transfer buffer: [{ “keyChange”: “https://acme-staging-v02.api.letsencrypt.org/acme/key-change”, “meta”: { “caaIdentities”: [ “letsencrypt.org” ], “termsOfService”: “https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf”, “website”: “https://letsencrypt.org/docs/staging-environment/” }, “newAccount”: “https://acme-staging-v02.api.letsencrypt.org/acme/new-acct”, “newNonce”: “https://acme-staging-v02.api.letsencrypt.org/acme/new-nonce”, “newOrder”: “https://acme-staging-v02.api.letsencrypt.org/acme/new-order”, “revokeCert”: “https://acme-staging-v02.api.letsencrypt.org/acme/revoke-cert”, “v8nzg65fo0g”: “Adding random entries to the directory” }] (724 bytes)
acme-client: bad exit: netproc(1429): 1
acme-client -vvDA www.arborlux.com
acme-client: /etc/ssl/acme/private/arborlux/arborlux.key: domain key exists (not creating)
acme-client: /etc/acme/letsencrypt-privkey.pem: account key exists (not creating)
acme-client: /etc/ssl/acme/private/arborlux/arborlux.key: loaded RSA domain key
acme-client: /etc/acme/letsencrypt-privkey.pem: loaded RSA account key
acme-client: https://acme-staging-v02.api.letsencrypt.org/directory: directories
acme-client: acme-staging-v02.api.letsencrypt.org: DNS: 104.102.202.177
acme-client: https://acme-staging-v02.api.letsencrypt.org/directory: bad CA paths
acme-client: transfer buffer: [{ “keyChange”: “https://acme-staging-v02.api.letsencrypt.org/acme/key-change”, “meta”: { “caaIdentities”: [ “letsencrypt.org” ], “termsOfService”: “https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf”, “website”: “https://letsencrypt.org/docs/staging-environment/” }, “newAccount”: “https://acme-staging-v02.api.letsencrypt.org/acme/new-acct”, “newNonce”: “https://acme-staging-v02.api.letsencrypt.org/acme/new-nonce”, “newOrder”: “https://acme-staging-v02.api.letsencrypt.org/acme/new-order”, “revokeCert”: “https://acme-staging-v02.api.letsencrypt.org/acme/revoke-cert”, “v8nzg65fo0g”: “Adding random entries to the directory” }] (724 bytes)
acme-client: bad exit: netproc(1429): 1