1ab68e6 check if curl is able to reach letsencrypt via http and https.
📊 Changes
1 file changed (+16 additions, -0 deletions)
View changed files
📝letsencrypt.sh (+16 -0)
📄 Description
I had the problem that http_proxy env var was not set. Because of set -e curl terminated with != 0 and the whole script terminated without error message.
So I've added 2 checks in check_dependencies() if curl is able to reach letsencrypt.org via http and https.
Another problem could be the firewall (port 80 or 443 blocked), dns or routing.
🔄 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/133
**Author:** [@mitch-geht-ab](https://github.com/mitch-geht-ab)
**Created:** 2/12/2016
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `master`
---
### 📝 Commits (1)
- [`1ab68e6`](https://github.com/dehydrated-io/dehydrated/commit/1ab68e6173853e79cb72a485b6874c94221c09f7) check if curl is able to reach letsencrypt via http and https.
### 📊 Changes
**1 file changed** (+16 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `letsencrypt.sh` (+16 -0)
</details>
### 📄 Description
I had the problem that http_proxy env var was not set. Because of set -e curl terminated with != 0 and the whole script terminated without error message.
So I've added 2 checks in check_dependencies() if curl is able to reach letsencrypt.org via http and https.
Another problem could be the firewall (port 80 or 443 blocked), dns or routing.
---
<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/133
Author: @mitch-geht-ab
Created: 2/12/2016
Status: ❌ Closed
Base:
master← Head:master📝 Commits (1)
1ab68e6check if curl is able to reach letsencrypt via http and https.📊 Changes
1 file changed (+16 additions, -0 deletions)
View changed files
📝
letsencrypt.sh(+16 -0)📄 Description
I had the problem that http_proxy env var was not set. Because of set -e curl terminated with != 0 and the whole script terminated without error message.
So I've added 2 checks in check_dependencies() if curl is able to reach letsencrypt.org via http and https.
Another problem could be the firewall (port 80 or 443 blocked), dns or routing.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.