# Error 405 from letsencrypt

**URL:** <https://community.letsencrypt.org/t/error-405-from-letsencrypt/124002>\
**Category:** Help\
**Created:** [May 27, 2020, 9:08am UTC](https://community.letsencrypt.org/t/error-405-from-letsencrypt/124002 "2020-05-27T09:08:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Josbrafe](https://avatars.discourse-cdn.com/v4/letter/j/dc4da7/32.png) [@Josbrafe](https://community.letsencrypt.org/u/Josbrafe)\
**Post date:** [May 27, 2020, 9:08am UTC](https://community.letsencrypt.org/t/error-405-from-letsencrypt/124002/1 "2020-05-27T09:08:22Z")

</div>

I created a certificate using certbot, and installed it into kubernetes.  
but when I try to request for a new certificate for a subdomain I get error 405 from letsencrypt.

{  
“type”: “urn:ietf:params:acme:error:malformed”,  
“detail”: “Method not allowed”,  
“status”: 405  
}

I am using cert-manager version 0.12 in my k8s cluster.  
I am using dns validation.

What can I check to make my troubleshooting easier.

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [May 27, 2020, 9:19am UTC](https://community.letsencrypt.org/t/error-405-from-letsencrypt/124002/2 "2020-05-27T09:19:38Z")

</div>

Hi @Josbrafe

> [@Josbrafe](#):
>
> {  
> “type”: “urn:ietf:params:acme:error:malformed”,  
> “detail”: “Method not allowed”,  
> “status”: 405  
> }

if you have that error, your ACME-client is too old.

There was a switch - method GET -\> method POST.

Older clients -\> you see that error.

---

<div class="post-metadata">

**Author:** ![Josbrafe](https://avatars.discourse-cdn.com/v4/letter/j/dc4da7/32.png) [@Josbrafe](https://community.letsencrypt.org/u/Josbrafe)\
**Post date:** [May 27, 2020, 10:15am UTC](https://community.letsencrypt.org/t/error-405-from-letsencrypt/124002/3 "2020-05-27T10:15:16Z")

</div>

Hi @JuergenAuer,

I will update you shortly.  
Thanks for reaching out to me.

I am currently testing out cert-manager v0.14.1 helm chart.

Regards,  
Josbrafe

---

<div class="post-metadata">

**Author:** ![Josbrafe](https://avatars.discourse-cdn.com/v4/letter/j/dc4da7/32.png) [@Josbrafe](https://community.letsencrypt.org/u/Josbrafe)\
**Post date:** [May 28, 2020, 1:42pm UTC](https://community.letsencrypt.org/t/error-405-from-letsencrypt/124002/4 "2020-05-28T13:42:19Z")

</div>

Hi @JuergenAuer,

I believe that this seems to be a normal behavior, in the order request of the csr, the finalize url, displays the above error.  
Even with above error, I still received a valid certificate.

Though the initial content of my certificate and clusterIssuer files was wrong, I corrected that.  
It is still a puzzle to me, while it still shows valid certificate, with above error.

Old version of cert-manager: 0.12  
Current version of cert-manager: 0.14.1

Regards,  
Joseph

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [June 27, 2020, 1:56pm UTC](https://community.letsencrypt.org/t/error-405-from-letsencrypt/124002/5 "2020-06-27T13:56:23Z")

</div>

Closed on June 27, 2020, 1:56pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.