ACME-v2: Invalid HTTP method when fething challenges #53

Nouveau ticket

Ghost · 2020-10-14T16:35:03Z

Ghost a commenté

2020-10-14 16:35:03 +00:00

.

RFC8555 states:

   To request authorization for an identifier, the client sends a POST
   request to the newAuthz resource specifying the identifier for which
   authorization is being requested.

acme-v2 version 1.8.6 uses GET

RFC8555 states: ``` To request authorization for an identifier, the client sends a POST request to the newAuthz resource specifying the identifier for which authorization is being requested. ``` acme-v2 version 1.8.6 uses `GET`

coolaj86 a commenté

2020-10-14 18:09:29 +00:00

.

Propriétaire

this was fixed over a year ago. you need to update to the latest version of greenlock.

Ghost a commenté

2020-10-20 06:34:51 +00:00

.

Auteur

I've installed the latest version of greenlock-cli, which comes with acme-v2 1.8.6. I've used the following command:

npm install greenlock-cli

How can I update this to the compliant version?

I've installed the latest version of greenlock-cli, which comes with acme-v2 1.8.6. I've used the following command: ``` npm install greenlock-cli ``` How can I update this to the compliant version?

Connectez-vous pour rejoindre cette conversation.

Sans labels

Sans jalon

Sans assignation

2 participants

Notifications

Échéance

La date d’échéance est invalide ou hors plage. Veuillez utiliser le format 'aaaa-mm-dd'.

Aucune échéance n'a été définie.

Dépendances

Aucune dépendance définie.

Référence : coolaj86/greenlock.js-ARCHIVED#53