fFailed to verify temporary files,trying for two weeks desparate

Help
1

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: quantummobileai.com

I ran this command: certbot -v

It produced this output:certbot -v
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: quantummobileai.com
2: www.quantummobileai.com

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

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: quantummobileai.com
Type: unauthorized
Detail: 2a02:4780:2b:1725:0:d37:d377:2: Invalid response from http://quantummobileai.com/.well-known/acme-challenge/AgEF-3S_1uSrFOpzZefYqIsGS2bD0kLKUWZnlAd9xZQ: 404

Domain: www.quantummobileai.com
Type: unauthorized
Detail: 2a02:4780:2b:1725:0:d37:d377:2: Invalid response from http://www.quantummobileai.com/.well-known/acme-challenge/62j0-ygVATspPzdl442KG3uJQ44uOrVoJJGHk0nZENg: 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:/

My web server is (include version):

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

My hosting provider, if applicable, is: Hostinger

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 2.11.0

2

See: Let's Debug

You have both an IPv4 A record and an IPv6 AAAA record in your DNS

But, the IPv6 address points to a Hostinger service not your server. Hostinger creates this AAAA record automatically for new setups.

You need to update the AAAA address or remove it if you do not support IPv6.

Any client trying to use IPv6 will connect to that Hostinger service instead of your server.
Let's Encrypt favors IPv6 when an AAAA record is present.

See Hostinger article here: How to manage AAAA records | Hostinger Help Center

6 Likes
3

I can't thank you enough! how good it was to se that padlock close. I honestly don't know if I would ever have solved that problem. Always more to learn it's been humbling I'm very grateful! Thanks so much ! that just made my day.

1 Like
4

You are welcome. We see that problem often with Hostinger

Usually we ask you to mark the post that solved it as the Solution but ... :slight_smile:

1 Like
5

new to this as well done!

1 Like
6

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