From users-return-118298-archive-asf-public=cust-asf.ponee.io@httpd.apache.org Tue Dec 25 18:08:00 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 2D20C180645 for ; Tue, 25 Dec 2018 18:07:59 +0100 (CET) Received: (qmail 31698 invoked by uid 500); 25 Dec 2018 17:07:53 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 31688 invoked by uid 99); 25 Dec 2018 17:07:53 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Dec 2018 17:07:53 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 5DADACCDE1 for ; Tue, 25 Dec 2018 17:07:53 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.199 X-Spam-Level: X-Spam-Status: No, score=0.199 tagged_above=-999 required=6.31 tests=[DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=jwmhosting.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id SsEZqAcmukSn for ; Tue, 25 Dec 2018 17:07:49 +0000 (UTC) Received: from mx3.jwmhosting.com (jwmhosting.com [64.34.196.231]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 3ABB961066 for ; Tue, 25 Dec 2018 17:07:49 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit DKIM-Signature: a=rsa-sha256; b=ul2790FUHAtUYZG+Tw2Y65CyaH46Vd7gOvez/lthlte9ZdajBFgh48ExxmwrPPoM2xvps4FsLJDCYNc9NBrR8tasTBGzLlfeIJcocxwDeNvSPw5UpD79nf7vz57XS4U49UtgC77kN1LWsal+4GM+CKV/DxEIdEIVQDrjxPWSXAI=; s=primary; c=relaxed/relaxed; d=jwmhosting.com; v=1; bh=XN7reTo1rt1YyHmv5+/PbB1l+cW+byD2u7JFpUKSgc0=; h=Message-ID:Date:Subject:From:To:MIME-Version:Content-Type; X-Processor-Root: true X-Processor-Authorized-Outbound: true X_JWMH_OUTBOUND: true X_JWMH_FLAG: $label3 X_JWMH_TGTFOLDER: Apache Forums.httpd Users X-Processor-Transport: true X-UserIsAuth: true X-MIME-Autoconverted: from 8bit to quoted-printable by Apache JAMES Received: from cpe-66-68-42-68.austin.res.rr.com (EHLO [192.168.0.202]) ([66.68.42.68]) by jwmhosting.com (JAMES SMTP Server ) with ESMTPA ID 1010180743 for ; Tue, 25 Dec 2018 11:07:42 -0600 (CST) To: users@httpd.apache.org References: <87013c07-f871-6945-1b6d-02c1b2921bf1@malcolms.com> <7a2b5469-4be9-2738-bb97-20aa8e474368@malcolms.com> From: Jerry Malcolm Message-ID: <241c9f86-7a28-4490-1c91-38200fd0403b@malcolms.com> Date: Tue, 25 Dec 2018 11:07:40 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3 In-Reply-To: Content-Language: en-US Subject: Re: [users@httpd] Re: acme-challenge folder exists but 404 contents On 12/25/2018 9:14 AM, Jonesy wrote: > On Tue, 25 Dec 2018 00:49:41 -0600, Jerry Malcolm wrote: >> --------------5C1A8A0DD708D3B6F6BE8489 >> Content-Type: text/plain; charset=utf-8; format=flowed >> Content-Transfer-Encoding: 8bit >> >> Update... I finally went back to my Sept conf and vhosts files. With the >> old configuration files, acme-challenge folder became available again. >> So I was able to get my certs refreshed, and I then restored the current >> conf files.  That at least tells me it's something in the conf files. >> But I really don't want to make this my official process every three >> months when I refresh the certs. I guess I'll start with an A-B >> comparison of the conf files.  But the only real significant change I >> can remember in the last three months was enabling http 2.0.  Doesn't >> seem to me that anything in that area of config would be locking out >> folders with certain names (??).  In any case, I can brute-force this >> and back out changes one by one.  But if any of you have a hint as to >> what could be happening causing one specifically-named folder to be >> blocked (or a way to dig deeper into logs to figure it out), it'll save >> me a lot of time and effort. >> >> Thanks. >> >> Jerry >> >> >> On 12/24/2018 11:18 PM, Jerry Malcolm wrote: >>> I have an apache install that has been up and running for months.  I >>> use LetEncrypt for certificates.  I went to renew all of my >>> certificates using an automated script that worked fine 3 months ago >>> on the last refresh.  It failed on every domain saying the challenge >>> file was not found.  I put a test.html file in >>> /.well-known/acme-challenge folder, and tried to access it with a >>> browser, and it gave me a 404.  After moving the test.html file around >>> into other folders, it was found correctly in every folder except >>> acme-challenge.  I even renamed acme-challenge to acme-challenge1 and >>> acme1challenge, and test.html was found in folders by those names. >>> Renamed it back to acme-challenge and I'm again getting 404.  I have >>> about 15 virtual hosts defined.  Exact same situation in every virtual >>> host  The folder specifically named "acme-challenge" is somehow now >>> being blocked or hidden by apache. >>> >>> I'm using WAMP 3.1.3 (Apache 2.4.33).  The only .htaccess file in the >>> entire wamp tree is in the php folder, and I'm not using php.  I'd say >>> I haven't made any changes that would cause this problem since the >>> last time I refreshed certificates.  But I guess I did 'something'. >>> But I'm clueless. >>> >>> One thing I did notice.... In the browser, if I look for a >>> non-existent file in any other folder, I get one 404 line saying the >>> requested file was not found on the server.  Fine.  But when I look >>> for that same non-existent file in the /.well-known/acme-challenge >>> folder, I get that same line.  But I also get another line I haven't >>> seen before that says: >>> >>> Additionally, a 404 Not Found error was encountered while trying to >>> use an ErrorDocument to handle the request. >>> >>> So not only can't find the file, it can't find a file to tell me it >>> can't find the file... (???). But this line ONLY appears when trying >>> to get a file from that one specific directory named 'acme-challenge'. >>> >>> Help.... certs have expired.... >>> >>> Thanks. >>> >>> Jerry > Well, just from the data you've shown, your _only_ failing > directory (.../.well-known/acme-challenge/) jumps out as the > only example in your testing that has a hyphenated directory name. > > Maybe a red herring..... > Jonesy I had tried /.well-known/acme-challenge1, and it worked.  But even if it was a hyphen, assuming there is no .htaccess file, is there something in the configuration that would say to hide all directories with hyphens? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org