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-3280580@2rosenthals.com>
 <list-3280786@2rosenthals.com>
Organization: Massimo S.
Message-ID: <00b6c905-7806-889d-c701-3271adfad660@ecomstation.it>
Date: Tue, 4 Aug 2026 17:08:02 +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-3280786@2rosenthals.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: it
Content-Transfer-Encoding: 7bit



Il 04/08/2026 17:01, Massimo S. ha scritto:
> 
> 
> Il 04/08/2026 16:00, Massimo S. ha scritto:
>>
>>
>> Il 04/08/2026 15:01, Massimo S. ha scritto:
>>>
>>>
>>> Il 09/06/2026 10:50, Paul Smedley ha scritto:
>>>> Hi Max,
>>>>
>>>> On 9/6/26 17:36, Massimo S. wrote:
>>>>> Hi all,
>>>>>
>>>>> for a LE certificate renewal if i use uacme 1.2.4 i get this:
>>>>>
>>>>> uacme: version 1.2.4 starting on Tue, 09 Jun 2026 09:34:39
>>>>> ...
>>>>> ...
>>>>> uacme: fetching directory at https://acme-v02.api.letsencrypt.org/directory
>>>>> uacme: curl_get: GET https://acme-v02.api.letsencrypt.org/directory failed: Problem with the SSL CA cert 
>>>>> (path? access rights?)
>>>>> uacme: curl_get: waiting 5 seconds before retrying
>>>>> uacme: curl_get: GET https://acme-v02.api.letsencrypt.org/directory failed: Problem with the SSL CA cert 
>>>>> (path? access rights?)
>>>>> uacme: curl_get: waiting 5 seconds before retrying
>>>>> uacme: curl_get: GET https://acme-v02.api.letsencrypt.org/directory failed: Problem with the SSL CA cert 
>>>>> (path? access rights?)
>>>>> uacme: curl_get: waiting 5 seconds before retrying
>>>>> uacme: acme_get: curl_get failed
>>>>> uacme: failed to fetch directory at https://acme-v02.api.letsencrypt.org/directory
>>>>>
>>>>> while it works if i use uacme 1.0.9
>>>>>
>>>>> i've seen that i'm using 1.0.9 on all VMs, i forgot about that..
>>>>>
>>>>> any suggestion?
>>>>> any help?
>>>>>
>>>> My guess would be the ca-certs rpm package is either missing or out of date.
>>>>
>>>> Cheers,
>>>>
>>>> Paul
>>>
>>> Hi Paul,
>>>
>>> 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..."?
>>>
>>> Anyway are the biggest changes from 1.0.19 to 1.2.4?
>>> Is it possible that 1.0.19 is OS/2 paths friendly, like 1.2.4 or 1.8.1 are not?
>>>
>>> massimo
>>
>> I add, Copilot chatbot say that uacme 1.2.4 or 1.8.1 fails if started by cron
>> since it do not find these DLLs:
>>
>> libssl.dll
>> libcrypto.dll
>> libcurl.dll
>>
>> But i don't have any of these DLLs in the entire VM file systems
>>
>> massimo
> 
> i add Copilot say that uacme 1.0.19 works correctly since it do
> not use libcurl
> 
> and it say also that 1.2.4 or 1.8.1 are not compiled correctly to run under OS/2
> 
> massimo

i'm beninng to believe that uacme portings after 1.0.19 are only lightly tested
and only on development machines that have all the libraries and development stuff
and surely not tested on a production VM

massimo