Récord aaaa goes to a

Error 204. Some challenges have failed.
How can I solve this?

We will need more info than that to help. Please answer as much as you can from the form you should have been shown when posting in the Help category


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:

I ran this command:

It produced this output:

My web server is (include version):

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

My hosting provider, if applicable, is:

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

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

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


Hi, my domain is: unificarte.com
I redirect to: unificarte.DDNS.net
I read that the problem is when aaaa record goes to a record but I don’t know how to solve it.

I don't know what you mean by that. An AAAA record is for your IPv6 address and an A record is for IPv4.

You have one of each. And, they both get the same results so that looks good. But, HTTP Challenge requests get handled by an nginx server. HTTP requests for your "home" page are handled by Apache.

The nginx server is probably your Unifi controller. Is that right? I am guessing just based on the domain name.

The 204 in the error message means "No Content". This is wrong. It should respond with the correct info for the HTTP Challenge.

If you are using Unifi controller, you might try asking on a Unifi forum how to setup the controller for Let's Encrypt. Otherwise, please provide more info.



Also, that name doesn't resolve to any IP.


It does (no-ip, so could be flaky, or it has changed recently), but connections to port 80 are timing out.

1 Like

In any case, that redirect will matter later but not for getting a cert with HTTP Challenge.

The ACME challenge URI is not redirected and handled by a different server (probably Unifi)

curl -i http://unificarte.com
HTTP/1.1 302 Found
Server: Apache
Location: http://unificarte.DDNS.net

curl -i http://unificarte.com/.well-known/acme-challenge/Test404
HTTP/1.1 204
Server: nginx

Also, since the dot com name has IPs [that don't match the ddns name IP]:

  • https://the dot com name/ will require a valid certificate BEFORE it can be redirected to https://the ddns name/

The places y redirect was limited in the free account. So that is the reasson of the error. Thanks to all.

1 Like

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