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

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. crt.sh | 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: stkippgrisumenep.ac.id

I ran this command: certbot --apache -v

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache

Which names would you like to activate HTTPS for?
We recommend selecting either all domains, or all domains in a VirtualHost/server block.


1: stkippgrisumenep.ac.id


Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel): 1
Requesting a certificate for stkippgrisumenep.ac.id
Performing the following challenges:
http-01 challenge for stkippgrisumenep.ac.id
Waiting for verification...
Challenge failed for domain stkippgrisumenep.ac.id
http-01 challenge for stkippgrisumenep.ac.id

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: stkippgrisumenep.ac.id
Type: unauthorized
Detail: 2a02:4780:3:c130::39: Invalid response from http://stkippgrisumenep.ac.id/.well-known/acme-challenge/dHWR70LE8hqkAKudKJP5rTizDmyO8MV2h3crrPiMwV4: 404

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.

Cleaning up challenges
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): Server version: Apache/2.4.59 (Ubuntu)

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

My hosting provider, if applicable, is:

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, but the other domain is on cpanel

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


previously, the website was on cpanel hosting. but for some reason, I moved the main website to a private server, by changing the IP from the hosting IP to the server's own IP.

Previously, in cpanel, the main website was using Let's Encrypt, and it was smooth. So, is this why I can't create a new certificate on my server?

Need help.
Thank you

1 Like

Welcome to the community @ajunk.pracetio

You have an AAAA record in your DNS for IPv6. But, it points to a litespeed server not your Apache. Let's Encrypt prefers the IPv6 when present.

You should either correct that or remove the AAAA record.

8 Likes

The moral of the story is : KILL IPV6 until you get your cert and then fix your ipv6 configuration.
@MikeMcQ is right.

5 Likes

Hi @MikeMcQ

Thank you for your reply. I will find that record on my cpanel. If there is any progress, I will writing here.

Update : I deleted my domain that using IPV6 at my cpanel, and then run cerbot command again, and it's running well.

thank you for all help.
Best Regards,
Agung PW

5 Likes

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