Mailing List ecs-isp@2rosenthals.com Archived Message #1375

From: "Massimo S." <ecs-isp@2rosenthals.com> Full Headers
Undecoded message
Subject: Re: [eCS-ISP] uacme 1.2.4 issue - update
Date: Wed, 5 Aug 2026 16:23:31 +0200
To: eCS ISP Mailing List <ecs-isp@2rosenthals.com>

Il 05/08/2026 10:57, Massimo S. ha scritto:


Il 05/08/2026 01:13, Peter Moylan ha scritto:
On 05/08/26 07:47, Paul Smedley wrote:
On 4/8/26 22:31, Massimo S. wrote:
Il 09/06/2026 10:50, Paul Smedley ha scritto:

My guess would be the ca-certs rpm package is either missing or out
of date.

this is what i believed too..
i've downloaded the new cacert.pem but this doesnt' help.

Maybe uacme starting from version 1.2.4 (like 1.8.1 by Andrey too) has
some issue with /2 paths.

cp: impossibile eseguire stat di
'c:etcssluacme/www.myfakedomain.com/cert.pem': No such file or directory

What's that "C:etcssluacm..."?

My 'guess' would be a shell issue.  Is this only when your scheduler
starts uacme? Perhaps the schedule is overriding the statemetnts in
config.sys that set *SHELL* to sh.exe

That sounds like a Unixism. My config.sys has
       SET OS2_SHELL=C:\OS2\CMD.EXE

I don't use cron, so I don't know whether cron overrides that.

I've just realised that my updating script explicitly specifies the shell:
      Path and file name: cmd.exe
      Parameters:    /C issue_pmoylan.org.cmd

Copilot say that UACME 1.0.19 have an its own https client that do direct
requests to LE's server, while later versions use external libcurl.
(i don't have any libcurl on the entire VM, but this do not explain
why the renewal works if started manually, damn..)

This stuff about the internal https client can only be confirmed by Paul
or Andrey that did the portings.
I've written to Andrey and also to Nicola Di Lieto (the developer
of UACME), but i still have no answers, we are in august, ppl are on holidays..

Nicola Di Lieto answered to the email, NO, UACME 1.0.19 don't have an
internal https service/code, it have allways used libcurl.

So who knows if libcurl has been statically linked into 1.0.19,
but not in the newer versions?

If so a libcurl statically linked build should fix the cron issue.

massimo

Subscribe: Feed, Digest, Index.
Unsubscribe
Mail to ListMaster