forked from TrueCloudLab/lego
README: Change staging URL example for ACME v2. (#592)
This commit is contained in:
parent
e0d512138c
commit
8c82824a83
1 changed files with 2 additions and 2 deletions
|
@ -180,7 +180,7 @@ lego --email="foo@bar.com" --csr=/path/to/csr.pem run
|
|||
lego defaults to communicating with the production Let's Encrypt ACME server. If you'd like to test something without issuing real certificates, consider using the staging endpoint instead:
|
||||
|
||||
```bash
|
||||
lego --server=https://acme-staging.api.letsencrypt.org/directory …
|
||||
lego --server=https://acme-staging-v02.api.letsencrypt.org/directory …
|
||||
```
|
||||
|
||||
## DNS Challenge API Details
|
||||
|
@ -296,4 +296,4 @@ fmt.Printf("%#v\n", certificates)
|
|||
|
||||
## ACME v1
|
||||
|
||||
lego introduced support for ACME v2 in [v1.0.0](https://github.com/xenolf/lego/releases/tag/v1.0.0), if you still need to utilize ACME v1, you can do so by using the [v0.5.0](https://github.com/xenolf/lego/releases/tag/v0.5.0) version.
|
||||
lego introduced support for ACME v2 in [v1.0.0](https://github.com/xenolf/lego/releases/tag/v1.0.0), if you still need to utilize ACME v1, you can do so by using the [v0.5.0](https://github.com/xenolf/lego/releases/tag/v0.5.0) version.
|
||||
|
|
Loading…
Reference in a new issue