Bug 50614 - Let's encrypt: "Method not allowed" in dry-run/with test-CA
Let's encrypt: "Method not allowed" in dry-run/with test-CA
Status: RESOLVED DUPLICATE of bug 50976
Product: UCS
Classification: Unclassified
Component: Let's Encrypt
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: Erik Damrose
Sönke Schwardt
https://github.com/diafygi/acme-tiny/...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-12-10 10:36 CET by Sönke Schwardt-Krummrich
Modified: 2020-03-19 09:13 CET (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.171
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sönke Schwardt-Krummrich univentionstaff 2019-12-10 10:36:36 CET
The let's encrypt client currently returns 

Aktueller Status der App
"detail": "Method not allowed",

if the test-CA is used. Looks like the "dry-run"/usage of test-CA is now broken:

See also:
https://community.letsencrypt.org/t/method-not-allowed-error-in-staging-environment/108194
https://community.letsencrypt.org/t/acme-breaking-change-most-gets-become-posts/71025
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2019-12-10 10:38:36 CET
This does (currently) not affect the production CA. So a valid certificate is created on my machine.
I have not investigated, but maybe the breaking change is done later on with production CA.
Comment 2 Erik Damrose univentionstaff 2020-03-19 09:13:39 CET
Marking as duplicate. The other bug is more recent and has more debug output

*** This bug has been marked as a duplicate of bug 50976 ***