Certificate is not being generated

Issuance Tech
14

It might help to take a step back and think about what you’re trying to achieve.

  1. We’ve excluded using the HTTP challenge because you don’t want to open port 80.
  2. The only current alternative to the HTTP challenge is the DNS challenge.
  3. In order to use the DNS challenge successfully, you need to be able to update the TXT records on your domain.
  4. In order to enable automatic renewal using the DNS challenge, you need to integrate your DNS provider with the Let’s Encrypt client software you use (e.g. Certbot)
  5. The guide you used assumes that your nameservers are operated by one of the providers in the displayed list (e.g. Route53). However, you do not appear to use any of the supported providers.

You need to figure out how you can automatically update the TXT records on your nameservers (e.g. dns1.bigrock.in). We, on this forum, don’t know how those nameservers work or who owns them, so you need to come up with this answer.

You can manually issue a certificate using Certbot, which will ask you to manually setup the TXT records, but you would need to repeat this process every 60-90 days, which is why it is ideal to automate it.

certbot -i apache -a manual --preferred-challenges dns -d network.lemoney.in
1 Like