From owner-freebsd-questions@freebsd.org Fri Jan 18 23:58:16 2019 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4CFB1487FCC for ; Fri, 18 Jan 2019 23:58:15 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 87CE182B1B for ; Fri, 18 Jan 2019 23:58:15 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id D27E327A60 for ; Fri, 18 Jan 2019 18:58:13 -0500 (EST) Received: from web6 ([10.202.2.216]) by compute7.internal (MEProxy); Fri, 18 Jan 2019 18:58:13 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=skunkwerks.at; h=message-id:from:to:mime-version:content-transfer-encoding :content-type:subject:in-reply-to:date:references; s=fm1; bh=Dwq 1vqD0tvcTXkirkGjhdewiVR/6kKYUZYC7qEo4uIA=; b=R7MfnyyuKTRwz11hhHx f+IJpVcFfO3wROzZqYDPliKIjhXRMzHI7KGNeC1X/zhKfiXo6Rw6ZbBtOOXvt0Zk VakpOnOptlMr56ysSApHJpYN5bFsE8iVKxQ87eRebeJ59pNrP1om1LDJAPbYA9Dv db4jJgxR1btGM0E+cOwOluj4ofUzRoyXw3nwh1cHNgWxuhCDPhK+We3Q82e6h5Tp PB0ubZ2wzH9Q10xWHZVmLuXRXf8GRA5VLpNDJUtsYvRtc8IxcPP7eriHoYlAPOcI mOj6Ux86DuI3KKrgOC9GN1gSdPoDxu0iuhtp/Ba3NGM10SYlOAIjE7XGqE2rvOP4 pdw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=Dwq1vqD0tvcTXkirkGjhdewiVR/6kKYUZYC7qEo4u IA=; b=nqn/+fUhvC80ChroMew7DerziDDNfOgo4mWqL1ZzlodilLb4v+WY5U1XZ LufFj+y156AlCAUnD4qETHl61NWv4H4Slw4aJxUjDvuFjOSe5lfDVevAZisiCYsB mTeTlSUoYdpc13vFgvhbdf3VBrwC2e13L31x7r34fQXihMdMVyG1q36rlVp39EZc Qr9aKcmEu+cevy+XFqoRXOX9+BpN1fXJbaU42i588Ls2ZSrQ9GhOKkPmfpSRgIJ/ L/8XHrk5xOoEfelsvvlrjMgGOCXlZVn9fWBYAqKAnnQUM66J3svyY8CvdcXHSs2I vrfb4Nookqn/2W/o1J14Mx5RQcnaA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrhedugdduhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucgoteefjeefqddtgeculdehtddmnecujfgurhepkffhvfgggfgtoffujgfffhesth ejredtredtjeenucfhrhhomhepffgrvhgvucevohhtthhlvghhuhgsvghruceouggthhes shhkuhhnkhifvghrkhhsrdgrtheqnecuffhomhgrihhnpehgihhthhhusgdrtghomhdpvg igrghmphhlvgdrohhrghenucfrrghrrghmpehmrghilhhfrhhomhepuggthhesshhkuhhn khifvghrkhhsrdgrthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 4257B4140; Fri, 18 Jan 2019 18:58:13 -0500 (EST) Message-Id: <1547855893.2361655.1638429920.0BB55387@webmail.messagingengine.com> From: Dave Cottlehuber To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-36e4bfd3 Subject: Re: certbot: OCSP check failed In-Reply-To: <6ec8f257-3ca0-38ba-2e07-aaf8f835ad63@FreeBSD.org> Date: Sat, 19 Jan 2019 00:58:13 +0100 References: <31b9ce5f-4134-ee49-47bf-10af7244d21e@ifdnrg.com> <6ec8f257-3ca0-38ba-2e07-aaf8f835ad63@FreeBSD.org> X-Rspamd-Queue-Id: 87CE182B1B X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.985,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jan 2019 23:58:16 -0000 On Fri, 18 Jan 2019, at 01:23, Matthew Seaman wrote: > On 17/01/2019 18:05, Paul Macdonald via freebsd-questions wrote: > > i'm seeing this for all certs on several boxes ( that are online!) > > > > mostly posting in case someone knows who to notify/where to check > > (@Matthew?) > > > > OCSP check failed for /usr/local/etc/letsencrypt/live//cert.pem > > (are we offline?) > > OCSP checking relies on making a web query to one of the CA's servers. > It could be that site was temporarily offline or somehow inaccessible to > you. That's where I'd start looking to debug this. OCSP is (at least in my circle of acquaintances) notoriously flakey in providing updates. I've switched to twice weekly updates with a wrapper around the checks to re-try if upstream cert provider is incapable of serving us. You can use this to check your OCSP validity: curl -4sSLo /dev/null --cert-status https://example.org/ I have found https://github.com/h2o/h2o/blob/master/share/h2o/fetch-ocsp-response (www/h2o is in ports) very useful to handle the fetching, it may suit your needs if your current tools do not. A+ Dave