I have woken up this morning and now my webmail pages are secure, they were not before. But direct to the same hostname on 443 is still complaining. But I feel this is normal behaviour now?
Ignore last message, webmail different server. [Thu Mar 20 05:00:01 GMT 2025] LE_WORKING_DIR='/root/.acme.sh' [Thu Mar 20 05:00:01 GMT 2025] Running cmd: cron [Thu Mar 20 05:00:01 GMT 2025] Using config home: /root/.acme.sh [Thu Mar 20 05:00:01 GMT 2025] default_acme_server='https://acme-v02.api.letsencrypt.org/directory' [Thu Mar 20 05:00:01 GMT 2025] ACME_DIRECTORY='https://acme-v02.api.letsencrypt.org/directory' [Thu Mar 20 05:00:01 GMT 2025] _ACME_SERVER_HOST='acme-v02.api.letsencrypt.org' [Thu Mar 20 05:00:01 GMT 2025] _ACME_SERVER_PATH='directory' [Thu Mar 20 05:00:01 GMT 2025] ===Starting cron=== [Thu Mar 20 05:00:01 GMT 2025] Using config home: /root/.acme.sh [Thu Mar 20 05:00:01 GMT 2025] ACME_DIRECTORY='https://acme-v02.api.letsencrypt.org/directory' [Thu Mar 20 05:00:01 GMT 2025] _ACME_SERVER_HOST='acme-v02.api.letsencrypt.org' [Thu Mar 20 05:00:01 GMT 2025] _ACME_SERVER_PATH='directory' [Thu Mar 20 05:00:01 GMT 2025] GET [Thu Mar 20 05:00:01 GMT 2025] url='https://api.github.com/repos/acmesh-official/acme.sh/git/refs/heads/master' [Thu Mar 20 05:00:01 GMT 2025] timeout=30 [Thu Mar 20 05:00:02 GMT 2025] _CURL='curl --silent --dump-header /root/.acme.sh/http.header -L -g --connect-timeout 30' [Thu Mar 20 05:00:02 GMT 2025] ret='0' [Thu Mar 20 05:00:02 GMT 2025] Already up to date! [Thu Mar 20 05:00:02 GMT 2025] Upgrade successful! [Thu Mar 20 05:00:02 GMT 2025] Using config home: /root/.acme.sh [Thu Mar 20 05:00:02 GMT 2025] ACME_DIRECTORY='https://acme-v02.api.letsencrypt.org/directory' [Thu Mar 20 05:00:02 GMT 2025] _ACME_SERVER_HOST='acme-v02.api.letsencrypt.org' [Thu Mar 20 05:00:02 GMT 2025] _ACME_SERVER_PATH='directory' [Thu Mar 20 05:00:02 GMT 2025] Automatically upgraded to: 3.1.0 [Thu Mar 20 05:00:02 GMT 2025] Using config home: /root/.acme.sh [Thu Mar 20 05:00:02 GMT 2025] ACME_DIRECTORY='https://acme-v02.api.letsencrypt.org/directory' [Thu Mar 20 05:00:02 GMT 2025] _ACME_SERVER_HOST='acme-v02.api.letsencrypt.org' [Thu Mar 20 05:00:02 GMT 2025] _ACME_SERVER_PATH='directory' [Thu Mar 20 05:00:02 GMT 2025] _stopRenewOnError [Thu Mar 20 05:00:02 GMT 2025] _server [Thu Mar 20 05:00:02 GMT 2025] _set_level='2' [Thu Mar 20 05:00:02 GMT 2025] di='/root/.acme.sh/domain-name-removed/' [Thu Mar 20 05:00:02 GMT 2025] d='domain-name-removed' [Thu Mar 20 05:00:02 GMT 2025] _renewServer [Thu Mar 20 05:00:02 GMT 2025] Using config home: /root/.acme.sh [Thu Mar 20 05:00:02 GMT 2025] ACME_DIRECTORY='https://acme-v02.api.letsencrypt.org/directory' [Thu Mar 20 05:00:02 GMT 2025] _ACME_SERVER_HOST='acme-v02.api.letsencrypt.org' [Thu Mar 20 05:00:02 GMT 2025] _ACME_SERVER_PATH='directory' [Thu Mar 20 05:00:02 GMT 2025] DOMAIN_PATH='/root/.acme.sh/domain-name-removed' [Thu Mar 20 05:00:02 GMT 2025] Renewing: 'domain-name-removed' [Thu Mar 20 05:00:02 GMT 2025] Le_API='https://acme-v02.api.letsencrypt.org/directory' [Thu Mar 20 05:00:02 GMT 2025] Renewing using Le_API=https://acme-v02.api.letsencrypt.org/directory [Thu Mar 20 05:00:02 GMT 2025] initpath again. [Thu Mar 20 05:00:02 GMT 2025] Using config home: /root/.acme.sh [Thu Mar 20 05:00:02 GMT 2025] ACME_DIRECTORY='https://acme-v02.api.letsencrypt.org/directory' [Thu Mar 20 05:00:02 GMT 2025] _ACME_SERVER_HOST='acme-v02.api.letsencrypt.org' [Thu Mar 20 05:00:02 GMT 2025] _ACME_SERVER_PATH='directory' [Thu Mar 20 05:00:02 GMT 2025] Skipping. Next renewal time is: 2025-05-17T05:00:09Z [Thu Mar 20 05:00:02 GMT 2025] Add '--force' to force renewal. [Thu Mar 20 05:00:02 GMT 2025] Return code: 2 [Thu Mar 20 05:00:02 GMT 2025] Skipped domain-name-removed [Thu Mar 20 05:00:02 GMT 2025] _error_level='3' [Thu Mar 20 05:00:02 GMT 2025] _set_level='2' [Thu Mar 20 05:00:02 GMT 2025] ===End cron===
There are no certificates that need to be renewed. So, the initial issue of certs not being renewed seems to be resolved now. Try to restart the web server (apache or nginx) and also dovecot and postfix to see if that solves the issue.
Thanks guys, these are all more positive than the errors before, I think we are sorted. Thanks for your help!