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