From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTP id 11131044 for ecs-isp@2rosenthals.com; Tue, 22 Oct 2024 18:05:49 -0400 Received: from secmgr-va.2rosenthals.com ([50.73.8.217]:59846 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1t3N0W-000000004vz-1MKU for ecs-isp@2rosenthals.com; Tue, 22 Oct 2024 18:05:40 -0400 Received: from mta-201b.earthlink-vadesecure.net ([51.81.229.181]:59421 helo=mta-201a.earthlink-vadesecure.net) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.97.1) (envelope-from ) id 1t3N0M-000000004sh-1kjC for ecs-isp@2rosenthals.com; Tue, 22 Oct 2024 18:05:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=wu05FzuRwaH2Xfk77B1IJegmEDk+m8sGpJ95bS oJP/E=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-unsubscribe-post: list-subscribe:list-post:list-owner:list-archive; q=dns/txt; s=dk12062016; t=1729634729; x=1730239529; b=I/GUNcQm94eTuMkRZj9RgE8IAK3 w7EHo4ZMB7zql5Aeu+/s1GrCXfbU8oyEjJvBsYC1ErBpVRy6mWGEq8V0VjA7+5BeMBPEx/K mXBWBsw2seYenyYye1W1nWgtKi9AXNFZaC9s0EbU+WAwAIMtw6zG1HsqHFftHI+sU1SMD7B g0f7Z+uAC94FG+VVurYyOqc8dfg2vmI5D+bjA/zbf79MFaJywPMA8+9q1t7PEug2Y0agaUY UcdDBsI2xO2ZZJSge2CkHe4reJwtLmRfjzfF72jxfPw4IEvGPUHIMeSgGnB/KWfOikFVTeQ 0HSFkDEd0WgQk8xU+HP1zMqK4Yjno1A== Received: from slamain ([172.58.117.14]) by vsel2nmtao01p.internal.vadesecure.com with ngmta id 88b60294-1800e59f5975e09c; Tue, 22 Oct 2024 22:05:29 +0000 Message-ID: <67181cf2.24.mr2ice.fgrirsq@earthlink.net> Date: Tue, 22 Oct 2024 13:45:22 -0800 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] uacme 1.2.4 and path issue X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 10/22/24 at 05:24 PM, "Massimo S." said: Hi Massimo, >uacme -v issue www.mydomain.it -c c:/mptn/etc/ssl/uacme -h >hook_www_mydomain_it.cmd >and i got uacme: c:/mptn/etc/ssl/uacme/private/www.mydomain.it/key.pem not found * This is normal. Uacme is checking if the domain private key exists, so it knows what to do next. uacme: checking existence and expiration of c:/mptn/etc/ssl/uacme/www.mydomain.it/cert.pem uacme: c:/mptn/etc/ssl/uacme/www.mydomain.it/cert.pem does not exist ** uacme: fetching directory at https://acme-v02.api.letsencrypt.org/directory This is normal. Uacme is checking if the cert exists so it knows what to do next. uacme: curl_get: GET https://acme-v02.api.letsencrypt.org/directory failed: SSL peer certificate or SSH remote key was not OK uacme: curl_get: waiting 5 seconds before retrying I've seen this recently too. It appears that Let's Encrypt is somewhat overloaded recently. There's nothing you can do other than retry until it works. It might be instructive to open https://acme-v02.api.letsencrypt.org/directory in a browser. The file contains a list of the actions that that LE supports. >while if i don't delete key.pem and cert.pem >i get All normal, best I can tell >while if i delete only cert.pem >i get the same Again. All normal other than the LE busy issue. >so i don't understand if uacme 1.2.4 is working correctly or not :-( uacme is working correctly. The problem is wih the LE server which hopefully will not persist. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------