I just had an issue after switching from dns based challenges to http (see serverfault and le-community) so I made this quick fix which allowed me to use dehydrated again.
The change in Line 464(old)/468(new) corresponds to the "bigger" answer as mentioned in the serverfault post. Indeed it may not longer be necessary as I implemented a "quick escape" before extracting the challenges but I would leave it there - just in case.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/dehydrated-io/dehydrated/pull/283
**Author:** [@dennisschuerholz](https://github.com/dennisschuerholz)
**Created:** 9/20/2016
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `master`
---
### 📝 Commits (2)
- [`28ba07d`](https://github.com/dehydrated-io/dehydrated/commit/28ba07d26b37bd63e7764080ab11d206c5d1ccda) Fix request new certificate if authorization valid
- [`01f26f5`](https://github.com/dehydrated-io/dehydrated/commit/01f26f53ea35d3f19c04b8ebd1859dc3107f3492) fix unbound variable
### 📊 Changes
**1 file changed** (+14 additions, -3 deletions)
<details>
<summary>View changed files</summary>
📝 `dehydrated` (+14 -3)
</details>
### 📄 Description
I just had an issue after switching from dns based challenges to http (see [serverfault](https://serverfault.com/questions/804030/letsencrypt-certificate-renewal-switching-from-dns-to-http) and [le-community](https://community.letsencrypt.org/t/certificate-renewal-switching-from-dns-to-http/20030?u=dennisschuerholz)) so I made this quick fix which allowed me to use dehydrated again.
The change in Line 464(old)/468(new) corresponds to the "bigger" answer as mentioned in the serverfault post. Indeed it may not longer be necessary as I implemented a "quick escape" before extracting the challenges but I would leave it there - just in case.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/dehydrated-io/dehydrated/pull/283
Author: @dennisschuerholz
Created: 9/20/2016
Status: ❌ Closed
Base:
master← Head:master📝 Commits (2)
28ba07dFix request new certificate if authorization valid01f26f5fix unbound variable📊 Changes
1 file changed (+14 additions, -3 deletions)
View changed files
📝
dehydrated(+14 -3)📄 Description
I just had an issue after switching from dns based challenges to http (see serverfault and le-community) so I made this quick fix which allowed me to use dehydrated again.
The change in Line 464(old)/468(new) corresponds to the "bigger" answer as mentioned in the serverfault post. Indeed it may not longer be necessary as I implemented a "quick escape" before extracting the challenges but I would leave it there - just in case.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.