Cant create a certificate - Port 80 issue

Help
1

My domain is: nomadus.duckdns.org

I ran this command: certbot certonly --standalone -d nomadus.duckdns.org

It produced this output:

Requesting a certificate for nomadus.duckdns.org

Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:

Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile C:\Certbot\log\letsencrypt.log or re-run Certbot with -v for more details.

The only i can say that i know for sure is that i have an active port fowarding for 80
as well an active rule in my windows firewall for the inbound. So i have no clue on why i have that issue.

There's a chance that i have made something wrong with those steps, but so far i review it several times and doesn't appear to be wrong.

My web server is (include version): I would love to tell, but i have no idea.

The operating system my web server runs on is (include version): Windows 10

My hosting provider, if applicable, is: I would say duckdns

I can login to a root shell on my machine (yes or no, or I don't know): i dont know

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): control panel in like Command Prompt? cuz no idea.

**The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):**certbot 1.24.0

2

Hello @DarkNomadus, welcome to the Let's Encrypt community. :slightly_smiling_face:

Well I do not believe that HTTP Port 80 is open.

$ curl -I http://nomadus.duckdns.org/.well-known/acme-challenge/FP6atzuxSAl_OacMUWPiPdRZz6CRjJ8CYFDU2_s0ZkM
curl: (28) Failed to connect to nomadus.duckdns.org port 80 after 129867 ms: Connection timed out

And

$ nmap -Pn nomadus.duckdns.org
Starting Nmap 7.80 ( https://nmap.org ) at 2022-11-19 22:51 UTC
Nmap scan report for nomadus.duckdns.org (212.225.225.91)
Host is up.
rDNS record for 212.225.225.91: 91.red.225.225.212.procono.es
All 1000 scanned ports on nomadus.duckdns.org (212.225.225.91) are filtered

Nmap done: 1 IP address (1 host up) scanned in 201.93 seconds

Best Practice - Keep Port 80 Open

2 Likes
3

@DarkNomadus,
Please find your IP Address with https://ifconfig.co/ in a Web Browser as you stated you are running on

On the machine that

Also (just informational)

Spins up itself as a temporary web server for getting the certificate.

1 Like
4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.