From owner-freebsd-questions@freebsd.org Tue May 23 12:30:34 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A07B8D79304 for ; Tue, 23 May 2017 12:30:34 +0000 (UTC) (envelope-from jim@mailman-hosting.com) Received: from maurice.jlkmail.com (maurice.jlkmail.com [23.111.151.218]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 76EF31195 for ; Tue, 23 May 2017 12:30:33 +0000 (UTC) (envelope-from jim@mailman-hosting.com) Received: from maurice.jlkmail.com (localhost [127.0.0.1]) by maurice.jlkmail.com (Postfix) with ESMTP id 2D427189045A for ; Tue, 23 May 2017 08:30:27 -0400 (EDT) Authentication-Results: maurice.jlkmail.com (amavisd-new); dkim=pass (1024-bit key) reason="pass (just generated, assumed good)" header.d=mailman-hosting.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= mailman-hosting.com; h=content-transfer-encoding :content-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:to:subject:subject; s=dkim; t=1495542621; x= 1496406622; bh=8IJZOx0h3m4Vfdvwu5qYCyzUcEhm0Yr0KrGTIJRKMBU=; b=F HiyVGexGwfD7VsHG0xve6CHmYCwEahxqxQz2FJyqSRtBl0slAN1nXz7hIhHnNc3o RTMe/Zxyc0YC48E3A27vZMnR7X6uW8zRT9VVr5eyJt5S2JCRT47ZkPRUeB+m2Y6R 91VaqfjDpBC0RsDeXb/kQFeApZB53PGk4b4dNiIQxU= X-Virus-Scanned: Debian amavisd-new at maurice.jlkmail.com X-Spam-Flag: NO X-Spam-Score: -0.999 X-Spam-Level: X-Spam-Status: No, score=-0.999 tagged_above=-9999 required=6.31 tests=[ALL_TRUSTED=-1, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from maurice.jlkmail.com ([127.0.0.1]) by maurice.jlkmail.com (maurice.jlkmail.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id eCMDYen_GQa6 for ; Tue, 23 May 2017 08:30:21 -0400 (EDT) Received: from [192.168.1.153] (static-70-104-198-154.nrflva.fios.verizon.net [70.104.198.154]) by maurice.jlkmail.com (Postfix) with ESMTPSA id 2BBDD1890449; Tue, 23 May 2017 08:30:21 -0400 (EDT) Subject: Re: Acme client not updating keys automatically To: freebsd-questions@freebsd.org, David Mehler References: From: Jim Ohlstein Message-ID: <186862bf-4b82-9ac2-dee4-4de476840f26@mailman-hosting.com> Date: Tue, 23 May 2017 08:30:20 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2017 12:30:34 -0000 Hello On 05/23/2017 08:23 AM, David Mehler wrote: > Hello, > > I've got a Freebsd 10.3 system running several ssl-enabled web > servers. I've got letsencrypt keys for all of them. I'm using > py27-certbot (am not stuck on it so if there's an alternative), and > have a cron job set to check keys and update them by doing a certbot > renew. > > I thought something was wrong when I kept getting key expirey notices > from letsencrypt, then I checked a site and got a key has expired > message. > > Suggestions welcome. Is it working from the command line manually? Any error message (certbot will log errors to a file - I think it's certbot.log)? Also, have you upgrade to the latest security/py-certbot? There was an issue after devel/py-configargparse was recently upgraded. -- Jim Ohlstein Professional Mailman Hosting https://mailman-hosting.com/