# Certbot failed to authenticate some domains

**URL:** <https://community.letsencrypt.org/t/certbot-failed-to-authenticate-some-domains/224281>\
**Category:** Help\
**Created:** [August 23, 2024, 1:44pm UTC](https://community.letsencrypt.org/t/certbot-failed-to-authenticate-some-domains/224281 "2024-08-23T13:44:44Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![jacmath](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@jacmath](https://community.letsencrypt.org/u/jacmath)\
**Post date:** [August 23, 2024, 1:44pm UTC](https://community.letsencrypt.org/t/certbot-failed-to-authenticate-some-domains/224281/1 "2024-08-23T13:44:44Z")

</div>

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. [https://crt.sh/?q=example.com](https://crt.sh/?q=example.com)), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: [jaco.ddns.net](http://jaco.ddns.net)

I ran this command: sudo certbot --apache --agree-tos --redirect --hsts --staple-ocsp --email [you@example.com](mailto:you@example.com) -d [yourdomain.com](http://yourdomain.com)

It produced this output:Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:  
Domain: [jaco.ddns.net](http://jaco.ddns.net)  
Type: connection  
Detail: 209.54.75.184: Fetching [http://jaco.ddns.net/.well-known/acme-challenge/OM0nE4Zr-7ssOjSG4Ow2BME-ekmWFsS9YjOLXxfhLwg:](http://jaco.ddns.net/.well-known/acme-challenge/OM0nE4Zr-7ssOjSG4Ow2BME-ekmWFsS9YjOLXxfhLwg:) Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet.

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

My web server is (include version): debian12

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

My hosting provider, if applicable, is: no-ip

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

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):no

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

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [August 23, 2024, 1:48pm UTC](https://community.letsencrypt.org/t/certbot-failed-to-authenticate-some-domains/224281/2 "2024-08-23T13:48:26Z")

</div>

> [@jacmath](#):
>
> Timeout during connect (likely firewall problem)

Have you made sure that HTTP requests can reach your system?

---

<div class="post-metadata">

**Author:** ![jacmath](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@jacmath](https://community.letsencrypt.org/u/jacmath)\
**Post date:** [August 23, 2024, 2:47pm UTC](https://community.letsencrypt.org/t/certbot-failed-to-authenticate-some-domains/224281/3 "2024-08-23T14:47:28Z")

</div>

Hi

yes I can access my server in HTTP

If it's a firewall problem I'm not sure how to fix that ?

Thanks

---

<div class="post-metadata">

**Author:** ![Nekit](https://avatars.discourse-cdn.com/v4/letter/n/7feea3/32.png) [@Nekit](https://community.letsencrypt.org/u/Nekit)\
**Post date:** [August 23, 2024, 2:49pm UTC](https://community.letsencrypt.org/t/certbot-failed-to-authenticate-some-domains/224281/4 "2024-08-23T14:49:18Z")

</div>

Can you access it from _the public internet_? E.g. from your phone with wi-fi off, on a cellular (data) connection? I would suggest to review Port Forwarding settings on your router.

---

<div class="post-metadata">

**Author:** ![jacmath](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@jacmath](https://community.letsencrypt.org/u/jacmath)\
**Post date:** [August 24, 2024, 12:49pm UTC](https://community.letsencrypt.org/t/certbot-failed-to-authenticate-some-domains/224281/5 "2024-08-24T12:49:15Z")

</div>

I can not access from public internet and port forwording are ok ??

---

<div class="post-metadata">

**Author:** ![orangepizza](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/orangepizza/32/19597_2.png) [@orangepizza](https://community.letsencrypt.org/u/orangepizza)\
**Post date:** [August 24, 2024, 2:32pm UTC](https://community.letsencrypt.org/t/certbot-failed-to-authenticate-some-domains/224281/6 "2024-08-24T14:32:17Z")

</div>

I can see a debain apache from link

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [September 23, 2024, 2:32pm UTC](https://community.letsencrypt.org/t/certbot-failed-to-authenticate-some-domains/224281/7 "2024-09-23T14:32:49Z")

</div>

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