SSL certificate not issued (status Failed): causes and fixes

Updated 2026-10-29

On this page
  1. Symptoms
  2. Causes
  3. Fix
  4. Good to know
  5. Still not working?

Symptoms

  • On SSL/TLS (control panel, section Domains), a website shows Failed.
  • A line under the domain gives the reason, starting with the domain name, for example example.com: Invalid response from http://example.com/.well-known/acme-challenge/...: 404.
  • The browser warns that the connection is not private, or the site opens without the padlock.
Note: if the status is Waiting for DNS, the domain does not point here yet. See Waiting for DNS.

Causes

Match the error text under the domain:

  1. Invalid response … 404 or 403 — the certificate authority could not read the check file in /.well-known/acme-challenge/ of the website.
  2. CAA record … prevents issuance — a CAA record of the domain does not allow Let's Encrypt.
  3. Timeout or Connection refused — the certificate authority could not reach the server on port 80, or the AAAA record points to an address that does not answer.
  4. Rate limit of the certificate authority reached — too many certificates or failed attempts for the domain in a short time.
  5. A wildcard certificate needs example.com to use this server's nameservers — a wildcard was requested for a domain whose DNS is elsewhere.

Fix

1. Let the check file through. Look in the website's folder for a .htaccess file or a security plugin that blocks or redirects /.well-known/. Allow that path, then click Check now. If the whole website (folder /) is password-protected in Access Control, the check file is refused too: protect only the folders that need it (for example /admin), or remove the protection while the certificate is issued and renewed.

2. Allow Let's Encrypt in CAA. In Zone Editor, add a CAA record with the value 0 issue "letsencrypt.org", or delete the CAA records you do not need. See DNS record types.

3. Check the addresses. Make sure the domain's A record and any AAAA record point to this server. Use Site Check (section Advanced). Remove an AAAA record that points elsewhere.

4. Wait. Rate limits clear by themselves, usually within hours (at most a week). Do not click Check now repeatedly; AutoSSL retries on its own.

5. Use this server's nameservers or remove the wildcard. Point the domain's nameservers here, or click Remove wildcard to go back to normal certificates. See wildcard certificates.

Good to know

  • While a certificate is still valid, a failed renewal does not remove it. The website keeps its padlock while AutoSSL retries.
  • After a failure, automatic attempts for that website pause for 6 hours. Check now tries at once.

Still not working?

Give your hosting provider the domain and the full error line from SSL/TLS. Administrators can also see the failed task in Task Queue.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.