Quote from: fraenki on May 06, 2026, 01:42:23 PMIf you want to dive even deeper: try to query the TrueNAS API endpoint "system.ready" using `curl` and your API key. The API documentation is available here:
https://www.truenas.com/docs/api/scale_websocket_api.html
It should make the root cause more obvious, but crafting the `curl` command might be a challenge.
Hi Fraenki,
I have the same problem as OP and when I copied the command from the logs and tried running it manually from an SSH shell (with the environment variables set) I got the follwing output:
root@router:/ # /usr/local/sbin/acme.sh --deploy --syslog 6 --log-level 1 --server 'letsencrypt' --home '/var/etc/acme-client/home' --cert-home '/var/etc/acme-client/cert-home/689ca6dd3b9044.57803608' --certpath '/var/etc/acme-client/certs/689ca6dd3b9044.57803608/cert.pem' --keypath '/var/etc/acme-client/keys/689ca6dd3b9044.57803608/private.key' --capath '/var/etc/acme-client/certs/689ca6dd3b9044.57803608/chain.pem' --fullchainpath '/var/etc/acme-client/certs/689ca6dd3b9044.57803608/fullchain.pem' --domain 'truenas.mgmt.lofjard.se' --ecc --deploy-hook truenas_ws --insecure
[Thu May 14 14:56:38 CEST 2026] Checking environment variables...
[Thu May 14 14:56:38 CEST 2026] Environment variables: OK
[Thu May 14 14:56:38 CEST 2026] Checking TrueNAS health...
/usr/local/sbin/acme.sh: midclt: not found
[Thu May 14 14:56:38 CEST 2026] TrueNAS is not ready.
[Thu May 14 14:56:38 CEST 2026] Please check environment variables DEPLOY_TRUENAS_APIKEY, DEPLOY_TRUENAS_HOSTNAME and DEPLOY_TRUENAS_PROTOCOL.
[Thu May 14 14:56:38 CEST 2026] Verify API key.
[Thu May 14 14:56:38 CEST 2026] Error deploying for domain: truenas.mgmt.lofjard.se
[Thu May 14 14:56:38 CEST 2026] Error encountered while deploying.
A quick "find / | grep midclt" returns nothing. Is my install broken or is there a file missing from the ACME plugin?
"