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 11075162 for ecs-isp@2rosenthals.com; Fri, 11 Oct 2024 20:42:20 -0400 Received: from secmgr-va.randr ([192.168.200.201]:46244 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.97.1) (envelope-from ) id 1szQD5-000000003Pl-1e4G for ecs-isp@2rosenthals.com; Fri, 11 Oct 2024 20:42:19 -0400 Received: from mta-102a.earthlink-vadesecure.net ([51.81.61.66]:40543) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.97.1) (envelope-from ) id 1szQD4-000000007IP-0Ehz for ecs-isp@2rosenthals.com; Fri, 11 Oct 2024 20:42:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=vvt/JkCRLEhXy9WZLn1PtBSEn11WgHUR77qEDK zdZ9I=; 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=1728693737; x=1729298537; b=rhTolaPC7TZVbKMMZNaDcLBK++Z fJfAk/6rmaiJ1e5d9Z5pHcJbEH/Yo7K0rb/VkvLhjz9vSIfGE4arn1IcmYZ1+QhFix43nl7 uQU0L6nllcG/FFatyPbnkX66QUd9CXZOTtuVokWK8ZCwYQUtIKEOOIze4PPTCu0STy4BI+V aTpsd4UGVLjg9pYcIcY2CVeIne2pC50CEmKzUIlR75f/tjH7iizu1ix5pn7dHQ/bB2bCZv/ A971O2+YpQ38M5olEHPNy6zuls5vmNI6ySDKpOgwOY75zy03tPMH5OK9Zg3SJvpFJlvn/4R WLl1QAYPVZ6nIXF+RA2WoAYCx+P0w5Q== Received: from slamain ([172.58.117.14]) by vsel1nmtao02p.internal.vadesecure.com with ngmta id c631d145-17fd8dcb84166159; Sat, 12 Oct 2024 00:42:17 +0000 Message-ID: <6709ca61.6.mr2ice.fgrirsq@earthlink.net> Date: Fri, 11 Oct 2024 17:01:21 -0800 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] HTTPS-Misery (for Steven) X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 10/12/24 at 01:40 AM, "Massimo S." said: Hi Massimo, >i still don't understand this No problem. This stuff was all new to us at one time. >2024/10/12-01:33:15 hook_webmail started at 2024/10/12-01:33:15 >2024/10/12-01:33:15 method is begin >2024/10/12-01:33:15 type is http-01 >2024/10/12-01:33:15 ident is webmail.mydomain.it >2024/10/12-01:33:15 token is OQg2xEXcj39j6brHDmIDwj5V5mYY1_DOvU5DRDOnPh4 Not so good. Notice that the hook did not create the token file. You log is missing a line like: 2024/08/25-19:58:36 Creating D:\www\docs\mbopinion\.well-known\acme-challenge\pyyk1CI7afsiXskFrCC8RGVYS9t3qOvvQkRrL07rGaE which reports that the token file has been successfully created. My guess is you broke the script when you did your edits. If think I see what you did wrong. You set docroot with docroot = 'X:\apache\htdocs\mywebsite\.well-known\acme-challenge' You should have used docroot = 'X:\apache\htdocs\mywebsite' docroot as the name implies is the name of the document root directory, not the challenge directory. The challenge directory name is set by uacme-hook.cmd:88 challengeDir = MakePath( docroot, '.well-known\acme-challenge') I'm pretty sure the script reported that it could not access X:\apache\htdocs\mywebsite\.well-known\acme-challenge\.well-known\acme-challenge and died and you ignored the error message or it scrolled by too fast for you to read. Run uacme with the -h and -v options and capture stdout and stderr to a file: uacme -v -h uacme-hook.cmd issue webmail.mydomain.it >out.log 2>&1 Out.log should contain the error message you missed. >i still find the acme-challenge dir empty This is normal. The only reason the challenge directory will not be empty is if uacme or the hook script crashes in such a way that the token file is not deleted. Your issue is a bit different. The token file never got created because you pointed challengeDir at a non-existant directory and the script died. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------