Changes

====Some challenges complete successfully but some hostnames fail====

====Some challenges complete successfully but some hostnames fail====

If you see some of your challenges returned without error but some fail, you need to make sure that you have Public DNS A or MX records for all the host names that you are adding to your certificate. Using the command:

If you see some of your challenges returned without error but some fail, you possibly do not have Public DNS A or MX records for all the host names that you are adding to your certificate. Using the command:

  config setprop letsencrypt configure all

  config setprop letsencrypt configure all

Is likely to cause this to happen. When a domain is added to an SME server, several host names are created automatically. these include ftp.your-domain.com, wpad.your-domain.com, proxy.your-domain.com, mail.your-domain.com, www.your-domain.com. Most of us do not create public DNS records for all these host names. When letsencrypt issues a challenge for a list of host names and '''ONE''' does not resolve, the challenge will fail and the certificate will not generate at all.

Is likely to cause this error. When a domain is added to an SME server, several host names are created automatically. these include ftp.your-domain.com, wpad.your-domain.com, proxy.your-domain.com, mail.your-domain.com, www.your-domain.com. Most of us do not create public DNS records for all these host names. When letsencrypt issues a challenge for a list of host names and '''ONE''' does not resolve, the challenge will fail and the certificate will not generate at all.

To resolve this, issue the following command:

To resolve this, issue the following command: