From: "Steven Levine" <ecs-isp@2rosenthals.com>
Message-ID: <6a2b4833.17.mr2ice.fgrirsq@earthlink.net>
Date: Thu, 11 Jun 2026 16:43:47 -0700
To: "eCS ISP Mailing List" <ecs-isp@2rosenthals.com>
In-Reply-To: <list-2750010@2rosenthals.com>
Subject: Re: [eCS-ISP] uacme 1.2.4 issue

In <list-2750010@2rosenthals.com>, on 06/11/26
   at 09:33 AM, "Massimo S." <ecs-isp@2rosenthals.com> said:

Hi,

Your answers have me a bit confused.

>there are also other posts to this ML

I recall them.  However, I suspect enough has changed that it's best to
start over and collect fresh data.

>on MTA2 was happening this, each scheduled renewal of the mta(popS) cert
>failed, so each time i had to start the script manually and it worked

If you want to continue to try to get 1.2.4 working on your setup, the
first order of business is the get it working from the command line.

>>    curl https://acme-v02.api.letsencrypt.org/directory
>no issues, with -o flag it save the same contents like wget does

This implies that there's something in your setup that is bothering
uacme.exe.  Both uacme and curl4 are using the same curl4 library.

>here buildlevel give out only this:
>unknown return code 3 from FileVerGetVersionStringFromFile
>File uacme_new.exe has no LAN component-style version string.

That's why I included the md5 hash.

>https://smedley.id.au/tmp/uacme-1.2.4-os2-20240817.zip

This is the most recent distro.  It's very unlikely that your binary
differs from what the rest of us are using.

If you want to continue trying to get 1.2.4 working, I need to see your
exact uacme command line.

Steven

-- 
----------------------------------------------------------------------
"Steven Levine" <steve53@earthlink.net>  Warp/DIY/BlueLion etc.
www.scoug.com www.arcanoae.com www.warpcave.com
----------------------------------------------------------------------