[GH-ISSUE #23] Client not working? "type": "urn:ietf:params:acme:error:malformed" with last renew #14

New issue

Open

opened 2026-03-13 16:26:30 +03:00 by kerem · 2 comments

kerem commented

2026-03-13 16:26:30 +03:00

Owner

Originally created by @xaras2 on GitHub (May 5, 2024).
Original GitHub issue: https://github.com/acme-dns/acme-dns-client/issues/23

https://acme-staging-v02.api.letsencrypt.org/acme/acct/**********

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

I receive this issue with last domain renew.
Need acme-dns-client update?

Thanks

Originally created by @xaras2 on GitHub (May 5, 2024). Original GitHub issue: https://github.com/acme-dns/acme-dns-client/issues/23 https://acme-staging-v02.api.letsencrypt.org/acme/acct/********** { "type": "urn:ietf:params:acme:error:malformed", "detail": "Method not allowed", "status": 405 } I receive this issue with last domain renew. Need acme-dns-client update? Thanks

kerem commented

2026-03-13 16:26:40 +03:00

Author

Owner

@joohoi commented on GitHub (May 5, 2024):

This message is from Let’s Encrypt API, which means that it’s caused by
whatever ACME client you are hooking acme-dns-client to. Acme-dns-client
doesn’t communicate towards the CA

On Sun 5. May 2024 at 16.52, Xaras @.***> wrote:

https://acme-staging-v02.api.letsencrypt.org/acme/acct/**********

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

I receive this issue with last domain renew.
Need acme-dns-client update?

Thanks

—
Reply to this email directly, view it on GitHub
https://github.com/acme-dns/acme-dns-client/issues/23, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABH6DJK7B5RHUECENLBXJ7DZAY2TRAVCNFSM6AAAAABHHX2JZSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI3TSNJUGM4DMOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@joohoi commented on GitHub (May 5, 2024): This message is from Let’s Encrypt API, which means that it’s caused by whatever ACME client you are hooking acme-dns-client to. Acme-dns-client doesn’t communicate towards the CA On Sun 5. May 2024 at 16.52, Xaras ***@***.***> wrote: > https://acme-staging-v02.api.letsencrypt.org/acme/acct/********** > > { > "type": "urn:ietf:params:acme:error:malformed", > "detail": "Method not allowed", > "status": 405 > } > > I receive this issue with last domain renew. > Need acme-dns-client update? > > Thanks > > — > Reply to this email directly, view it on GitHub > <https://github.com/acme-dns/acme-dns-client/issues/23>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABH6DJK7B5RHUECENLBXJ7DZAY2TRAVCNFSM6AAAAABHHX2JZSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI3TSNJUGM4DMOI> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >

kerem commented

2026-03-13 16:26:45 +03:00

Author

Owner

@xaras2 commented on GitHub (May 5, 2024):

Thanks for reply.

ok, i found my error:

modify, into /etc/letsencrypt/renewal/yourdomain.conf,
FROM server = https://acme-staging.api.letsencrypt.org/directory ------> server = https://acme-
v02.api.letsencrypt.org/directory

removed --test-cert into renew command
( correct command: certbot certonly --manual --preferred-challenges dns --manual-auth-hook 'acme-dns-client' -d
*.domain1.io -d *.domain2.io )

Thanks for reply, again :-)

@xaras2 commented on GitHub (May 5, 2024): Thanks for reply. ok, i found my error: > modify, into /etc/letsencrypt/renewal/yourdomain.conf, FROM server = https://acme-staging.api.letsencrypt.org/directory ------> server = https://acme- v02.api.letsencrypt.org/directory > removed --test-cert into renew command ( correct command: certbot certonly --manual --preferred-challenges dns --manual-auth-hook 'acme-dns-client' -d *.domain1.io -d *.domain2.io ) Thanks for reply, again :-)