v1 staging: fails in walk chain because letsencrypt now redirect you #286

New Issue

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

adam commented

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

Originally created by @az143 on GitHub (Mar 3, 2018).

i'm testing my setup with the current/v1 staging setup, and dehydrated -c fails in walk chain because
http://cert.stg-int-x1.letsencrypt.org/ is no longer available in that location; instead letsencrypt redirects you to https://.

workaround for me: tell curl to follow redirections, ie add CURL_OPTS="-L" to the dehydrated config.

$ dehydrated -e
...
declare -- CA="https://acme-staging.api.letsencrypt.org/directory"
...
$ dehydrated -c
...
+ Creating fullchain.pem...
 + Walking chain...
  + ERROR: An error occurred while sending get-request to http://cert.stg-int-x1.letsencrypt.org/ (Status 301)

Details:
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>


ERROR: Walking chain has failed, your certificate has been created and can be found at <hidden>, the corresponding private key at <hidden>.

Originally created by @az143 on GitHub (Mar 3, 2018). i'm testing my setup with the current/v1 staging setup, and dehydrated -c fails in walk chain because http://cert.stg-int-x1.letsencrypt.org/ is no longer available in that location; instead letsencrypt redirects you to https://. workaround for me: tell curl to follow redirections, ie add CURL_OPTS="-L" to the dehydrated config. ``` $ dehydrated -e ... declare -- CA="https://acme-staging.api.letsencrypt.org/directory" ... $ dehydrated -c ... + Creating fullchain.pem... + Walking chain... + ERROR: An error occurred while sending get-request to http://cert.stg-int-x1.letsencrypt.org/ (Status 301) Details: <html> <head><title>301 Moved Permanently</title></head> <body bgcolor="white"> <center><h1>301 Moved Permanently</h1></center> <hr><center>nginx</center> </body> </html> ERROR: Walking chain has failed, your certificate has been created and can be found at <hidden>, the corresponding private key at <hidden>. ```

adam closed this issue

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

adam commented

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

@lukas2511 commented on GitHub (Mar 3, 2018):

Are you using the newest version from git? This should already be fixed since 7a0e71c6c2.

Edit: dehydrated 0.6.0 will be released in the next few days and will include this fix

@lukas2511 commented on GitHub (Mar 3, 2018): Are you using the newest version from git? This should already be fixed since 7a0e71c6c2ccc6e98abca5ea1c7de28053e90c02. Edit: dehydrated 0.6.0 will be released in the next few days and will include this fix

adam commented

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

@az143 commented on GitHub (Mar 4, 2018):

you're right. i'm sorry for the noise; i'm using 0.5.0 and somehow i missed the commit comment about this having been fixed since the release.

@az143 commented on GitHub (Mar 4, 2018): you're right. i'm sorry for the noise; i'm using 0.5.0 and somehow i missed the commit comment about this having been fixed since the release.

adam referenced this issue

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

[PR #286] [CLOSED] Create Alpine based Dockerfile #786

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dehydrated#286