You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+25-2Lines changed: 25 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,26 @@
1
1
Let's Encrypt DNS Challenge
2
2
===========================
3
3
4
+
## Why ?
5
+
6
+
# New Image / Container
7
+
Generally you start your letsencrpyt container and make an authentication challenge over http.
8
+
9
+
The problem here is that the http authentication requires both standard ports from http (80/tcp) and https(443/tcp).
10
+
11
+
I couldn't managet it to use other ports for the http challenge. So in that case it requires to temporarily shutdown your loadbalancer to receive a new certificate.
12
+
13
+
Later I read on and I found out that the [ACME Spec](https://letsencrypt.github.io/acme-spec/) supports more than http authentication challenge.
14
+
15
+
So I found the interessting point. That I can resolve my authentication over dns.
16
+
17
+
Futhermore I wan't to be able to do in future and I don't want to handle all dependencies again, so I wrote this container.
18
+
19
+
### Cloudflare
20
+
21
+
Cloudflare helps to automatically generate dns entries in this case TXT Records to supoort the [DNS Authentication](https://letsencrypt.github.io/acme-spec/#dns),
22
+
because they provide an API for managing her DNS Server.
23
+
4
24
This repo contains only an image for an letsencrpyt container to use dns challenge with cloudflare.
0 commit comments