From 751d836746ec6ca34e4c04bf8fd3cf0c67c5cef5 Mon Sep 17 00:00:00 2001 From: ohemorange Date: Tue, 21 Apr 2020 12:47:59 -0700 Subject: [PATCH] Update using.rst to accurately describe acmev2 behavior (#7924) Fixes #7268 I removed the reference to automatically selecting which ACME protocol we use, since at some point we'll want to rip out the non-spec-compliant ACMEv1 code. --- certbot/docs/using.rst | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/certbot/docs/using.rst b/certbot/docs/using.rst index 1d8d54d3a..0a0b6d1a2 100644 --- a/certbot/docs/using.rst +++ b/certbot/docs/using.rst @@ -846,17 +846,15 @@ Example usage for DNS-01 (Cloudflare API v4) (for example purposes only, do not Changing the ACME Server ======================== -By default, Certbot uses Let's Encrypt's initial production server at -https://acme-v01.api.letsencrypt.org/. You can tell Certbot to use a +By default, Certbot uses Let's Encrypt's production server at +https://acme-v02.api.letsencrypt.org/. You can tell Certbot to use a different CA by providing ``--server`` on the command line or in a :ref:`configuration file ` with the URL of the server's ACME directory. For example, if you would like to use Let's Encrypt's -new ACMEv2 server, you would add ``--server -https://acme-v02.api.letsencrypt.org/directory`` to the command line. -Certbot will automatically select which version of the ACME protocol to -use based on the contents served at the provided URL. +staging server, you would add ``--server +https://acme-staging-v02.api.letsencrypt.org/directory`` to the command line. -If you use ``--server`` to specify an ACME CA that implements a newer +If you use ``--server`` to specify an ACME CA that implements the standardized version of the spec, you may be able to obtain a certificate for a wildcard domain. Some CAs (such as Let's Encrypt) require that domain validation for wildcard domains must be done through modifications to