Error: options.newRegUrl must be the a new registration url #10

Nieuw probleem

Ghost · 2018-05-10T11:10:05Z

Ghost reageerde

2018-05-10 11:10:05 +00:00

Hey there, thanks for the great lib.

I have things working end-to-end with the staging URL but I'm getting an error after switching to the production URL (https://acme-v02.api.letsencrypt.org/directory). I'm using the built in le-store-certbot and le-challenge-fs. Wondering if you can point me in the right direction.

cheers,
Brock

Hey there, thanks for the great lib. I have things working end-to-end with the staging URL but I'm getting an error after switching to the production URL (https://acme-v02.api.letsencrypt.org/directory). I'm using the built in `le-store-certbot` and `le-challenge-fs`. Wondering if you can point me in the right direction. cheers, Brock

coolaj86 reageerde

2018-05-10 15:48:38 +00:00

Eigenaar

Because Let's Encrypt v2 support is new and not compatible with Let's Encrypt v1, you must now specify either version: 'draft-11' (for Let's Encrypt v2) or version: 'v01' (for Let's Encrypt v1).

I'd like to see your configuration to better help you, but I'm pretty sure the error your getting is that either you didn't specify version: 'draft-11' or you have a typo in the version.

I probably still have a few incorrect or mismatched references in the documentation, so I'll double check on that.

Because Let's Encrypt v2 support is new and not compatible with Let's Encrypt v1, you must now specify either `version: 'draft-11'` (for Let's Encrypt v2) or `version: 'v01'` (for Let's Encrypt v1). I'd like to see your configuration to better help you, but I'm pretty sure the error your getting is that either you didn't specify `version: 'draft-11'` or you have a typo in the version. I probably still have a few incorrect or mismatched references in the documentation, so I'll double check on that.

coolaj86 reageerde

2018-05-10 15:51:10 +00:00

Eigenaar

FYI: There's some general confusion in the community on the version naming. When the ACME draft is finalized it will be "version 1". However, Let's Encrypt has been operating since pre-draft days therefore Let's Encrypt v03 will likely be ACME v1.

Hence I use the weird dual-naming scheme 'v01' and 'draft-11' so that I can track Let's Encrypt by the nought versions and ACME by the draft and complete versions.

FYI: There's some general confusion in the community on the version naming. When the ACME draft is finalized it will be "version 1". However, Let's Encrypt has been operating since pre-draft days therefore Let's Encrypt v03 will likely be ACME v1. Hence I use the weird dual-naming scheme `'v01'` and `'draft-11'` so that I can track Let's Encrypt by the nought versions and ACME by the draft and complete versions.

Ghost reageerde

2018-05-11 08:07:58 +00:00

Thank you! That did the trick.

Would you like a pull request to your README that clarifies that is required?

Thank you! That did the trick. Would you like a pull request to your README that clarifies that is required?

Ghost heeft dit probleem gesloten

2018-05-11 08:07:58 +00:00

coolaj86 reageerde

2018-05-11 21:26:03 +00:00

Eigenaar

I would love that!

Log in om deel te nemen aan deze discussie.

Geen label

Geen mijlpaal

Niet toegewezen

2 deelnemers

Notificaties

Vervaldatum

De deadline is ongeldig of buiten bereik. Gebruik het formaat 'jjjj-mm-dd'.

Geen vervaldatum ingesteld.

Afhankelijkheden

Geen afhankelijkheden ingesteld.

Referentie: coolaj86/greenlock.js-ARCHIVED#10