From: "Massimo S." <ecs-isp@2rosenthals.com>
Reply-To: ml@ecomstation.it
Subject: Re: [eCS-ISP] uacme 1.2.4 issue
To: eCS ISP Mailing List <ecs-isp@2rosenthals.com>
References: <list-2730016@2rosenthals.com> <list-2730036@2rosenthals.com>
 <list-3280432@2rosenthals.com> <list-3281855@2rosenthals.com>
 <list-3281996@2rosenthals.com>
Organization: Massimo S.
Message-ID: <6e399439-d97c-1cc5-14b7-db8cac0844ec@ecomstation.it>
Date: Wed, 5 Aug 2026 10:57:22 +0200
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; it-IT; rv:1.7.13) Gecko/20060424
 Thunderbird/1.0.8 Mnenhy/0.7.4.0
MIME-Version: 1.0
In-Reply-To: <list-3281996@2rosenthals.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: it
Content-Transfer-Encoding: 8bit



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..

About CRON maybe it ignore libpathstrict entry in the renewal script, maybe..
But i don't know how to avoid this situation.

massimo