From: "Paul Smedley" Received: from vps.smedley.id.au ([23.238.44.164] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTP id 3291521 for ecs-isp@2rosenthals.com; Wed, 05 Aug 2026 15:16:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=smedley.id.au; s=default; t=1785956776; bh=kMxhoynaNrNm0Bzag+d10aIwHdowq1OfhFB0IRinr9A=; h=Date:Subject:To:References:From:In-Reply-To:From; b=pyTavh8zgWDJSv9jkOm2qSP/KALTg5appmyGIkhEH/aj089bNvDGQgbYFTJjYc1q2 NgdI5EIUQIUkahRcRMuvIn0WTOGtElcH+eusUlcAZ3uj+glx8MOzQnPkhHWfjumsQU T+opjmOhZpFqzpoDbun6FNo50MSkdkbbIVpWvbOo= Received: from [192.168.245.251] (smedley.org [45.249.117.21]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by vps.smedley.id.au (Postfix) with ESMTPSA id 145C3200F9 for ; Thu, 06 Aug 2026 04:36:15 +0930 (ACST) Message-ID: Date: Thu, 6 Aug 2026 04:36:13 +0930 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [eCS-ISP] uacme 1.2.4 issue - update To: eCS ISP Mailing List References: Content-Language: en-AU In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Max, On 5/8/26 23:53, Massimo S. wrote: > 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. > Sounds more like BEGINLIBPATH should fix your cron issue, ie your cron isn't respecting the system LIBPATH. Cheers, Paul