From 34982bd4c8cc2ab004c585ee1cec889c56ec1a88 Mon Sep 17 00:00:00 2001 From: tb Date: Wed, 10 May 2023 07:34:57 +0000 Subject: [PATCH] Add a hint on using letsencrypt-staging for testing While florian rightly points out that this is likely to be overlooked, it may help someone. Also doesn't affect the adjust-config-with-sed-ability of the example file after input by a few. no objection florian ok espie millert --- etc/examples/acme-client.conf | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/etc/examples/acme-client.conf b/etc/examples/acme-client.conf index 31dd96f0088..842f2f3d814 100644 --- a/etc/examples/acme-client.conf +++ b/etc/examples/acme-client.conf @@ -1,5 +1,5 @@ # -# $OpenBSD: acme-client.conf,v 1.4 2020/09/17 09:13:06 florian Exp $ +# $OpenBSD: acme-client.conf,v 1.5 2023/05/10 07:34:57 tb Exp $ # authority letsencrypt { api url "https://acme-v02.api.letsencrypt.org/directory" @@ -27,5 +27,7 @@ domain example.com { alternative names { secure.example.com } domain key "/etc/ssl/private/example.com.key" domain full chain certificate "/etc/ssl/example.com.fullchain.pem" + # Test with the staging server to avoid aggressive rate-limiting. + #sign with letsencrypt-staging sign with letsencrypt } -- 2.20.1