Certbot failed to authenticate some domains (authenticator: apache). - Timeout during connect (likely firewall problem)

My domain is:
galacticamc.xyz

I ran this command:
# certbot --apache -d galacticamc.xyz -d www.galacticamc.xyz

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Unable to read ssl_module file; not disabling session tickets.
Requesting a certificate for galacticamc.xyz and www.galacticamc.xyz
Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: galacticamc.xyz
Type: connection
Detail: Fetching http://galacticamc.xyz/.well-known/acme-challenge/HRf5J7kaqTccFDRh5YiG0ZOHPsu-X4NVy6GqGcigJO0: Timeout during connect (likely firewall problem)
Domain: www.galacticamc.xyz
Type: connection
Detail: Fetching http://www.galacticamc.xyz/.well-known/acme-challenge/WYdrHz6HeLCYjsXIzgkItJEYm7PVNwO5OZUHnBk3_qE: 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. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version):
apache24

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

My hosting provider, if applicable, is:
n/a

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

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):
certbot 1.18.0

1 Like

The http challenge needs port 80 to be open. I only see port 443 open at your IP. I can see your server just fine on port 443. Check your router to ensure it allows port 80. Check that Apache is listening for port 80 for that domain.

3 Likes

haha DUH, it was my rc.conf and ipfw - i realized i needed 80 and opened it in my router and forgot these. thanks!

3 Likes

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