From 8fa0d4cc58b844d84f7b1bf6f269162b645a2f0d Mon Sep 17 00:00:00 2001 From: Navan Chauhan Date: Mon, 23 Nov 2020 19:39:48 +0530 Subject: Publish deploy 2020-11-23 19:39 --- posts/2020-11-17-Lets-Encrypt-DuckDns/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'posts/2020-11-17-Lets-Encrypt-DuckDns') diff --git a/posts/2020-11-17-Lets-Encrypt-DuckDns/index.html b/posts/2020-11-17-Lets-Encrypt-DuckDns/index.html index de0df91..c319535 100644 --- a/posts/2020-11-17-Lets-Encrypt-DuckDns/index.html +++ b/posts/2020-11-17-Lets-Encrypt-DuckDns/index.html @@ -1,4 +1,4 @@ -Generating HTTPS Certificate using DNS a Challenge through Let's Encrypt | Navan Chauhan
3 minute readCreated on November 17, 2020

Generating HTTPS Certificate using DNS a Challenge through Let's Encrypt

I have a Raspberry-Pi running a Flask app through Gunicorn (Ubuntu 20.04 LTS). I am exposing it to the internet using DuckDNS.

Dependencies

sudo apt update && sudo apt install certbot -y +Generating HTTPS Certificate using DNS a Challenge through Let's Encrypt | Navan Chauhan
3 minute readCreated on November 17, 2020

Generating HTTPS Certificate using DNS a Challenge through Let's Encrypt

I have a Raspberry-Pi running a Flask app through Gunicorn (Ubuntu 20.04 LTS). I am exposing it to the internet using DuckDNS.

Dependencies

sudo apt update && sudo apt install certbot -y

Get the Certificate

sudo certbot certonly --manual --preferred-challenges dns-01 --email senpai@email.com -d mydomain.duckdns.org

After you accept that you are okay with you IP address being logged, it will prompt you with updating your dns record. You need to create a new TXT record in the DNS settings for your domain.

For DuckDNS users it is as simple as entering this URL in their browser:

http://duckdns.org/update?domains=mydomain&token=duckdnstoken&txt=certbotdnstxt

Where mydomain is your DuckDNS domain, duckdnstoken is your DuckDNS Token ( Found on the dashboard when you login) and certbotdnstxt is the TXT record value given by the prompt.

You can check if the TXT records have been updated by using the dig command:

dig navanspi.duckdns.org TXT -- cgit v1.2.3