From 7d8573af12051abbb9a1c4eae592914899040d5c Mon Sep 17 00:00:00 2001
From: Nick <nick@kousu.ca>
Date: Thu, 1 Apr 2021 16:49:55 -0400
Subject: [PATCH] Update staging.md to use ACMEv2 server (closes #812)

letsencrypt is phasing out the v1 server:

```
  + ERROR: An error occurred while sending get-request to https://acme-staging.api.letsencrypt.org/directory (Status 403)

Details:
HTTP/2 403
server: nginx
date: Thu, 01 Apr 2021 20:48:17 GMT
content-type: application/problem+json
content-length: 189
etag: "600b3710-bd"

{
  "type": "urn:acme:error:serverInternal",
  "detail": "ACMEv1 Brownout in Progress. ACMEv1 will fully turn off on June 1, 2021. Check https://letsencrypt.status.io/ for more details."
}

```
---
 docs/staging.md | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/docs/staging.md b/docs/staging.md
index bae8903..6e6a84b 100644
--- a/docs/staging.md
+++ b/docs/staging.md
@@ -8,10 +8,5 @@ you will quickly hit these limits and find yourself locked out.
 To avoid this, please set the CA property to the Let’s Encrypt staging server URL in your config file:
 
 ```bash
-CA="https://acme-staging.api.letsencrypt.org/directory"
+CA="https://acme-staging-v02.api.letsencrypt.org/directory"
 ```
-
-# ACMEv2 staging
-
-You can use `CA="https://acme-staging-v02.api.letsencrypt.org/directory"` to test dehydrated with
-the ACMEv2 staging endpoint.
-- 
2.47.3