On 10/12/24 10:54, Peter Moylan wrote:

D:\APPS\UACME]uacme -v -h uacme-hook.cmd issue pmoylan.org
www.pmoylan.org mail.pmoylan.org
uacme: version 1.2.4 starting on Tue, 10 Dec 2024 10:06:27
uacme: loading key from /@unixroot/etc/ssl/uacme/private/key.pem
uacme: loading key from
/@unixroot/etc/ssl/uacme/private/pmoylan.org/key.pem
uacme: checking existence and expiration of
/@unixroot/etc/ssl/uacme/pmoylan.org
/cert.pem
uacme: /@unixroot/etc/ssl/uacme/pmoylan.org/cert.pem does not exist
uacme: fetching directory at https://acme-v02.api.letsencrypt.org/directory
A non-recoverable error occurred.  The process ended.

Confirmed: uacme-hook.cmd did not start execution before this crash happened.

I tried backlevelling uacme.exe to version 1.0.19, but it failed a different way: failed to access /etc/ssl/uacme. I guess that version didn't translate slashes to backslashes. But that gave me a new idea: maybe uacme can't handle uacme.exe (and its scripts) being on drive D:, but %ETC being on drive C:. So I moved all the executables to C:\uacme. (And went back to version 1.2.4.)

Now the symptoms have changed:
{14}[c:\uacme] issue_pmoylan.org
uacme -v -h uacme-hook.cmd issue pmoylan.org www.pmoylan.org mail.pmoylan.org
uacme.exe: version 1.2.4 starting on Tue, 10 Dec 2024 14:11:04
uacme.exe: loading key from /@unixroot/etc/ssl/uacme/private/key.pem
uacme.exe: loading key from /@unixroot/etc/ssl/uacme/private/pmoylan.org/key.pem

uacme.exe: checking existence and expiration of /@unixroot/etc/ssl/uacme/pmoylan
.org/cert.pem
uacme.exe: /@unixroot/etc/ssl/uacme/pmoylan.org/cert.pem does not exist
uacme.exe: fetching directory at https://acme-v02.api.letsencrypt.org/directory

No crash now. But uacme-hook still hasn't been invoked, so no challenge and no certificate.

I guess that's progress.