coolaj86
/
greenlock.js-ARCHIVED
3
3
Fork 0
Code Issues 13 Pull Requests 1 Releases Activity
Labels Milestones
New Issue

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

Open
by Ghost opened 4 years ago · 2 comments
Ghost commented 4 years ago

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 commented 4 years ago
Owner

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

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

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?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
acmev2
dns-challenge-regression-fix
github
greenlock
master
next
node-letsencrypt-python
npm
v1
v2
v2.1
v2.2
v2.3
v2.4
v2.5
v3
v4
wip
Labels
Apply labels
Clear labels
No items
No Label
Milestone
Set milestone
Clear milestone
No items
No Milestone
Assignees
Assign users
Clear assignees
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Write Preview
Loading…
Cancel
Save
There is no content yet.
Delete Branch '%!s(MISSING)'

Deleting a branch is permanent. It CANNOT be undone. Continue?

No
Yes