An error occurred while sending post-request to http://my.domain/.well-known/acme-challenge/... #339

New Issue

adam · 2025-12-29T01:23:21+01:00

adam commented

2025-12-29 01:23:21 +01:00

Originally created by @repomaa on GitHub (Apr 25, 2018).

Lately I've come across this bug:

(Longer than 30 days). Ignoring because renew was forced!
 + Signing domains...
 + Generating private key...
 + Generating signing request...
 + Requesting new certificate order from CA...
 + Received 1 authorizations URLs from the CA
 + Handling authorization for my.domain
 + 1 pending challenge(s)
 + Deploying challenge tokens...
Configuring nginx for acme challenge (my.domain)
 + Responding to challenge for my.domain authorization...
  + ERROR: An error occurred while sending post-request to http://my.domain/.well-known/acme-challenge/Qu6DxevKnvFIksMVVIU6mGeaKpgXxoPv_stj_HNg0WQ (Status 405)

Details:
HTTP/1.1 405 Not Allowed
Server: nginx
Date: Wed, 25 Apr 2018 17:20:56 GMT
Content-Type: text/html
Content-Length: 166
Connection: keep-alive
Strict-Transport-Security: max-age=15768000; includeSubDomains; preload

<html>
<head><title>405 Not Allowed</title></head>
<body bgcolor="white">
<center><h1>405 Not Allowed</h1></center>
<hr><center>nginx</center>
</body>
</html>

I'm super confused why dehydrated tries to send a POST request to .well-known...

Originally created by @repomaa on GitHub (Apr 25, 2018). Lately I've come across this bug: ``` (Longer than 30 days). Ignoring because renew was forced! + Signing domains... + Generating private key... + Generating signing request... + Requesting new certificate order from CA... + Received 1 authorizations URLs from the CA + Handling authorization for my.domain + 1 pending challenge(s) + Deploying challenge tokens... Configuring nginx for acme challenge (my.domain) + Responding to challenge for my.domain authorization... + ERROR: An error occurred while sending post-request to http://my.domain/.well-known/acme-challenge/Qu6DxevKnvFIksMVVIU6mGeaKpgXxoPv_stj_HNg0WQ (Status 405) Details: HTTP/1.1 405 Not Allowed Server: nginx Date: Wed, 25 Apr 2018 17:20:56 GMT Content-Type: text/html Content-Length: 166 Connection: keep-alive Strict-Transport-Security: max-age=15768000; includeSubDomains; preload <html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx</center> </body> </html> ``` I'm super confused why dehydrated tries to send a POST request to .well-known...

adam closed this issue

2025-12-29 01:23:21 +01:00

adam commented

2025-12-29 01:23:22 +01:00

@lukas2511 commented on GitHub (Apr 25, 2018):

Can you please update your version of dehydrated? This really seems to be a duplicate of #515 and has been fixed since over a month.

@lukas2511 commented on GitHub (Apr 25, 2018): Can you please update your version of dehydrated? This really seems to be a duplicate of #515 and has been fixed since over a month.

adam commented

2025-12-29 01:23:22 +01:00

@lukas2511 commented on GitHub (Apr 25, 2018):

@jreinert can you give me some feedback after trying the current master version? I'm preparing a release with the fix and would like to know if it really works.

@lukas2511 commented on GitHub (Apr 25, 2018): @jreinert can you give me some feedback after trying the current master version? I'm preparing a release with the fix and would like to know if it really works.

adam referenced this issue

2025-12-29 01:29:23 +01:00

[PR #339] [CLOSED] Debianized #803

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dehydrated#339